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 WecOptTool license #60

Closed
ryancoe opened this issue Mar 20, 2020 · 5 comments
Closed

Choose WecOptTool license #60

ryancoe opened this issue Mar 20, 2020 · 5 comments
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@ryancoe
Copy link
Member

ryancoe commented Mar 20, 2020

I'm considering GNU GPLv3, any thoughts?

https://choosealicense.com

@ryancoe ryancoe added the documentation Improvements or additions to documentation label Mar 20, 2020
@ryancoe ryancoe added this to the v0 release milestone Mar 20, 2020
@ryancoe ryancoe self-assigned this Mar 20, 2020
@ssolson
Copy link
Collaborator

ssolson commented Mar 20, 2020

I have no experience but remember Mat saying everyone uses GPL3 now. So I would lean that way.

@H0R5E
Copy link
Member

H0R5E commented Mar 23, 2020

I think there are two main issues to consider which are how it will be used in the future and what other code we might need to interface with.

If this code would be useful as a library (and you were happy for it to be used in a commercial setting) then a permissive licence like MIT, BSD etc is nice as it pretty much allows any future use. If you would prefer for this code to stay free, then a copy-left license like GPL is the way to go, as it will force any modified source code to also be open (when its published).

One thing that may force us into using GPL is that we may need to leverage (and I suspect this is very likely) other GPL codes. In this case it often obliges the user of GPL codes to be GPL as well.

In DTOcean, I was able to make some of the code MIT and the rest GPL, which was possible as its split accross a few packages, where some are more useful as libraries than others. I don't think this project is big enough yet to consider that, but maybe if we have some nice library code in the future, we could split it off as a seperate project under a more permissive license.

So, in conclusion, probably GPL for now and maybe think about it again later.

@ryancoe
Copy link
Member Author

ryancoe commented Mar 24, 2020

Will proceed w. GPL for time being, can reassess later, if necessary.

@H0R5E H0R5E mentioned this issue Mar 24, 2020
7 tasks
@ryancoe
Copy link
Member Author

ryancoe commented Mar 25, 2020

completed w/ e559fff

also added to git io pages w/ 0d2faa2

@ryancoe ryancoe closed this as completed Mar 25, 2020
@kmruehl
Copy link

kmruehl commented Mar 30, 2020

If you would like my input, I have a lot of thoughts on this. I think the GNU license will be a barrier for industry adoption.

Also, the copyright assertion needs to go through Sandia legal and be approved by Sandia and DOE prior to release of the code. This requires identification of a open source license (eg BSD, GNU) and information about the code to be submitted through the Sandia online system: https://webprod.sandia.gov/TAIPM/. Has this been done?

@kmruehl kmruehl reopened this Mar 30, 2020
@ryancoe ryancoe closed this as completed Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants