Hi, First of all, thanks for pushing this! On Tue, Dec 26, 2017 at 04:42:13PM +0100, Christian Hofstaedtler wrote: > * Pirate Praveen <praveen@onenetbeyond.org> [171226 16:29]: > > On 12/26/2017 08:28 PM, Chris Hofstaedtler wrote: > > > Hey *, > > > > > > Hope your holidays have been going well. > > > > > > As you're all hopefully aware, Alioth has an expiration date [1]: > > > 2018-05-01, with incoming mail service ending 2018-02-01. > > > > > > Therefore we must take action soon, on at least these two topics: > > > > > > 1) provide a working mail adress in the Maintainer field. > > > > > > Right now, most packages have this set: > > > Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org> > > > > > > The only option that I know of is to replace that with > > > debian-ruby@lists.debian.org. Needs an upload of all packages > > > in any case (before 2018-02-01 preferably). > > > > I'd prefer if tracker.debian.org allows creation of teams [1] though it > > is only in discussion stage. I'm worried about the volume of mails, but > > if that is the only option, we may have to go for it. > > For now this appears to be our only option. Although I'd suggest not > sending VCS infos by mail anymore. This would leave us with bugs > only... > > > > > > > 2) git hosting > > > > > > Apparently we have about ~1300 git repositories on alioth. > > > > > > I see two options here: > > > > > > a) migrate to salsa.debian.org, under a new debian-ruby group. > > > Would need to request that group from the salsa admins. > > > > I prefer ruby-team and -team is the normal choice (javascript team > > already created js-team). > > Right. So before reading this I've gone ahead and got us > https://salsa.debian.org/debian-ruby IMO the "debian-" is a little redundant, so I would rather go with just ruby or ruby-team > >From what I see we could also have gotten ruby-team or just plainly > ruby (see qa, postgresql teams). > I think we can get another rename, but then we should really know > what to :) > > > There is a batch import script which we could use [2]. > > Indeed. > Well, once we actually move over, we then have a few things to do: > > a) actually add all users to the team actually now that we will have a decent contribuiton workflow, you don't necessarily need to have everyone who is in the alioth team on the gitlab group. I would rather have only people who can actualy do uploads (i.e. DD/DM), and have everyone else to contribute via pull requests etc. This way we will have code reviews a priori, instead of after the fact. IMO we could use the code review features in gitlab even when the person writing the code is a DD/DM, but that's maybe a different conversation. > b) stop using git on alioth. Not sure we can set stuff to R/O there. yes. you can write a pre-receive git hook that prints a message and returns non-zero. that would effectively make the repositories readonly. > c) update make-mrconfig and so on > d) ??? We need to figure out the new maintainer email address. I think we will only know what are the alternatives in a couple of weeks. I think we can keep using the current one before that.
Attachment:
signature.asc
Description: PGP signature