Latest news


Today we enabled project imports from GitHub. Should you want to import your project (which should import both the repository and the issues) into gitlab, please check out gitlab documentation for the github import workflow.

As part of the effort to enable GitHub imports, we had to do a minor GitLab upgrade. The current hosted GitLab version is now 7.9.1.

Another part of enabling GitHub imports was to allow users to log in on our site using their GitHub credentials. Please note that this will only work for those who already have a valid (i.e. pre-existing and confirmed) GitLab account. If you want to use this option (which is also available for Google accounts), please check the GitLab omniauth for existing users documentation.


GitLab upgraded to 7.9.0. GitLab released its newest version (7.9.0) on the Sunday after the Friday we went live with our self-hosted GitLab (7.8.4 -- then latest). The release contains a large number of fixes and enhancements.


Our self-hosted git repository management environment is now live! During the deployment, the system was seeded with 390 users, 434 groups and 210 repositories.

The deployment itself took little over an hour, while we were able to resolve the issues we identified after completion well within the migration timeframe of 4 hours. During this time, most services were fully available. Only SSH has been impacted shortly.

If you experience any issues, please report to the site admins.

We hope you enjoy the new user experience!


Today the date has been announced for the final migration of all git repositories to GitLab: Friday March 20th!


While testing the seeding scripts for the new GitLab site, a number of e-mails to live users have unintentionally been sent instead of held.

The content of the messages suggests one may be able to log in on the system. When trying so, the system denies access. This is a side effect of the testing setup. In the final migration run, you will receive an account confirmation mail. A mail not distributed in the test-run. Once the account is confirmed, the system will allow changing passwords and logging in.

We're sorry for any inconvenience caused.


The site admins have announced a change in policies for the mailing lists to be in effect as of March 15th, 2015. Please read the original announcement e-mail for details.

In summary, there are two changes being implemented:

  1. Subject prefix '[<mailing-list>]' won't be added anymore.
  2. Moderation requests won't be held indefinitely anymore, defaulting to a hold period of 90 days (expiring the unmoderated e-mail when unhandled).

The former addresses problems with delivery of DKIM signed mail being sent through mailing lists. Changing the message headers and body may invalidate any prior DKIM signatures, leading to mailing list e-mail looking suspect to large mail receiving providers like Google and Yahoo!.

The later addresses the fact that the moderation queue is growing indefinitely, with most lists set to never expire moderation requests.


The site admins identified a list of mailing lists for which contact with the list owner has been lost list for your favorite list or your name.


Due to a failed system upgrade, the system experienced extended downtime on Sunday. Our apologies for any inconvenience.

The maintenance was completed successfully around 18.00 UTC and is a step towards easier maintainance for the system and support the development of new and simplified configuration.


Erik Huelsmann -one of the maintainers- has submitted a proposal for the nearby future of the site. Read the details in his mail to the clo-devel mailing list in the archive. Feedback is very much appreciated.


The (www.) domain has started using the https protocol for all its URLs. In the weeks to come, the various sub-domains will be switched too. This change has been made in response to user requests. Should you have a request too, please let us know on the mailing list!


The mail system's criteria for accepting mail have been tightened and mail forwarding now uses SRS when the sender domain specifies an SPF policy. The changes address these issues:

  • too many spam mails entering the moderation queues
  • improved reputation of the domain at Google

Google considers a Bulk Sender, which means we must abide by a number of requirements to make sure mail gets accepted.

Some of the stricter criteria to accept mail on are:

Mail failing SPF validation is no longer accepted
Due to the SRS rewriting, these mails would leave as legitimate mail. By rejecting these mails, we honor the policy stated by the sender domain.
Note: We're currently not rejecting soft-failing mails.
Mail failing DKIM validation is no longer accepted
Forwarding mail which fails DKIM validation reflects poorly on's reputation as a mail host. By rejecting mail failing DKIM validation, we honor the policy stated by the sender domain.
A series of requirements on the host submitting mail
By enforcing a number of requirements on the DNS configuration and protocol conformity of the hosts submitting mail to, we enforce the same requirements that Google and other mail hosters enforce on us, can't be used as a hub by spammers to increase legitemacy of the mail flow. Nor can accidental forwarding of spam mail hurt's reputation with the large mail hosters.


Hello everybody. The site moved to a shiny new server a few moments ago. Everything should work, and if it doesn't, please let us know.

You can also help us by donating.