On 22/03/26 00:16, Simon Josefsson wrote:
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.Hi Shruti,Do you have any thoughts on the single-maintainer model vs team-based package maintenance?
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.Do you think anything should change here? If yes, any thoughts on what?
/Simon
OpenPGP_signature.asc
Description: OpenPGP digital signature
