On Saturday, August 3, 2024 1:37:42 PM MST Salvo Tomaselli wrote: > > 2. Standardizing around a single (or small number of) workflows will make > > some people unhappy. But that is an acceptable price to pay because of the > > general benefit to the project *as long as the correct solution is > > adopted*. Unity is more important than minority opinions on this > > particular issue. > > Keep in mind that unhappy people quit. > > I don't think that unity is so important that we're willing to sacrifice > project members.
Yes, but based on my work helping new contributors start working on Debian, I think the number of people the project would gain would far exceed those who would leave. > What exact issue are we trying to fix? The core of the issue is that it is far too hard for a new contributor to figure out how to contribute to Debian, and far too hard for an experienced DD to figure out how to contribute to a package that is based on a workflow with which they are not familiar. > At the bottom, is it ok for a package to have a single maintainer or not? Yes, as I have written elsewhere, I am a proponent of a strong package maintainer orientation. However, even single maintainer packages periodically need input from other developers, either as an NMU or as an adoption or because of a mass bug report or a transition or various other things. Having one workflow that everyone understands is a strong benefit for all packages, whether or not they are team maintained. > If as a project this has to change, I think a vote is warranted. Absolutely. This is such a core aspect of Debian that any changes or mandates would need to involve a vote. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
