> On Dec 8, 2024, at 11:26 PM, Thomas Grainger via Twisted <twisted@python.org> > wrote: > The problem is some people don't want to subscribe to mailing lists, or send > a response if something is breaking, but are happy to subscribe to a GitHub > issue and leave an emoji response. > > The issue should only be for merged breaking changes, not discussion of the > possibility of breaking changes like the mailing list > I guess I'm open to this idea if it's something folks actively want, but as it stands, I would prefer not to do this.
The main thing that it lets users do is engage with the Twisted community even less than they are right now. If we had a big problem with traffic on this mailing list getting to the point of it being spammy, I'd be keen to address that, but if anything we have the opposite problem — very little feedback from users, very little conversation, most of which has been shunted off to specific issues, so it's extremely difficult to get a sense of what's going on. There are really only two cases for notifications of incompatible changes: either you want to be involved, or you don't. If you want to be involved, then you need to be willing to type out a sentence or two when you want to avoid an incompatible change landing. I don't think that emoji reactions are usually sufficient for that level of participation. If you don't want to be involved, i.e. you just want to find out when Twisted has broken an API, at a point past the end of the conversation where it's already been made, then run your tests and see the errors. Simple enough; if you pin your dependencies and upgrade via dependabot or something like it, fix the tests whenever you see a failure and you should be fine. The third case, the one where someone want to be just involved enough to get a pre-notification that they might have to do some work when the next release hits, and then have no recourse but to find some other channel to yell at maintainers to revert already-decided-upon work because that might be easier for them than actually committing to the upgrade, is a kind of user I think we don't want. This is also not really a character flaw from users, it is setting them up for failure, a mode of engagement where the only responses are "nothing" and "toxicity". Anyway, this process is so rarely used that I don't think it bears this many words, but it's worth thinking about user engagement more broadly, and if a change like this were to fit into a more general strategy I'd definitely be interested to hear about it. Much as I wish we had more general conversations about Twisted's development and where it is going, I also have no illusions that mailing lists are the state of the art as far as such things go :). -g
_______________________________________________ Twisted mailing list -- twisted@python.org To unsubscribe send an email to twisted-le...@python.org https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/twisted@python.org/message/LM6FQHOCJAGLGGFVNNHY3L7QNHMHYVR3/ Code of Conduct: https://twisted.org/conduct
