Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 0BSD License #642

Closed
ghost opened this issue Feb 11, 2019 · 9 comments

Comments

Projects
None yet
2 participants
@ghost
Copy link

commented Feb 11, 2019

spdx/license-list-XML#768

screen shot 2019-02-11 at 6 16 24 pm

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

@ghost ghost referenced this issue Feb 11, 2019

Closed

Possibly add 0BSD license #464

@mlinksva

This comment has been minimized.

Copy link
Contributor

commented Feb 11, 2019

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!

@ghost

This comment has been minimized.

Copy link
Author

commented Feb 12, 2019

Fair enough:

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.

@ghost

This comment has been minimized.

Copy link
Author

commented Feb 12, 2019

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

This comment has been minimized.

Copy link
Contributor

commented Feb 12, 2019

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

@ghost

This comment has been minimized.

Copy link
Author

commented Feb 13, 2019

@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

This comment has been minimized.

Copy link
Contributor

commented Feb 13, 2019

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.

@ghost ghost referenced this issue Feb 13, 2019

Merged

Added license file for 0BSD #216

@ghost

This comment has been minimized.

Copy link
Author

commented Feb 13, 2019

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:

screen shot 2019-02-13 at 6 23 03 pm

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

This comment has been minimized.

Copy link
Contributor

commented Feb 13, 2019

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. 😄

@ghost ghost referenced this issue Feb 14, 2019

Merged

Add Zero Clause BSD license #643

@ghost

This comment has been minimized.

Copy link
Author

commented Feb 14, 2019

Pull opened

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.