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

License for the user guide #134

Open
IAlibay opened this issue Feb 10, 2021 · 6 comments · May be fixed by #363
Open

License for the user guide #134

IAlibay opened this issue Feb 10, 2021 · 6 comments · May be fixed by #363

Comments

@IAlibay
Copy link
Member

IAlibay commented Feb 10, 2021

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.

@RMeli
Copy link
Member

RMeli commented Feb 18, 2021

Given that it is more text than code, is it worth thinking about a CC license as well?

@jbarnoud
Copy link

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.

@IAlibay
Copy link
Member Author

IAlibay commented Feb 18, 2021

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?

@RMeli
Copy link
Member

RMeli commented Feb 18, 2021

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.

@lilyminium
Copy link
Member

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).

If we can do that then that sounds like the best solution to me

@RMeli RMeli linked a pull request Feb 11, 2024 that will close this issue
@hmacdope
Copy link
Member

Sounds good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants