Re: Plannings for secure-testing repository migration to git
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.
As said, the conversion of the svn repository is just one part, and
this has been done and then later can be imported.
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.
For the automatic updated of the sectracker user i was pointed to the
'deploy keys', so we do not need to enable a role account in salsa.
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.
I will report back in the next days further updates.
I write mainly this mail as well since there was hardly no feedback on
my original mail, I would appreciate to hear concern, ideas, comments
from both main involved teams (security, lts).
Regards,
Salvatore
Reply to: