Re: Q: single-maintainer vs team-maintainance of packages
Sruthi Chandran <[email protected]>
| Newsgroups | gmane.linux.debian.devel.vote |
|---|---|
| Message-ID | <[email protected]> |
On 22/03/26 00:16, Simon Josefsson wrote: > Hi Shruti, > > Do you have any thoughts on the single-maintainer model vs team-based > package maintenance? Yes, I am a very vocal advocate of team-based package maintenance. That may be because most of my contributions are with a well-functioning team like ruby-team. In ruby-team, we have regular sprints, regular housekeeping of packages, team taking care of packages even when the primary uploaders are unavailable, timely mentoring/sponsoring packages etc. > > Do you think anything should change here? If yes, any thoughts on what? 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. > > /Simon
OpenPGP_signature.asc
(application/pgp-signature, 665 B)
-----BEGIN PGP SIGNATURE----- wsD5BAABCAAjFiEEcd3Fxr6GmkZB13n+x+ob4VdN7V0FAmnCzioFAwAAAAAACgkQx+ob4VdN7V1I 4wv/YGIYRtTBVHEMviwU47pX0oDecton9UKgO/k+8gMwUaz7pJtwYxdOKpG8mT1B4mg7dICjBaBY hBI3DX8KeFH7zRokUeTFIxOQqRVfpdHzZZjgRYTCs9nny6uK/0xHmn7Y8zKNWqyxCj2CNGjjfiFc Ez1LsclOIsFZOWeyiRBJovPm+kdWzbkiCWBLKq4vPc6B+YmXA7RH5Oyah5W92WZlGFQN6U5k6qxm DLRCYX871OG1PSQfcHope3YVT04Cd5TWo1rS3kEEoTjWzDCcZM8TjJ342/tISZnzCofNhOVrY/Ld SaeyeELRUzSWnWn4GnA1rglLRSeuQHX9FV5gXPf9C9KM4668EFwIZzV8ttusq8Omk4yMAOjgc21p 3MwYp7Yr+Zh0dojBYKxyxkIdXOrVLTopM6lrRh2wYqRR7Y4A4+t+b5H7xG2a/WJvRjjbcwMK1ZXE hlMlP9d/A5NwKBT76pesgGJVn1Hmbmjk1k2xwi4EdZDvBDRqVCTsIuv+OzkC =2ukG -----END PGP SIGNATURE-----