[Pkg-shadow-devel] should src:adduser, src:shadow and src:base-passwd work together?

[Chris Hofstaedtler]

* Marc Haber <mh+pkg-shadow-devel at zugschlus.de> [241029 11:15]:
> I apologize for letting this rest for more than two months.

No worries. Have limited bandwidth myself at the moment due to
unforeseen occurrences.

> Giving the face that shadow already has its own mailing list, it would probably
> make most sense to unite under the roof of the shadow package.

Agreed.

> Since shadow, adduser and base-passwd are exposed security-wise as well, it
> would probably make sense to move the three source packages from the Debian
> project to its own Salsa project, probably best called shadow-team.

I can kinda see that, but I don't want to do this for util-linux,
and then I'm not seeing the extra value.

In general for Debian I'd like to see more things move into the
debian/ namespace. If people introduce crap -because- of that, then
so be it. They can already (NM)U the packages anyway. I'd rather
take the extra drive-by help.

> We can then decide together whether to move the Maintainer field of base-passwd
> and adduser to pkg-shadow-devel at l.a.d.o as well. Adduser has its Maintainer set
> to adduser at p.d.o, so interested parties can subscribe via the tracker, and
> shadow has its Maintainer set to the mailing list. This leaves base-passwd
> where there currently is no possibility to see maintainer mail like support
> requests, bug reports and other issues.

Using the mailing list would seem like it makes the most sense?
Teams on tracker.d.o are a bit meh at the moment, given tracker
still uses sso.d.o for managing them.
I have no clue how to reconcile the mailing list and the
<package>@packages.d.o alias however. Open to ideas.

Best,
Chris