-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Consider recoloring CC0 license and adding 0BSD #10058
Comments
Thanks for reaching out. I confess my initial reaction seeing this is the typical "I'm not a lawyer, I don't even want to pretend to be able to adjudicate open source licenses", but I also fully recognize the badge coloring is, to an extent, already doing just that. I'll be curious to hear thoughts from other maintainers, but I think there's two separate items here: the addition of 0BSD which should be fairly noncontroversial, and potential changes on CC0 which will have some level of blast radius consideration and controversy |
Yeah I agree regarding CC0. That's exactly why I put the opinions of Free Software Foundation nor Open Source Initiative in the original post, not my own opinion 😉 |
Broadly speaking, I'm against us just freestyling this and making our own judgements. Looking over the comments in https://github.com/badges/shields/blob/master/services/licenses.js and the discussion in #1190 it seems that we're mostly deferring to choosealicense.com on this. Looking over the table on https://choosealicense.com/appendix/ and http://landley.net/toybox/license.html I agree with adding 0BSD to this category 👍 On removing CC0: Badges are not only for software projects (although I acknowledge that is the primary use). Data projects can use badges too. You can use one on your eBook if you want 🤷 |
Change is available for merge in PR #10092 |
I had this exact same reaction too but talked myself into not opening that can of worms. The more I think about it, the more I feel like the license fits squarely into that blue/informational pattern that we use for data elements I'd consider to be very similar in nature. Given #10092 I'm going to go ahead and close this, as one half of this has already been resolved and there's some objections and concerns on the other half of this issue around removing CC0 from the public domain group. Separately, I would be open to discussing dropping our current default behavior of applying semantic coloring to licenses and just using blue/informational by default, as people can always adjust to whatever color they want (in fact, reviewing my own personal usages of this badge I was reminded that I seem to always drop a |
Are you experiencing an issue with...
shields.io
🐞 Description
Neither Free Software Foundation nor Open Source Initiative recommend releasing software under CC0 due to patent grant issues, and only Free Software Foundation considers CC0 as a free license. However, it is currently being colored as the least restrictive. The license is controversial at best.
One real no-attribution license in the software world is 0BSD, which is not included by shield.io.
🔗 Link to the badge
No response
💡 Possible Solution
Recolor or remove CC0, and add 0BSD to the public domain color list.
The text was updated successfully, but these errors were encountered: