-
Notifications
You must be signed in to change notification settings - Fork 1.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
Change license to something more standard #1392
Comments
This is also mentioned in #1280 which shows there is a real demand for it, And I'm not just suggesting this change for the sake of change alone. |
My comments on the issue you linked as well as the previous re-license of nerdcommenter pretty much explains my position on this. The potential contributor with a legal reason for not being able to contribute under WTFPL is a pretty solid nudge in that direction too. Even if that person doesn't turn back up I'm sure there are others is similar positions. I'd fully support a re-license to Given the lack of barriers to re-licensing in this situation I would probably just let this sit around a little while collecting upvotes and any comments, then if nobody objected with unaddressed concerns we'll just go for it. |
Thank you for pinning this issue, I didn't want to be rude and pin this without permission from you. I think |
I want to suggest something similar to what happened to the
nerdcommander
.My points are pretty much identical to what is discussed in this issue preservim/nerdcommenter#217.
Switching to another license can make it easier for people to use and/or contribute to the project.
I don't have any strong argument for/against any of the available licenses other than
PUBLIC DOMAIN
which doesn't really make that much of a difference withWTFPL
; Since it is not considered a real license in many jurisdictions around the world(I've never consulted a lawyer about this but from what I've read on the internet I think it is true).I'm going to ping a few of the people with most contributions to the project to chip in in this discussion.
@scrooloose @PhilRunninger @alerque @lifecrisis
The text was updated successfully, but these errors were encountered: