The GitLab for Open Source program was created because GitLab believes in a world where everyone can contribute and we like to support those who share our mission.
Public open source projects requiring GitLab Ultimate features will need to be part of the GitLab for Open Source program as a result of changes to our free tier. Those changes include:
Free tier public projects will no longer receive Ultimate by default and must apply for Open Source program to continue benefits.
Public projects will be included in the CI/CD minutes quotas of 400 minutes for free users.
A detailed frequently asked questions document outlines the upcoming changes and how you can manage the changes to your free GitLab SaaS account.
In order to publish your feedback regarding this change, please add a reply to this thread.
Thank you very much for taking the time to provide us with your perspective. Please allow our Product Team some time to review the input you add here.
@sugaroverflow How does one chase up an application to the GitLab for Open Source program? I completed the process (on behalf of our community organisation) a number of weeks back but still havenāt received a response.
Hello @myii - Thanks for reaching out. I just replied to your email as well. Your application was marked as expired in our queue (not entirely sure why yet). Weāll take a look at it today! Thanks for your patience and interest in joining the GitLab for Open Source Program.
Thanks, @chupy. I did get an e-mail, which I responded to last Friday. I havenāt received a response since then, so Iād appreciate it if you could have another look.
Reading the FAQ, I would ask for clarity on the following point
Q. I am an active contributor to GitLab. Will the same limits be applicable to me as well?
A. All free tier users receive 50,000 CI/CD minutes for running pipelines on public forks of public open source projects, like GitLab. Contributions to all other projects by free tier users are subject to the new limits
When this refers to āopen source projectsā, is this meaning all public projects under an open source license, or is it only meaning those subset of open source projects who have chosen to join the āGitLab for Open Source Programā ?
Iām hoping it refers to the former, because I suspect many (possibly even most) smaller scale OSS projects arenāt going to jump through the hoops to join the special Program.
Iām pretty sure it means you would have to be registered with the Open Source program. Otherwise everyone could claim open source and abuse all the minutes and Gitlabās platform - just like when people were crypto mining and killing all the shared runners.
I have a couple of questions before I apply to the program on behalf of our community.
1- One of our projects has a dual license Apache 2.0 AND BDS-3-Clause (both OSI approved),
with 2 license files, GitLan shows āOtherā in the overview.
I unsuccessfully tried different things to make GitLab identify both licenses, so I can take the first screenshot of the project overview, the only workaround I found was to concatenate both files in one LICENSE file but GitLab only identify the Apache 2.0 license, itās that ok?
2- Also a project in the same namespace, is the website HTML code of the project (using a GitLab Page), its license is CC-BY-SA-4.0, which is not listed as OSI approved.
Could this be a problem when applying for the Open Source program?
Thanks for sending along your questions. I am happy to help. Iāll address each one below.
1- One of our projects has a dual license Apache 2.0 AND BDS-3-Clause (both OSI approved), with 2 license files, GitLan shows āOtherā in the overview. I unsuccessfully tried different things to make GitLab identify both licenses, so I can take the first screenshot of the project overview, the only workaround I found was to concatenate both files in one LICENSE file but GitLab only identify the Apache 2.0 license, itās that ok?
Thanks for bringing this to our attention, and for your kind offer to concatenate the files. But that wonāt be necessary. When you apply, simply choose either license to screenshot and weāll take it from there.
2- Also a project in the same namespace, is the website HTML code of the project (using a GitLab Page), its license is CC-BY-SA-4.0, which is not listed as OSI approved.
Youāre correct that Creative Commons licenses arenāt OSI-approved; however, as the CC-licensed project is among many other projects in your namespace that are carrying OSI-approved licenses, I feel confident saying this wonāt be an issue for your enrollment in the GItLab for Open Source Program. Weāll know for sure when weāre able to review your application.
I hope that helps! Looking forward to seeing your application.