Add 0BSD License

spdx/license-list-XML#768

This seems to be missing from your list, which I was under the impression was pulled from SPDX license XML (it's already there).

Ref: #464

[mlinksva]

The catalog here is checked against the SPDX list (eg that a given license exists and we're using the same naming) but only includes a small subset of licenses in the SPDX list since we do additional work to describe the attributes of each license cataloged here. I welcome a PR to add any license here that meets all of our criteria. I'm not sure that 0BSD meets 3 yet but if you can come up with a query that shows it plausibly (it's hard to get exact results) does, great!

Fair enough:

• Here's 431+ licenses using an alternate name: https://github.com/search?q="Free+Public+License+1.0.0"+filename%3ALICENSE&type=Code
• And another 135 or so https://github.com/search?q="Zero-Clause+BSD"+filename%3ALICENSE&type=Code
• 634 with "0BSD" https://github.com/search?q=%220BSD%22+filename%3ALICENSE&type=Code

Considering "exact search" doesn't turn up all the results does BlackDuck have something which might help? Or does it make more sense to also include GitLab, BitBucket et al. considering this website—and licensing in general—are bigger than GH alone?

Thanks for helping with the extra work to raise visibility of 0BSD on this global website resource.

And I just learned today on npm.community 0BSD SPDX code was recently added to NPM so we can expect 1000 no sweat. /cc @landley

[mlinksva]

Thanks for your research @JHabdas. Feel free to open a PR to add 0BSD if you'd like to take a stab at it.

@landley could you help me identify 2 noteable projects besides your own using 0BSD or the former license name in order to help me satisfy the contributing guidelines? Don't think mine counts yet. ;)

[waldyrious]

Ideally this listing from libraries.io would be helpful, but the results seem to be quite unreliable.

That said, I did find https://github.com/m-labs/smoltcp (around 700 stars, FWTW as a measure of notability) and https://github.com/nazar-pc/PickMeUp (~570 stars). The latter lacks an actual LICENSE file, though. There's only a reference to the name of the license in package.json, and some links in the README. You might want to submit one as a PR, to ensure it can be legally considered as licensed under the 0BSD.

Thanks @waldyrious. Pull submitted. We'll see what the author says. As an aside I'm curious to know what is necessary to have 0BSD also start showing up in the GitHub UI:

When I copy the exact license text and push a commit up it doesn't seem to take yet and I get the generic View License message. Perhaps that's driven by an NPM or Ruby SPDX license list module somewhere?

[mlinksva]

To show up in the GitHub UI the license has to be added in this repo, then vendored in licensee (which GitHub uses for license detection), then a new version of licensee cut, then that new version of licensee deployed on GitHub, then finally a detection has to be triggered in a particular repo (e.g., license file added/edited, or manually via support), and license text in repo has to be a near exact match of what has been added to this repo, or licensee won't positively identify it, and you'll still see "View license". So making a PR to add 0BSD to this repo is the first step. 😄

Pull opened