Hey Bob,
Little resemblance? I would not say that. If I look at schematics vs. schematics, pcb vs. pcb, code vs. code, I do not come to this conclusion (notabene without downplaying Onefinity’s adaptation work).
You mean e.g. one might wonder when or whether at all the macros feature which buildbotics implemented will become available on Onefinity. I count at least three threads started in “Feature Requests” asking for this. I don’t know if they are responsive to this.
Of course, everybody who makes a fork has the option to ignore improvements that are made upstream. But if sometimes such seems to be the case, it’s often because maintaining a fork and keep up with upstream fixes and improvements really is work.
I would say if it is a feature that has nothing to do with the modifications that the forker applies to forked code, and especially in this case according to the amount of code that is originary from buildbotics, I would address such a feature request upstream. I also see more chances for implementing something new there, and I also feel it is the right way to go. In my eyes making clear to the manufacturer of an entire CNC machine that customers want something from controller upstream is a second step. Of course you can request that feature from Onefinity, I’m not opposing to this, if you find it more probable to succeed this way.