My main reason for prefering /debian/ wasn't about permissions, it was about trying to reduce the URL churn. Moving between XMPP team, Authentication team, Security team, etc changes the Salsa URL but there is no strong gain from that move. The strongest argument seems to be that "it looks nicer", some notion of consistency, and the Salsa permission issue (which is also just a "it looks nicer" thing), which I can sympathize with. But compared to the cost of changing URLs once every five year depending on which group happens to be healthy, I don't think it is worth that cost any more. If there was a collaborative package maintainer team that was all-inclusive, that would fit better with how I would like to work. Since the Authentication Team has not had a lot of team spirit to it, I slowly want to move all packages I care about out of it, but finding an appropriate place for it isn't all that simple since all teams seems to have specific requirements that doesn't hold underversally. So take this as a mild plea to allow use of /debian/ namespace for packages maintained by pkg-security. /Simon tor 2025-02-13 klockan 09:36 +0100 skrev Raphael Hertzog: > Gah, Samuel's reply broke the thread and I missed his reply. You > might have > seen my other suggestion elsewhere. Romain did not particularly care > of > the exact location and I think Simon's suggestion was somewhat ill- > advised > as putting them in /debian/ is not required to make it open to all > DD. > > On Sun, 09 Feb 2025, Carlos Henrique Lima Melara wrote: > > Well, as a compromise between both approaches, we could create a > > subgroup under debian/ namespace so we could inherit debian's > > namespace > > benefits and have a way to look at our subgroup's Merge requests, > > issues > > and everything else. Maybe we could even move pkg-security-team to > > debian/pkg-security-team easily (not sure if gitlab supports it > > though). > > Moving groups is possible AFAIK but that's even worse in terms of > complexity > and impact on contributors. The right way to do this if we want to be > open > to all DD by default (and yes I think this is quite OK), is to use > the > "Invite a group" feature on > https://salsa.debian.org/groups/pkg-security-team/-/group_members > and invite the debian group to have "Maintainer-level" access to the > pkg-security-team group. > > I think we can decide this relatively quickly, I don't think that it > needs a > huge discussion. > > Cheers,
Attachment:
signature.asc
Description: This is a digitally signed message part