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

Consider switching to a more permissive software license #68

Closed
jodal opened this issue Nov 26, 2014 · 14 comments
Closed

Consider switching to a more permissive software license #68

jodal opened this issue Nov 26, 2014 · 14 comments

Comments

@jodal
Copy link

jodal commented Nov 26, 2014

pafy is licensed under GPLv3. This makes it unusable for projects with a more permissive license, like the Apache Licence, MIT or BSD, without them changing their own license to GPLv3 too.

Of course, the choice of license entirely up to you as the author of the software, but I'd like you to at least consider switching to a more permissive license so pafy can be used as a building block by more projects. :-)

np1 added a commit that referenced this issue Nov 27, 2014
@np1
Copy link
Contributor

np1 commented Nov 27, 2014

That's fine with me. MIT it is. Thanks for the suggestion.

@np1 np1 closed this as completed Nov 27, 2014
np1 added a commit that referenced this issue Nov 27, 2014
@jodal
Copy link
Author

jodal commented Nov 27, 2014

Thanks :-)

np1 added a commit that referenced this issue Nov 27, 2014
np1 added a commit that referenced this issue Nov 27, 2014
@np1
Copy link
Contributor

np1 commented Nov 27, 2014

I may have been too hasty to switch to the MIT license and will need to consider more which license to use, back to GPLv3 for now.

@np1
Copy link
Contributor

np1 commented Nov 28, 2014

Ok, I have looked into it a bit more and from what I understand the more "permissive" licenses are permissive in that they permit others to be less permissive, so I decided to stick with GPLv3.

@np1 np1 removed the implemented label Nov 28, 2014
@ktws
Copy link

ktws commented Nov 29, 2014

Wouldn't using LGPL be a good compromise? This would allow Apache Licence, MIT or BSD licenced python scripts to dynamically import Pafy.

As I understand it, under LGPL, any 3rd party modifications to the Pafy library its-self would still need to be released to the public under LGPL. Lifting sections of the pafy library code and using it in another script would mean that that script would need to be released under GPL. It's what videolan's libVLC python library is now released under.

@np1
Copy link
Contributor

np1 commented Dec 2, 2014

Yes possibly, I will consider it and get back to you.

@np1 np1 reopened this Dec 2, 2014
@ids1024
Copy link
Contributor

ids1024 commented Dec 6, 2014

To change software license, you need permission from all copyright holders. In this case, it would be anyone who contributed code to the project, unless their contribution was a trivial change, such as a single line.

It looks like there are a couple contributors whose changes are non-trivial.

@np1
Copy link
Contributor

np1 commented Dec 10, 2014

@ids1024 thanks for making me aware of this, in that case I will contact the other contributors if I decide I wish to switch and seek their approval.

@np1
Copy link
Contributor

np1 commented Dec 10, 2014

@kewitz @ElegantMonkey @stav @Dav1dde
Thank you for contributing code to this project while it was released under GNU Public License v3. Do you consent to changing the license to GNU Lesser General Public License v3?

@Dav1dde
Copy link
Contributor

Dav1dde commented Dec 10, 2014

Yes, the change would be great!

@stav
Copy link
Contributor

stav commented Dec 10, 2014

Yes, sounds like a good idea for the lesser.

@kewitz
Copy link
Contributor

kewitz commented Dec 10, 2014

Sure, whatever you decide is good for me.

@ekisu
Copy link
Contributor

ekisu commented Dec 10, 2014

Yes, that's alright.

np1 added a commit that referenced this issue Dec 18, 2014
@np1
Copy link
Contributor

np1 commented Dec 18, 2014

Great, thank you all for your approval 👍
I have changed the license.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants