Jump to content

Licenses


draje

Recommended Posts

Hi.  Anything that does not have an explicit license is protected under copyright.

 

We will need to review exactly which components may need specific licenses.

 

Thanks.

Link to comment
Share on other sites

kingargyle

Hi.  Anything that does not have an explicit license is protected under copyright.

 

We will need to review exactly which components may need specific licenses.

 

Thanks.

 

This kind of defeats the purpose of publishing the code and repos though.  Basically if it is solely under copyright, then a person can not legally fork it or modify it beyond for personal use.   I would highly recommend at least considering a CopyLeft License like Apache or EPL where you maintain the code ownership.    Or my prefered method of licensing code to the open source community is to use BSD or MIT style licenses.

Link to comment
Share on other sites

Hi.  Anything that does not have an explicit license is protected under copyright.

 

We will need to review exactly which components may need specific licenses.

 

Thanks.

 

Thanks for clarifying.

 

Any chance you could note this in the repository? It's very deceptive to see full source code on GitHub only to find out that it's proprietary, copyright software.

 

Also - to which extent are forks permitted? For example, if I forked both repositories to my account, I would essentially be redistributing copyrighted code.

 

If forks are permitted - to which extent are modifications allowed?

Edited by draje
Link to comment
Share on other sites

kingargyle

Thanks for clarifying.

 

Any chance you could note this in the repository? It's very deceptive to see full source code on GitHub only to find out that it's proprietary, copyright software.

 

Also - to which extent are forks permitted? For example, if I forked both repositories to my account, I would essentially be redistributing copyrighted code.

 

If forks are permitted - to which extent are modifications allowed?

 

GitHub terms of service allow you to fork the repository if they made the code public.   As for making or distributing changes, you can make changes but only for personal use, unless you contribute those changes back to the original project.  Note that I am not a member of the project team, just going off past experience.

 

 

https://help.github.com/articles/licensing-a-repository/

 

Note: If you publish your source code in a public repository on GitHub, according to the Terms of Service, other GitHub users have the right to view and fork your repository within the GitHub site. If you have already created a public repository and no longer want users to have access to it, you can make your repository private. When you convert a public repository to a private repository, existing forks or local copies created by other users will still exist. For more information, see "Making a public repository private."

Edited by kingargyle
Link to comment
Share on other sites

GitHub terms of service allow you to fork the repository if they made the code public.   As for making or distributing changes, you can make changes but only for personal use, unless you contribute those changes back to the original project. 

 

This is correct and I've highlighted an important phrase :).

 

Thanks.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...