Re: gitlab subscription expiring

Jonas Hahnfeld via Discussions on LilyPond development <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.devel
Message-ID <[email protected]>
On Fri, 2025-06-20 at 19:22 +0200, Han-Wen Nienhuys wrote:
> I saw the following on logging on to gitlab,
> 
>  Your Opensource subscription will expire on 2025-07-01
> 
>  Your Opensource subscription for LilyPond will expire on 2025-07-01.
> If you do not renew by 2025-07-15, you can't use merge approvals, code
> quality, or any other paid features.
> 
>  [Renew subscription][That's OK, I don't want to renew]

Yes, sorry for being a bit slow this year in renewing. I started
receiving emails two months ago, but as you noticed the automatic
renewal didn't work and I had trouble finding time to look further into
the topic...

> do we use "merge approvals"?

FWIW I think the one paid feature we use are scoped labels:
https://docs.gitlab.com/user/project/labels/#scoped-labels We could
probably live without it for the merge requests (Patch::review,
Patch::push etc.) and have the bot take care of mutual exclusive
labels, but somebody (tm) would need to code that.

> I tried renewing the subscription, but it fails with:
> 
>   Your group contains project(s) without an open source license.
> Projects that don't meet the requirements: LilyPond / GUB, LilyPond /
> lilypad, LilyPond / lilypond-extra, LilyPond / static-files.

Note that the first three projects are archived. The first two are
open-source, they would just be missing the LICENSE file. The last two
have some PDF files that I don't think we can license under an OSI
approved text - to be checked for next year because ...

> options:
> * add LICENSE files to the above repos; renew subscription
> * ignore this, and let the subscription run out.

option 3: ask the GitLab for Open Source Program Team and have them
send over a coupon code - thank you! I received the email earlier this
evening, just as I was about to leave. I entered it now, we should be
all set until July next year.

Jonas
signature.asc (application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQRiF4DLRvon1vw5biCcVOmY/6OEDwUCaFXc+wAKCRCcVOmY/6OE
D6UqAP465W2z2U6sEa6aiXJEFlp8ZAwl8YAYek7VJRXkV9G5dAEAj5jhmM+cVcXD
T2sN/skSYF7V2xFyKYajgQdGFzsk1Ao=
=K6rd
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.