Re: Q: single-maintainer vs team-maintainance of packages

Hello,

you asked.

On Tue, Mar 24, 2026 at 06:47:22PM +0100, Sruthi Chandran wrote:
>I know all the teams are not as functional as ruby-team, but I still 
>think a group of people responsible for a package is better than a 
>single point of failures. I think it is high time we move to 
>team-maintenance. Having said that, I would like to hear what people 
>who prefer single maintainer model have to say.

I think that Debian should not force people maintaining packages to do 
anything. There are people who are emotionally challenged to which 
extensive communication with others is a burden.

I do maintain most of my packages alone and I find that okay. For sudo, 
there is a team with me doing like 95 % of the work which I am also okay 
with. It feels very good to have people to talk to if I have questions 
(and I have lots).

Adduser, on the other side, I would love to have team maintained. Are 
you planning to fine me because I have failed to assemble a team around 
adduser? Or what do you have in your mind to make people do team work if 
a team fails to form?

Will I get people assigned to help with adduser? Who is going to manage 
those non-volunteers?

Team maintainance is a good thing. But forcing or requiring it is not 
going to work. Don't assume that there are people queuing up to 
co-maintain packages.

Greetings
Marc