-
Notifications
You must be signed in to change notification settings - Fork 290
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
docs: Dual license under CC BY-SA and the GFDL #1432
Conversation
(Don't merge yet - I need to send out a "relicensing ok?" email to people) |
@grimthorpe You are included in this due to 596fc29 - is this OK with you? |
I do not object. :) |
I think we also should add a SPDX identifier[1] tag to the license text. E.g. When on it, we should also add the SPDX-identifier for COPYING file. edit: [1] https://spdx.org/sites/cpstandard/files/pages/files/using_spdx_license_list_short_identifiers.pdf |
@marcusfolkesson Makes sense, I'll update this PR for the docs. As for the source - before you do the PR, just so I know: does that involve touching every source file or just the |
I'm not a SPDX expert but isn't it |
@cgwalters And yes, it is OR as you suggest, I was a little too fast... |
OK how about this for a footer? Licensing for this document:
|
Kinvolk is fine with the OStree documentation it holds rights to being relicensed CC-BY-SA-3.0 AND GFDL-1.3+ |
Relicensing is fine by me |
+1 to Relicensing |
1 similar comment
+1 to Relicensing |
This will allow the text to be used in Wikipedia for example; it also just makes more sense for documentation than the LGPLv2+. Closes: ostreedev#1431
OK, lifting WIP. The only people who haven't replied only have single line changes, which definitely falls under the ">= 10 lines" = "copyright" heuristic. |
Just for my own future reference, the |
💥 Test timed out |
@rh-atomic-bot retry |
💔 Test failed - status-atomicjenkins |
@rh-atomic-bot retry |
☀️ Test successful - status-atomicjenkins |
Originating issue: #1431
Mailing list post: https://mail.gnome.org/archives/ostree-list/2018-January/msg00004.html
This will allow the text to be used in Wikipedia for example; it
also just makes more sense for documentation than the LGPLv2+.