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

Add a LICENSE #24

Closed
sirkitree opened this issue Jun 29, 2015 · 16 comments
Closed

Add a LICENSE #24

sirkitree opened this issue Jun 29, 2015 · 16 comments

Comments

@sirkitree
Copy link
Contributor

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.

@sirkitree
Copy link
Contributor Author

I'd like to advocate GPL v3: http://choosealicense.com/licenses/gpl-3.0/

@sirkitree
Copy link
Contributor Author

Pull Request in #30

@sirkitree sirkitree removed their assignment Jun 30, 2015
@timschwartz
Copy link
Member

Does the GPL3 allow you to write closed-source plugins?

@sirkitree
Copy link
Contributor Author

I work with an open source activist who would know, I'll ask.

@sirkitree
Copy link
Contributor Author

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.

@timschwartz
Copy link
Member

People could totally sell plugins that use this code,

under the terms of the GPL.

So theoretically, they might sell one copy which then gets redistributed for free?

Does GPL2 have that same restriction?

@sirkitree
Copy link
Contributor Author

GPL2 works the same way, yes.

@sirkitree
Copy link
Contributor Author

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?

@sirkitree
Copy link
Contributor Author

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 license is mainly applied to libraries. You may copy, distribute and modify the software provided that modifications are described and licensed inside the modified files and licensed for free under LGPL."

This part allows other libraries to not need this license.

"Derivatives works (including modifications or anything statically linked to the library) can only be redistributed under LGPL, but applications that use the library don't have to be."

https://tldrlegal.com/license/gnu-lesser-general-public-license-v3-%28lgpl-3%29

@sirkitree
Copy link
Contributor Author

I'm going to summarize this in the original post.

@timschwartz
Copy link
Member

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.

@sirkitree
Copy link
Contributor Author

@bnolan
Copy link

bnolan commented Jun 30, 2015

I'm in favour of MIT, let people do whatever they want to do with the code. Scene is under MIT.

@timschwartz
Copy link
Member

James opinion:

from JamesMcCrae[F] sent 10 minutes ago

Haven't thought a lot about it. Perhaps MIT or LGPL. Whatever is liberal.

@sirkitree
Copy link
Contributor Author

Good to know, thank you. I'll leave the decision up to @lisa-lionheart since it's her's originally.

sirkitree added a commit that referenced this issue Jul 4, 2015
…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
sirkitree added a commit that referenced this issue Jul 4, 2015
sirkitree added a commit that referenced this issue Jul 4, 2015
@sirkitree
Copy link
Contributor Author

Going with MIT

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