[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Allura/SourceForge to Gitlab migration
From: |
Federico Bruni |
Subject: |
Allura/SourceForge to Gitlab migration |
Date: |
Mon, 09 Apr 2018 18:06:38 +0200 |
Hi
I don't want to revamp this old discussion:
http://lists.gnu.org/archive/html/lilypond-devel/2013-10/msg00095.html
http://lists.gnu.org/archive/html/lilypond-devel/2013-10/msg00140.html
This is just a call for all contributors who are not quite satisfied
with current setup and think that moving to Gitlab "one day™" might
be an improvement.
Current obstacle is that there's no way to import Allura/SourceForge
issues into Gitlab. This is the issue to follow:
https://gitlab.com/gitlab-org/gitlab-ce/issues/45007
If you have a Gitlab account, click on the thumb up icon, as popular
issues should have higher chances to be tackled sooner than later.
BTW, both Debian and GNOME projects moved to Gitlab in the last months:
https://salsa.debian.org/public
https://gitlab.gnome.org/GNOME
In 2013 Janek set up a LilyPond group/organization on gitlab.com:
https://gitlab.com/groups/lilypond
Best
Federico
- Allura/SourceForge to Gitlab migration,
Federico Bruni <=
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, James Lowe, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Carl Sorensen, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09