Re: Alioth → Salsa
- To: debian-perl@lists.debian.org
- Subject: Re: Alioth → Salsa
- From: Dominic Hargreaves <dom@earth.li>
- Date: Thu, 8 Feb 2018 12:34:46 +0000
- Message-id: <[🔎] 20180208123446.kf2ol2hw5alefv5u@urchin.earth.li>
- In-reply-to: <20180127160506.mzap2vd3yq5ljbui@jadzia.comodo.priv.at>
- References: <20180122182844.zorckm6fq32ke2a7@jadzia.comodo.priv.at> <20180125205835.l2zgyc447wmwv4sa@jadzia.comodo.priv.at> <87fu6tfy4k.fsf@fifthhorseman.net> <20180125212200.vnxks5rhx34bizl2@urchin.earth.li> <20180126223439.hfa4lc6nwdbasyz3@ktnx.net> <20180127085153.GA20869@estella.local.invalid> <87lggjabxm.fsf@delenn.ganneff.de> <20180127130010.q56mnbmayraejcyp@urchin.earth.li> <20180127130927.GA21931@estella.local.invalid> <20180127160506.mzap2vd3yq5ljbui@jadzia.comodo.priv.at>
On Sat, Jan 27, 2018 at 05:05:06PM +0100, gregor herrmann wrote:
> On Sat, 27 Jan 2018 15:09:27 +0200, Niko Tyni wrote:
>
> > On Sat, Jan 27, 2018 at 01:00:10PM +0000, Dominic Hargreaves wrote:
> > > On Sat, Jan 27, 2018 at 10:27:49AM +0100, Joerg Jaspert wrote:
> > > > In a group structure of
> > > >
> > > > perl-team
> > > > modules
> > > > interpreter
> > > >
> > > > anyone who is granted access to perl-team will have the access copied to
> > > > any subgroup, ie modules and interpreter. Anyone with access to modules
> > > > will have it only there, not in interpreter. And also, anyone with
> > > > access in perl-team can have different access in a subgroup, but that
> > > > needs to be explicitly set.
> > >
> > > Sounds like this can definitely work then. I'm fine with this arrangement;
> > > it seems the neatest to me.
> >
> > Yeah, sounds good to me as well!
>
> Thanks for your help, Ganneff, and Dom&Niko for your approval.
>
> There's one detail left where I'm not sure how to handle this
> structure- and permissions-wise. Quoting from my first mail in this
> thread:
>
> currently we have
> + meta.git
> + website.git
> + scripts.git
> + packages/
> lib.*-perl.git
> ...
> + attic/
> lib.*-perl.git
> ...
> + do we want to keep this structure? probably yes;
>
> So besides a subgroup ("packages" →) "modules" and the new
> "interpreter" subgroup we currently also have some more repos and a
> directory ("attic"). And we probably want a system where permissions
> are separate for "interpreter" on the one hand and everything else on
> the other hand.
>
> If we more or less keep the structure as above we could add
> members/permissions for "perl-team" but then would have to lower
> permissions for interpreter explicitly; or we'd have to add members
> for "modules" and "attic" and whatnot separately. Sounds a bit
> complicated and error-prone.
>
>
> Or maybe we throw everything under "modules" except "interpreter":
>
> group perl-team
> subgroup interpreter
> project perl.git
> subgroup modules
> subgroup packages
> project libfoo-perl.git
> project libbar-perl.git
> subgroup attic
> project libbaz.git
> meta.git
> website.git
> scripts.git
>
> Maybe a bit complicated with many levels but then we can set
> permissions as in Ganneff's mail, and after all it's just about paths
> which are consumed by scripts ...
Sorry for the delay in responding to this point. "scripts" contains
things relevant to the interpreter pacakging too, sort of. So could
be a top-levl thing. Maybe website too, though that presumably depends
on how it will be used with gitlab pages.
Dominic.
Reply to: