>Chris, it seems there needs to be a process to look at new work becasue >what you are saying is if you are not in the inner sanctum, you can't >contribute. It more difficult to contribute yes. The more complicated the work the worse that is. TP and motion are surely the least understood sections of code - so only a few feel qualified, but GUI work for instance is much safer - ie I think I have merged all Phill's pull requests for pyqt. (Which is my project) and some to AXIS. I feel reasonably confident to do GUI work - I only occasionally dabble with motion control work. I just don't understand enough - and none of it is documented that well. I don't program for a living.
>But if you are in the inner sanctum, you don't have the time. >Certainly a Catch22 and its users like us who suffer if guys like Randy and >Phill aren't given the keys to the inner sanctum. I was suggesting to give Phill, Rob and John push rights if they were interested. >But it begs the question if Tormach paid for the development and depended >it for their business, why wasn't their work merged when it was all fresh >and you had them on side to guide the process through if it broke something? To some degree it was - the look-ahead TP is Rob's work from pilotpath. And Rob and John have made pull requests for updates. I would say it requires a 'leader' of sorts and a formal process. For instance machinekit has a formal process for merging work: Collective Code Construction Contract (C4, Rev. 1)<http://rfc.zeromq.org/spec:22>, and a project direction: https://www.machinekit.io/about/ I've never submitted work so I can't say how well it works, but at the least you have a process to follow. >I think state tags has some nice features that would make Phills job as the >plasma machine expert a lot easier (like reading the Commanded velocity as >the current velocity is not useful in the plasma context). Yes there is lots of good thing to come yet. Hopefully we don't lose too many either (like the jog while paused work) Chris M _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
