Work in Progress

The service described below is not public, yet. Please ignore any related information until it is officially published.

Even the name (Salsa) is not official, yet.

Salsa Documentation

Salsa is a collaborative development platform within Debian.

Users: Login and Registration

Namespace concepts (Users, Teams, Packages, ...)



Hints for previous users of Alioth

Salsa provides services which partially replace some features of the former Alioth service. The following hints may help you to move your packaging collaboration effort from Alioth to Salsa.

Many Alioth features are (intentionally) not provided by the Salsa platform. You may want to take a look at the related discussion during a sprint for the detailed reasons for this decision.

Import git repository


Import non-git version control repository

Only git repositories are supported by the Salsa platform.

You may want to take a look at the ?reasons for not supporting other version control systems within Salsa.

Import mailing list

Salsa does not offer any mailinglist features on its own (see ?discussion).

Some mailing lists that were formerly hosted on Alioth may be eligible for being hosted on The lists eligible for migration must follow the requirements outlined on the "How to ask a mailing list" guide. The process is also the same as outlined on the guide.

The following kind of lists are probably acceptable for

Short version: file a bug on the pseudo-package with the severity 'wishlist', with the following information:

Lists migrated from Alioth are expected to be open, that is:

If you do want the archive and/or the subscribers to be imported into your new mailing list, please:

Also, please understand that the requirements and features for lists on are not the same as for a mailing list on Alioth, and the listmaster might reject your request. is not supposed to replace all mailing lists and aliases on Alioth.

Import members of a team

It is not possible to transfer the members of an Alioth team to Salsa. You will need to ask the members of your team to join your team on Salsa individually.

Host project web pages

Gitlab offer the "Gitlab Pages" feature, and it is enabled on Salsa both as<namespace>/<project> or http://<namespace><project>

This feature makes use of Gitlab-CI to generate static pages in a public directory, on every push.

See for a detailed documentation and HOWTOs.

Should you want to access the pages with your own domain name and your own certificate, it is possible via 'Settings > Pages > New Domain' in your project.

Quick start

  1. On your project Home, use Set up CI button

  2. Choose a Gitlab CI Yaml template (Pages templates are at the end)

  3. Edit the template to suit your needs and save it
    • Note: To limit the load on Runners, we limit the actual runs on projects tagged with "pages". So you need to add it to your .gitlab-ci.yml:

          - pages
  4. Push something to the repository. You will see there is a CI Job pending
  5. Wait a few minutes for the job to run. When it's Passed you can see your pages at<namespace>/project (or http://<namespace><project>/)

    • Note: in most cases, you should content yourself with the HTML template, and generate the pages locally to push them afterward, in order to save the ressources on the runner. Some templates might require commands not available on the server anyway.

    • Note 2: We mean that. Really. Be nice to the server. At some point in the future we hope to add some dedicated Runners servers - Sponsors welcome! ;).

Getting Help

See the Salsa maintenance description.