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

Choose a proper license #9

Open
tomlutzenberger opened this issue Apr 10, 2017 · 4 comments
Open

Choose a proper license #9

tomlutzenberger opened this issue Apr 10, 2017 · 4 comments

Comments

@tomlutzenberger
Copy link
Member

tomlutzenberger commented Apr 10, 2017

I'm not sure if the initial picked license (ISC) fits our needs. It should be clarified which license should be used in the future.
https://choosealicense.com/

@gagarine
Copy link
Contributor

In my opinion MIT is alright for the plugin.

@shanness
Copy link
Collaborator

LGPL sounds better I reckon, MIT doesn't require distributed changes to be disclose the source.
https://choosealicense.com/licenses/

@tomlutzenberger
Copy link
Member Author

Fixed in 0060694

@gagarine
Copy link
Contributor

gagarine commented Apr 11, 2017

@shanness for a browser plugin. I don't see why someone would like to modify it and not distribute the change. The plugin is useless without the server side.

Now if someone find some line of code in our project that he want to copy in is own project... who cares.

One things to keep in minde: LGPL License in incompatible with Apache License.

I will advice LGPL for example for a library like ffmpeg. You don't want google fork ffmpeg, make it a bit better, and don't share his changes.

@gagarine gagarine reopened this Apr 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants