Hi Simon, Quoting Simon Josefsson (2026-03-24 23:07:31) > I share your reaction, but also: please don't assume poeple will NOT > randomly appear if there is a team around packages. You don't > necessarily need to do anything beyond changing the 'Maintainer:' field. > > I believe the rust/python/go/ruby/etc teams in Debian all prove, to some > extent, that merely having a team around packages somehow leads to a > dynamic that make people appear and contribute. > > I believe the lack of contribution to single-maintainer packages can be > attributed (again: to some extent) to the fact the package is perceived > to be "owned" by a single individual.
Do you have any concrete experiences with simply changing the Maintainer field and that lead to more contributors? I have tried that approach but have not experienced it attracting any contributors. > I maintain some packages (e.g., cppi, git-merge-changelog, gnulib, > git2cl, gnulib-l10n, xe) where team-maintainance would be higly > appropriate and welcome, but I'm not aware of any existing team where > the packages naturally belong. Maybe the situation is the same for > 'adduser'? I don't fancy launching any new team, as my experience with > small teams is poor and I try to reduce the number of teams (e.g., > pkg-authentication, pkg-privacy, debian libidn team) rather than create > more. Oh, I am confused now. Do you not suggest to simply change the Maintainer field to a *new* team? When you talk about people randomly appearing, do you then somehow mean them "randomly appearing" by you moving your package to their already existing team, or what approach are you describing? Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
