Re: salsa.debian.org (git.debian.org replacement) going into beta
- Date: Tue, 26 Dec 2017 13:01:34 +0000 (UTC)
- From: Felipe Sateler <fsateler@xxxxxxxxxx>
- Subject: Re: salsa.debian.org (git.debian.org replacement) going into beta
On Mon, 25 Dec 2017 11:45:37 +0100, Alexander Wirt wrote:
> Since summer we have worked on our git.debian.org replacement based on
> GitLab. I am really happy to say that we are launching the beta of our
> service today. Please keep in mind that it is a beta, we don't expect
> any database resets, but under unexpected circumstances it might still
> The new service is available at https://salsa.debian.org. Every active
> Debian Developer already has an account. Please request a password reset
> via https://salsa.debian.org/users/sign_in -- your login is either your
> Debian login or Debian e-mail address. SSH Keys from udldap get synced
> into your account.
Thank you very much for your work. It is very much appreciated.
> If you want to allow other Debian Developers to work on your packages or
> software, you can create projects within the **Debian** group. Every
> Debian Developer has write access to projects created in this group.
> If you create a project within the Debian group, you are implicitly
> welcoming all DDs to contribute directly to the project.
> Guest users can only be added to individual projects with the Debian
> group, but not to the entire Debian group. This is different to the
> policy for the collab-maint group on Alioth.
Also note that currently the permissions set up for the debian group
allow debian developers to create projects but not delete or transfer
them. When experimenting it's better to do so in you own namespace.
> GitLab runners
> We won't provide any shared Gitlab runners for now. If you want to
> sponsor resources for such runners please contact us.
Note that setting up a runner is fairly easy, so if you have spare
resources firing up a gitlab-ci-runner and hooking it into your projects
It would be awesome if someone could somehow integrate autopkgtest with
the CI runners, especially if that can be done via the autodevops feature.
> Migration of repositories
> We don't plan to do any automatic migration of alioth repositories. If
> you use a repository and think it is important (!)
> migrate it on your own. We will provide a read-only export of all
> repositories that weren't exported after disabling alioth.
For those not following planet, Christoph Berg published a handy import
script that can be used to automate the migration: