On 21/02/2022 20:44, Glyph wrote:
I’m in a similar place myself. I could probably put more effort forth if
we could get a bit more of a small commitment from more other
developers. I do not want to spend my time as a full-time unpaid
twisted maintainer, or simply slogging through reviewing old tickets
while never developing any interesting new features myself.
Heh, have the tickets auto-close after 30 days... While I find this
infuriating myself, it's certainly effective triage and a lot of python
projects with a high ratio of users to maintainers are doing it.
If an issue is hitting a lot of people, it'll get re-raised soon enough ;-)
It makes me wish we could have a sort of open source mutually-assured
maintenance system, where we all put in some number of hours and get
some small reward (like bragging rights, a little badge?) out of meeting
that commitment. But that also requires some volunteers[1] to go build it.
This trial maintenance is also something I’m definitely interested in,
but I don’t think /just/ a small commitment from me and JP would be
quite enough to get it somewhere meaningful.
Speaking just for myself, my problem is that while I respect Twisted and
really heavily hammer it while being massively impressed how it behaves,
I don't enjoy working on the code base :-/
I've yet to hit a "bug that I need to fix" in the 4 years since I came
back to Twisted, and that's a massive testament to the quality of the
software...
Chris
_______________________________________________
Twisted mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/twisted.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/6T3KH5SC36FZENUPBHJPZLCCAC3GN2LB/
Code of Conduct: https://twisted.org/conduct
