Leaving python-dev behind

Posted Jul 21, 2022 16:13 UTC (Thu) by farnz (subscriber, #17727)
In reply to: Leaving python-dev behind by pizza
Parent article: Leaving python-dev behind

And your attitude as expressed here is perfectly reasonable; if you don't mind the "new guard" bypassing your project entirely and doing their own thing in the same space, that's great.

But it is unreasonable to simultaneously complain that people are working on a new thing in the same space as your thing, and also refuse to change the way you work to make working on your thing attractive to people who work on the new thing. Make your choice: do you want to minimise change for existing contributors, and accept that future contributors (if any) might instead start a fork or new thing, or do you want to adopt changes that increase the chance of future contributors and risk losing existing contributors?

Both of those are reasonable choices to make - it sounds like you've chosen to risk losing future contributors to a fork or a new thing instead of changing workflow, and that is absolutely A-OK; however, you then can't complain that the new generation aren't interested in working with you when they do their own thing (and I can find no evidence that you've complained about the new generation not supporting your project, which implies that you're making reasonable choices).