New submission process for feature enhancements

Thanks for all the feedback.

Your z hop stuff was submitted prior to July 1st - I will try to review it regardless of the discussion here.

I’m happy with the GNU GPL v3 license for Klipper. I don’t have any plans to change the license. (There are also many copyright holders now, so it’s not clear I could change the license even if I did want to.)

FWIW, in my experience, “testing branches” do not provide much value in practice. What I’ve seen happen in other projects is that they tend to consume precious contributor time and rarely catch bugs. The main issue I’ve seen is that merging, remerging, tracking conflicts and coordination require active work. However, when users (and other developers) run into an issue on the “testing branch” they tend to think, “I guess that’s what happens on a testing branch” and the issue rarely gets reported or fixed. So, in effect, the coordination effort increases but the benefits don’t.

That said, I think it’s fine if someone wants to run a development or testing repo. I think it is great when more people to run tests, provide feedback, and try new experiments.

Cheers,
-Kevin

2 Likes