-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
chore(create-vite): mark template files as CC0 #18366
chore(create-vite): mark template files as CC0 #18366
Conversation
Run & review this pull request in StackBlitz Codeflow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me 👍 I did a little research as well and CC0 seems like the best option to waive all copyrights. A bit unfortunate that it's a little long.
I also found this interesting link where Google folks can't patch CC0 licensed projects, but I don't think we should be deciding based on that.
Co-authored-by: Bjorn Lu <bjornlu.dev@gmail.com>
I think we also need to regenerate the LICENSE from the last commit |
Ah, good catch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Sounds good to me. I wonder what others create-xxx are doing. They should all do something similar to this.
It seems some are licenesed with MIT (unintentionally?) (facebook/create-react-app#9480) and some are unlicensed (sveltejs/template#78, vercel/next.js#28007) (which makes the template be in a blurry state). The only one that had a public domain license I found was gatsby (0BSD: gatsbyjs/gatsby#25091). |
The files in the directories starting with "template-" in create-vite and files | ||
generated from those files are licensed under the CC0 1.0 Universal license: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I replaced "files generated by create-vite" with "files generated from those files" so that we don't say anything about files generated by the redirected CLIs (e.g. create-vue, create svelte).
I noticed 0BSD as a compelling alternative too, but I figured being in the public domain has lesser restrictions and concerns. But as a non-lawyer they both look similar and there shouldn't be any downsides choosing either I believe. |
Different from CC0, 0BSD and MIT No Attribution License are OSI approved licenses and might be compelling in that point. |
Ah, one thing I remember now is that technically 0BSD and MIT-0 are copyright licenses. You'd put your name/year etc in the license. Some 0BSD licenses don't have the copyright line, but I believe in that case it's still implicitly copyrighted. The main distinction of those licenses is that you don't need attribution, but no attribution doesn't mean waiving copyright. CC0 technically holds copyright, but it tries to waive as much as possible by law. That means when someone uses the templates, we no longer hold the rights (as much as possible by law) to that template code. In which case, I think CC0 is still beneficial here. (With all that said, IANAL and this is based on my own research) |
Description
Marked template files as CC0 1.0 (public domain).
close #16228