Moving pkg-gnome to Salsa
I imported our pkg-gnome git repos to https://salsa.debian.org/gnome-team
I disabled pushing to the old Alioth repos with a pre-receive hook
that briefly announces the move to salsa.
I enabled the irker integration for IRC notifications of commits
(there aren't IRC notifications for tags or anything else yet) and the
tag pending hook (to mark BTS bugs as pending when a commit is pushed
referencing the bug). I've also used protected branches to make it
difficult to force-push or to accidentally push a patch-queue branch.
For now, I've disabled the wiki and snippets features to make the
sidebar less cluttered. It's easy to turn on in a repository's
Settings > General > Permissions if you want it for a specific repo.
I haven't imported the empty repos from
Update all the Vcs fields and probably do uploads for all our packages again.
If there aren't any objections, we should add our Alioth repos to the
redirect service. 
Issues are also turned off, as per the Salsa default, but we should
have a conversation about that since some of us think it is a useful
CI is available, but we aren't using it yet.
Currently, we aren't importing tags straight from upstream, but we are
using debian/* and upstream/* tags created by git-buildpackage. I
think it would be useful to enable protected tags so that other tags
aren't accidentally pushed, but GitLab doesn't offer an API for this
so it takes time to click all the buttons in the web UI for that for
each repository one at a time. 
In Settings > General > Merge Request Settings, I think we want to
switch to fast-forward merge, but I don't think there's an API for
More documentation should be added to https://wiki.debian.org/Gnome/Git
See the documentation for how to log in to Salsa 
Once there, if you don't already have commit access to gnome-team
repos, you can visit the gnome-team page and request membership.
A nice feature is that permissions can be either group-wide or for
specific repositories. For instance, I gave Developer access to the
Accessibility team for the 5 accessibility-related packages we
Here's a starting point for using the API. I should document how I
used it somewhere too.