On Tue, Dec 26, 2017 at 11:58:39AM +0100, Rafael Laboissière wrote: > * Rafael Laboissière <rafael@debian.org> [2017-12-24 14:08]: > > > * Sébastien Villemot <sebastien@debian.org> [2017-12-24 10:07]: > > > > > So we probably shouldn’t rely too much on that infrastructure for > > > the moment. But obviously all your preparatory work is going to help > > > a lot when the platform enters production mode. > > > > I thought it was already in production mode. There are loads of > > repositories now at salsa.d.o. > > This is an excerpt of a recent announcement [1] from the salsa team: “We > want to run this beta [GitLab @ salsa.d.o] at least for four weeks. If > everything goes well we intend to leave beta around the end of January.” I > propose that we wait until the service leaves the beta state before > migrating the repositories from Alioth to Salsa. I found an easy way to > automate the migration. Actually, now that the service seems to be in widespread use, I would be ok with migrating now. But of course we can also wait until the end of the beta. > As regards the settings of this “Emails on push” service, I am unsure about > the “Send from committer” option. The default behavior is to have the > sender of the push notifications to be gitlab@salsa.debian.org. In our > current setting at Alioth, the email of the sender is the same as the commit > author. Should we use the same setting at Salsa? I prefer that we use the salsa default (gitlab@salsa.debian.org). I don’t really like the idea of having a robot sending emails with my address (in particular this could increase the probability of having my email classified as spam by some filters). -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
Attachment:
signature.asc
Description: PGP signature