[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Allura/SourceForge to Gitlab migration
From: |
Karlin High |
Subject: |
Re: Allura/SourceForge to Gitlab migration |
Date: |
Mon, 9 Apr 2018 13:27:34 -0500 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 |
On 4/9/2018 11:06 AM, Federico Bruni wrote:
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.
Which edition of Gitlab should we be looking at for this discussion? Or
are the feature differences irrelevant for LilyPond purposes?
<https://about.gitlab.com/handbook/marketing/product-marketing/#tiers>
<https://about.gitlab.com/handbook/marketing/product-marketing/#open-source-projects-on-gitlabcom-get-all-gold-features>
--
Karlin High
Missouri, USA
- Re: Allura/SourceForge to Gitlab migration, (continued)
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/09
- Message not available
- Re: Allura/SourceForge to Gitlab migration, Urs Liska, 2018/04/10
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/09
- Re: Allura/SourceForge to Gitlab migration, James Lowe, 2018/04/10
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/10
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/10
- Re: Allura/SourceForge to Gitlab migration, Karlin High, 2018/04/10
Re: Allura/SourceForge to Gitlab migration,
Karlin High <=
Re: Allura/SourceForge to Gitlab migration, Carl Sorensen, 2018/04/09