-
Notifications
You must be signed in to change notification settings - Fork 35
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
License for the user guide #134
Comments
Given that it is more text than code, is it worth thinking about a CC license as well? |
I think a CC license would be the most appropriate. However, the user guide is backed quite a bit by docstring and those have been contributed under GPL. That may be an issue. |
Ideally a CC-BY4 license would be most appropriate, but I agree with @jbarnoud if anything in the userguide is taken out of the docs verbatum we'd probably have to adhere to GPL. @lilyminium might have a better view of things here, but maybe it's one of those we should be asking the numfocus folks? |
I was thinking more about a dual license model that I've seen multiple times in this scenario: CC for text and GPL for code? CC-BY-SA is reasonably aligned with GPL (I think). Of course if you have access to NumFocus advice, they will probably know already how to handle this. |
If we can do that then that sounds like the best solution to me |
Sounds good. |
So I might not be looking at the right place, but as far as I can tell the user guide doesn't directly declare any type of license.
I guess the assumption is that it inherits MDA's GPLv2 license?
Given that the user guide is a really good teaching resource, I think it might be good to make it clear as to what the license is so that folks can be more confident in using parts of it in derivative works where possible.
The text was updated successfully, but these errors were encountered: