Well that explains why I couldn’t figure out a rational numbering system. When I clone a repo the next thing I do is create a fork if I know I am going to be making some changes. Then the process of merging forks gets a lot more entertaining (ok a LOT more difficult) - but a proper repo/code management system relies on checkouts and assignments to a developer, GitHub doesn’t work like that AFAIK, at least not in a formal way. I believe that’s why modular code development with defined interfaces works well - that’s how we wrote COBOL code for running factory control systems. Then you can allocate resources to module development. All this AI code writing hype is just nonsense when it cannot determine good from bad, clean from buggy. Sorry Dave I cannot do that. Roger. Sent from my iPhone 6

ROFLOL... I have had to much to drink to unpack this beyond you are so right that I have to take an extra day to post a GO DO SOMETHING SCRIPT... On Wed, Dec 10, 2025 at 5:40 AM Roger Whiteley via Discuss < discuss@lists.openscad.org> wrote: > Well that explains why I couldn’t figure out a rational numbering system. > When I clone a repo the next thing I do is create a fork if I know I am > going to be making some changes. > > Then the process of merging forks gets a lot more entertaining (ok a LOT > more difficult) - but a proper repo/code management system relies on > checkouts and assignments to a developer, GitHub doesn’t work like that > AFAIK, at least not in a formal way. > > I believe that’s why modular code development with defined interfaces > works well - that’s how we wrote COBOL code for running factory control > systems. Then you can allocate resources to module development. > > All this AI code writing hype is just nonsense when it cannot determine > good from bad, clean from buggy. > Sorry Dave I cannot do that. > > Roger. Sent from my iPhone 6 > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org