Thanks everyone for the details, and especially aviau for getting the technical bits sorted out.
Let’s also consider the social aspect of this migration, though. I suggest we send out an announcement regarding the migration timeline and expected impact. More specifically: • Please outline how one can easily update their git working directories to switch to the new remote address. Perhaps there is a git or sed oneliner we could use? • Let’s give people at least 7 days notice to activate their account on GitLab, and to voice any feedback or concerns they might have regarding the migration. • It might be good to send a targeted reminder to people who are in the pkg-go team on alioth, but not yet on GitLab. I’d be happy to review any draft announcement you come up with. Thanks! On Tue, Jan 16, 2018 at 10:00 PM, Joerg Jaspert <jo...@ganneff.de> wrote: > On 14919 March 1977, Michael Stapelberg wrote: > > How do we ensure that people are redirect from alioth to salsa? I think > > some redirection support is underway or already working, so it would be > > good to set up these redirects. > > MergeRequest in https://salsa.debian.org/salsa/AliothRewriter > > > Redirects only cover the web interface part, so what do we do with the > old > > git repositories? Could we mark them read-only, to prevent accidental > > pushes to the wrong repository? > > Yes. Thats the common way. > > -- > bye, Joerg > -- Best regards, Michael
_______________________________________________ Pkg-go-maintainers mailing list Pkgemail@example.com http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers