Implications of change in GitLab free-of-charge tier limits?

julianstirling · May 16, 2022, 2:05pm

Remind @julianstirling to make the damn pull request each week he fails to do so

hpy · May 16, 2022, 2:05pm

Haha OK, that I can do.

hpy · May 23, 2022, 4:36pm

Hi @julianstirling, as you requested I’m responding to this thread to check on the status of the pull request.

julianstirling · May 23, 2022, 8:31pm

Thank you, status is “did not percolate to top of todo list, nor was achieved as procrastination from those items at the top of todo list”.

hpy · May 23, 2022, 8:33pm

Haha fair enough, story of my life…

julianstirling · June 13, 2022, 8:21am

It turned out to be more work than expected as we needed examples and we needed some automatic tests to pass. Divided work between @Javier and myself, and someone we don’t know had already got us started. In true open source fashion we built on their start, and had a helpful conversation with the maintainer.

The pull request is not yet merged, but the automatic tests are passing!

github.com/github/choosealicense.com

Add cern ohl v2

github:gh-pages ← julianstirling:add-CERN-OHL-V2

opened 04:59PM - 10 Jun 22 UTC

julianstirling

+849 -0

This PR contains all the commits from #854 adding the CERN-OHL v2 family of lice…nses. (See also the discussion in issue #853) This remains a draft whilst we check and tweak the "how" field ## Requirements ### 1. The license must have [an SPDX identifier](https://spdx.org/licenses/). If your license isn't registered with SPDX, please [request that it be added](https://spdx.org/spdx-license-list/request-new-license). * [CERN-OHL-P-2.0](https://spdx.org/licenses/CERN-OHL-P-2.0.html) * [CERN-OHL-S-2.0](https://spdx.org/licenses/CERN-OHL-S-2.0.html) * [CERN-OHL-W-2.0](https://spdx.org/licenses/CERN-OHL-W-2.0.html) ### 2. The license must be listed on one of the following approved lists of licenses: * [CERN-OHL-P-2.0](https://opensource.org/CERN-OHL-P) * [CERN-OHL-S-2.0](https://opensource.org/CERN-OHL-S) * [CERN-OHL-W-2.0](https://opensource.org/CERN-OHL-W) ### 3. The license must be used in at least 1,000 public repositories. This may be documented, for example, with a [GitHub code search](https://github.com/search?q=MIT+filename%3ALICENSE&type=Code). As noted in #853, there are a considerable number of projects using the CERN-OHL family of licenses. This requirement appears to be to show the license is notable enough for inclusion. As the Open Hardware community is still settling on how best to share hardware, this increases the number of platforms that need to be searched. We provide the following further considerations: 1. The CERN OHL family is recommended by the [Open Source Hardware Association](https://www.oshwa.org/) 2. The CERN OHL family is recommended by journals such as [HardwareX](https://www.elsevier.com/journals/hardwarex/2468-0672/guide-for-authors) and [Journal of Open Hardware](https://openhardware.metajnl.com/about/submissions/) 3. Inclusion of CERN OHL as the first OSI approved hardware specific licenses was deemed newsworthy by [a major tech news website](https://www.theregister.com/2021/01/29/cern_ohl_approved/) ### 4. 3 notable projects using the license must be identified. These must have straightforward LICENSE files which serve as examples newcomers can follow and that could be detected by [licensee](https://github.com/licensee/licensee) if it knew about the license. As discussed in #854 this PR updates the projects.

julianstirling · July 10, 2022, 10:07am

The pull request is merged! There is now a hardware section on choosealicense.com! We have arrived!

hpy · July 10, 2022, 1:00pm

Thank you @julianstirling!

While GitHub is not my preferred platform for many reasons, this is clearly a historic step in the promotion of open source hardware.

Javier · July 10, 2022, 6:33pm

Thanks @julianstirling! Now my guess is at some point we should see the CERN OHL v2 variants pop up in the drop down menus when you want to select a licence for a new project in github.com, gitlab.com or any instance of GitLab and also when you create a new file called LICENSE or similar. I checked and did not see this yet. Does anybody know more about this? Otherwise I will try to contact somebody at GitHub.
Cheers,
Javier

julianstirling · July 13, 2022, 3:54pm

I think it is worth contacting as I don’t know exactly how it works. Also worth trying GitLab as CERN is a customer?

hpy · November 27, 2022, 2:50pm

Don’t know if it’s related, but FYI I saw that the licensee tool has added support for the CERN-OHL-P/W/S-2.0 licenses in its latest 9.15.3 release. I think this is the tool GitHub uses for license detection, so maybe doesn’t directly affect GitLab…