On 17/08/25 at 15:26 +0200, Andrej Shadura wrote: > Hello, > > On Fri, 15 Aug 2025, at 13:37, Lucas Nussbaum wrote: > > This package has a strange state. > > It has > > Uploaders: Debian Ruby Team > > <[email protected]> > > but > > Vcs-Git: https://salsa.debian.org/debian/git-bump.git > > > > I think that it should either be fully maintained by the Ruby team (and > > thus moved to the ruby-team salsa group, and follow the usual Ruby > > team's practices), or be maintained outside the Ruby team (and do not > > mention the Ruby team in Maintainer/Uploaders). Both options are fine, > > but the current status isn't. > > When I set the fields into the current state, I thought it clearly > communicated the idea. I can see that probably is not the case. > I’m the package maintainer. The Ruby Team is set as a co-maintainer, i.e. > members of the team can modify the package when there’s some important issue > and I’m not around without asking me first. Since the team is not the primary > maintainer, the package lives in the Debian namespace on Salsa. > > I don’t see how this status is problematic. Is it?
The problem I encountered with it is that I was doing some (consensual, I think) changes over all packages maintained by the team, such as making sure that CI is enabled and configured consistantly. In that context, ruby-git-bump falls in a strange category, and I'm not sure what I should do about it: push team standards to that package as well, or assume that the role of the team is limited to fixing important issues, and thus leave it as it is? Lucas
