Hi, On 6/22/24 04:40, Russ Allbery wrote:
I am frequently told that Debian is a do-ocracy: the people who are willing to do the work have wide latitude over how that work is done. One of the implications of that is that delegates don't get to force other people to do their work in arbitrarily different ways just because they would personally like that better.
Yes, but the delegates are *also* doing work, and have wide latitude over how that work is done, and one of the implications of that is that people contributing to that work do not get to force them to do their work in arbitrarily different ways just because they personally like that better.
The difference is the expectation that the delegates will continue to perform this work and therefore need to deal with the long term impact. One-time contributions are welcomed as long as they are a net positive, but not all of them are, and some take up hundreds of hours of volunteer time several years down the line.
Because of that, I would give them a veto over short-term "solutions" that solve one particular problem but that the domain experts understand will cause other issues down the line, or conflict with other requirements.
Deploying tag2upload *as a service* is an ongoing commitment, which means creating a new delegation, or altering the scope of an existing one. We need to be explicit which one it is.
There is an obligation that comes with the delegate position to only block things for clear and important reasons that matter, and to do that, one also has to be *correct*.
Maintainability matters, and the onus for coming up with a maintenance plan is on the person proposing the change.
Simon
OpenPGP_0xEBF67A846AABE354.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
