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

docs: Dual license under CC BY-SA and the GFDL #1432

Closed
wants to merge 1 commit into from

Conversation

cgwalters
Copy link
Member

@cgwalters cgwalters commented Jan 25, 2018

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

@cgwalters
Copy link
Member Author

(Don't merge yet - I need to send out a "relicensing ok?" email to people)

@cgwalters cgwalters added the WIP label Jan 25, 2018
@cgwalters cgwalters changed the title docs: Dual license under CC BY-SA and the GFDL WIP: docs: Dual license under CC BY-SA and the GFDL Jan 25, 2018
@cgwalters
Copy link
Member Author

@grimthorpe You are included in this due to 596fc29 - is this OK with you?

@jlebon
Copy link
Member

jlebon commented Jan 25, 2018

I do not object. :)

@marcusfolkesson
Copy link
Contributor

marcusfolkesson commented Jan 25, 2018

I think we also should add a SPDX identifier[1] tag to the license text.

E.g.
SPDX-License-Identifier: (CC-BY-SA-3.0 AND GFDL-1.3+)

When on it, we should also add the SPDX-identifier for COPYING file.
Do you want me to send a separate patch for SPDX-identifier on COPYING?

edit:
Actually... we should replace licence-text in all source files with
SPDX-License-Identifier LGPL-2.0+.
I will fix this later today if noone here thinks it is a bad idea.

[1] https://spdx.org/sites/cpstandard/files/pages/files/using_spdx_license_list_short_identifiers.pdf

@cgwalters
Copy link
Member Author

@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 COPYING? And is there a public example of a project doing that?

@cgwalters
Copy link
Member Author

I'm not a SPDX expert but isn't it OR not AND here?

@marcusfolkesson
Copy link
Contributor

@cgwalters
Yes, I think we should replace the license text in every source file with the identifier.
Example on projects that is doing this is: Linux kernel, U-Boot, Barebox, Buildroot and so on.

e.g.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/usb/core/driver.c?h=v4.14.15

And yes, it is OR as you suggest, I was a little too fast...

@cgwalters
Copy link
Member Author

cgwalters commented Jan 25, 2018

OK how about this for a footer?

Licensing for this document:

SPDX-License-Identifier: (CC-BY-SA-3.0 OR GFDL-1.3-or-later)

@blixtra
Copy link

blixtra commented Jan 25, 2018

Kinvolk is fine with the OStree documentation it holds rights to being relicensed CC-BY-SA-3.0 AND GFDL-1.3+

@wmanley
Copy link
Member

wmanley commented Jan 25, 2018

Relicensing is fine by me

@maxamillion
Copy link
Contributor

+1 to Relicensing

1 similar comment
@miabbott
Copy link
Collaborator

+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
@cgwalters
Copy link
Member Author

OK, lifting WIP. The only people who haven't replied only have single line changes, which definitely falls under the ">= 10 lines" = "copyright" heuristic.

@cgwalters cgwalters changed the title WIP: docs: Dual license under CC BY-SA and the GFDL docs: Dual license under CC BY-SA and the GFDL Jan 30, 2018
@cgwalters
Copy link
Member Author

Just for my own future reference, the man/ directory probably should have been covered here, but we can do that later.

@jlebon
Copy link
Member

jlebon commented Feb 1, 2018

@rh-atomic-bot r+ c5c6ed6

@rh-atomic-bot
Copy link

⌛ Testing commit c5c6ed6 with merge 79b3e22...

rh-atomic-bot pushed a commit that referenced this pull request Feb 1, 2018
This will allow the text to be used in Wikipedia for example; it
also just makes more sense for documentation than the LGPLv2+.

Closes: #1431

Closes: #1432
Approved by: jlebon
@rh-atomic-bot
Copy link

💥 Test timed out

@jlebon
Copy link
Member

jlebon commented Feb 2, 2018

@rh-atomic-bot retry

@rh-atomic-bot
Copy link

⌛ Testing commit c5c6ed6 with merge 0211fa7...

rh-atomic-bot pushed a commit that referenced this pull request Feb 2, 2018
This will allow the text to be used in Wikipedia for example; it
also just makes more sense for documentation than the LGPLv2+.

Closes: #1431

Closes: #1432
Approved by: jlebon
@rh-atomic-bot
Copy link

💔 Test failed - status-atomicjenkins

@jlebon
Copy link
Member

jlebon commented Feb 5, 2018

@rh-atomic-bot retry

@rh-atomic-bot
Copy link

⌛ Testing commit c5c6ed6 with merge 85c3164...

@rh-atomic-bot
Copy link

☀️ Test successful - status-atomicjenkins
Approved by: jlebon
Pushing 85c3164 to master...

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 this pull request may close these issues.

None yet

8 participants