Project hosting going bad - do we need to act?
As you may have seen, GitLab.com is changing the T(Q?)oS:
Changes to free tier public projects
- Effective June 1, 2022, all free tier public projects will be included in the CI/CD quota of 400 minutes per month.
This is less than two weeks away. We use the CI runners for spell checking and publishing of the editor's copy of the draft. Each job takes one to two minutes, to this amounts to anything between 200 and 400 CI jobs, which I think is plenty.
If we run into this limit, I'm happy to volunteer our CI runner for this project.
- Before July 1, 2022, all free tier public open source projects must enroll in the GitLab Open Source Program to continue to receive GitLab Ultimate benefits.
This is less than six weeks away. Whether we get the spec out of the door by then is anyone's guess.
AIUI there are two options with different consequences:
- Not doing anything. This will restrict the number of active participants to five. Maybe the doc has settled down enough by then that this isn't an issue. Also, AIUI, you can juggle participants in and out of the over-limit status. Still, might be annoying.
- Applying for GitLab’s Open Source program. There is a weird non-profit clause in that. IANAL of international law, but a pessimistic interpretation may exclude all implementers in this group from participating.