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 license to repo #133

Closed
jhamman opened this issue Jul 9, 2014 · 7 comments
Closed

Add license to repo #133

jhamman opened this issue Jul 9, 2014 · 7 comments
Assignees
Milestone

Comments

@jhamman
Copy link
Member

jhamman commented Jul 9, 2014

Here is a good reference (set up by the folks at GitHub) on the different types of licenses available: http://choosealicense.com

We probably should go with a GPL license that

... is a copyleft license that requires anyone who distributes your code or a derivative work to make the source available under the same terms. V3 is similar to V2, but further restricts use in hardware that forbids software alterations.

It is also probably a good idea to add a piece of the license to the header of each source code file.

Related: #48

@jhamman jhamman added this to the 5.0 milestone Jul 9, 2014
@jhamman jhamman assigned jhamman and unassigned bartnijssen Sep 27, 2014
@jhamman jhamman modified the milestones: 4.2, 5.0 Sep 27, 2014
jhamman pushed a commit that referenced this issue Sep 27, 2014
@jhamman
Copy link
Member Author

jhamman commented Sep 27, 2014

I've added the GNU GPL v2.0 to the repo. We still need to add something regarding the license to the header of the source code files but that should be done as part of #48.

@jhamman jhamman closed this as completed Sep 27, 2014
@bartnijssen
Copy link
Member

Why gpl v2 rather than v3?

On Sep 26, 2014, at 6:41 PM, Joe Hamman notifications@github.com wrote:

I've added the GNU GPL v2.0 to the repo. We still need to add something regarding the license to the header of the source code files but that should be done as part of #48.


Reply to this email directly or view it on GitHub.

@jhamman
Copy link
Member Author

jhamman commented Sep 27, 2014

V2 is less restrictive which obviously has its pros and cons but my understanding is that this is the main difference:

V3 is similar to V2, but further restricts use in hardware that forbids software alterations.

@bartnijssen
Copy link
Member

It doesn't forbids alterations as far as I know but requires that you share them which makes sense to me for scientific open-source. We picked v3 for SUMMA. let me take another look and leave the issue open for now.

On Sep 26, 2014, at 7:37 PM, Joe Hamman notifications@github.com wrote:

V2 is less restrictive which obviously has its pros and cons but my understanding is that this is the main difference:

V3 is similar to V2, but further restricts use in hardware that forbids software alterations.


Reply to this email directly or view it on GitHub.

@bartnijssen
Copy link
Member

Since VIC has been around for a long time and people are using it for many purposes already, we'll leave the more permissive V2 license.

@jhamman
Copy link
Member Author

jhamman commented Sep 29, 2014

Sounds good. We can always change the license at a later date if need be.

@bartnijssen
Copy link
Member

True - although that would not be the preferred way as people need to know whether they can use the model for a specific purpose going forward.

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

2 participants