-
Notifications
You must be signed in to change notification settings - Fork 59
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
Licensing, again #824
Comments
@SamuelDudley @cglusky for discussion? |
I was reading the post you linked and the associated licence. I'm allergic to lawyer speak so the blue oak licence is appealing in that regard. |
I agree. Blue Oak seems really simple and easy to read. Works for me. |
Based on the above is everyone happy to move licence? I'm for the change. |
Yeah I like blue oak, I'm for the change. I'm a little hesitant that it's not a recognised license, probably hasn't been tested or looked at by big companies or lawyers, and most people will never have heard of it. I suggest that we add a clear note to the license file explaining what it is and that it's a permissive license, and links to one or more of the following pages: |
Make decision by 2.0-beta |
@fnoop wrote:
Just my .02€: if every project would wait for a license to be popular, there will be no MIT, no GPL, not APL2 present today. If this project has at least some support, it should go for it. Maybe even go dual license under MIT+BOML for the transition time, if it's very sensitive project. Cheers! |
BOML just got an OSI approval: spdx/license-list-XML#2352 |
https://writing.kemitchell.com/2019/03/09/Deprecation-Notice.html
Not suggesting this new license necessarily, but it does seem that Apache 2.0 is a very popular permissive license. Very large companies like facebook still use MIT but they don't really have to worry too much about being sued..
The text was updated successfully, but these errors were encountered: