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

Documentation licensing #18269

Closed
3ynm opened this issue Nov 16, 2015 · 3 comments
Closed

Documentation licensing #18269

3ynm opened this issue Nov 16, 2015 · 3 comments

Comments

@3ynm
Copy link

3ynm commented Nov 16, 2015

Since the documentation examples are intended to be used as copy-paste, and the code is already licensed, why using attribution license for examples and pieces of code instead of CC0?

@kkirsche
Copy link
Contributor

I'd start by reviewing issues #16470 and #16487 — for the most part this has to do with the need to contact every single individual contributor who has ever touched the docs to change which is an extremely painful process for a project of this size as I understand it.

@mdo
Copy link
Member

mdo commented Oct 24, 2016

Closing out since there are no planned changes here.

The docs content itself is under a different license than the code, yes, but the code included there is still under that MIT license as far as I know. However, as I'm no lawyer, if someone has a more authoritative source, I'd happily revisit.

@mdo mdo closed this as completed Oct 24, 2016
@dcousens
Copy link

dcousens commented Sep 24, 2018

@mdo to clarify, do you know if are the examples are actually MIT licensed?

The README states "Code released under the MIT License.", which seems to be a resounding yes...
But then "Docs released under Creative Commons." ... hmph.

The examples are under docs/, but they are Code...

#16487 seems contradictory to what you suggest @mdo?

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

5 participants