Re: Plannings for secure-testing repository migration to git
Hi
On Tue, Dec 26, 2017 at 03:43:38PM +0100, Moritz Mühlenhoff wrote:
> Hi,
>
> > FTR, so now that the beta for salsa.d.o has been announced I started
> > to look on what further is needed and recorded further findings in
> > TODO.gitmigration.
>
> Thanks for looking into this.
Very welcome, I did made some progress today.
> > I suggest to as well create a new namespace and project name away from
> > secure-testing, namely use 'security-tracker', any objection to that?
> > The project can be shared with the Debian group, so any DD will get
> > automaticly write access to the security tracker. -guest users will
> > first need to create an account and then be added.
>
> Sounds good to me.
Ok I have done so, there is a security-tracker-team group, and below
that a project (aka. repository security-tracker) which will be the
converted git repository for the security-tracker.
> > On Sat, Oct 21, 2017 at 03:04:42PM +0800, Paul Wise wrote:
> > > On Fri, Oct 20, 2017 at 11:37 PM, Salvatore Bonaccorso wrote:
> > >
> > > > What we would desire is to keep the possibiltiy to keep the commit
> > > > mailinglists which is often used in team members commit review
> > > > processes.
> > >
> > > IIRC the folks who are working on the migration have said that commit
> > > lists will be replaced with gitlab's commit notification features.
> >
> > Apart the notification feature, there seem to be as well a 'mail on
> > push' feature, which matches our need at least for the sectracker
> > user. Personally I still would have appreciated a commit mailinglist,
> > since at least Moritz' and mine's review work was done that way so
> > far. But I realize no option in this direction arised.
>
> How can it be configured who receives a mail on push? Is that a per
> user setting?
That needs to be done by a project owner and is just a list of email
addresses to be forwarded the push notices via mail. Ideally there one
adds a commit mailinglist if we can have that.
sectracker role account defintively needs to recieve those either
directly by listing the user there or by having it subscribed to the
commits mailinglist.
Regards,
Salvatore
Reply to: