-
Notifications
You must be signed in to change notification settings - Fork 32
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
Add a LICENSE #24
Comments
I'd like to advocate GPL v3: http://choosealicense.com/licenses/gpl-3.0/ |
Pull Request in #30 |
Does the GPL3 allow you to write closed-source plugins? |
I work with an open source activist who would know, I'll ask. |
People could totally sell plugins that use this code, they would just be required to also provide the source code when they sell it (which they'd have to in this case anyway as it's not compiled code) and under the terms of the GPL. But if people make the plugins, they are under no obligation to distribute the code to anyone else. |
So theoretically, they might sell one copy which then gets redistributed for free? Does GPL2 have that same restriction? |
GPL2 works the same way, yes. |
If we wanted to allow a world where there was some sort of market for buying plugins, we'd probably want to go with the Apache 1.1 License which does not require that derivative works be distributed using the same license. I'm not entirely sure how I feel about that, as I'd personally rather foster a ecosystem of sharing openly rather than closed markets. But I could be persuaded. Perhaps we should ask on the JanusVR subreddit? |
Another option pointed out to me by a friend who understands licensing better than me is the LGPL This part protects the core janus-server code.
This part allows other libraries to not need this license.
https://tldrlegal.com/license/gnu-lesser-general-public-license-v3-%28lgpl-3%29 |
I'm going to summarize this in the original post. |
I'm in favor of LGPL 2.1, but if everyone else wants GPL 3.0 I won't object. If a person or company absolutely needs to keep their code proprietary they can always reimplement the server themselves from the API. |
Opened a thread on the subreddit here: http://www.reddit.com/r/janusVR/comments/3bnuqg/weigh_in_which_open_source_license_should_the/ |
I'm in favour of MIT, let people do whatever they want to do with the code. Scene is under MIT. |
James opinion:
|
Good to know, thank you. I'll leave the decision up to @lisa-lionheart since it's her's originally. |
…icense[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License[#24] Add the MIT License
Going with MIT |
We should specify the license for this software.
Current options being discussed mainly relate to the distribution of server plugins.
GPL 3.0
This would ensure that the server code is always open and free as well as any plugins created for it.
LGPL 2.1
This would ensure that the server code is always open and free but plugins would not have to be free and/or open source.
The text was updated successfully, but these errors were encountered: