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

Need policy clarification on documentation licensing #230

Closed
jberkus opened this issue Nov 9, 2021 · 5 comments
Closed

Need policy clarification on documentation licensing #230

jberkus opened this issue Nov 9, 2021 · 5 comments

Comments

@jberkus
Copy link

jberkus commented Nov 9, 2021

Our charter has this confusing language about documentation licensing:

(e) All projects evaluated for inclusion in the CNCF shall be completely licensed under an OSI-approved open source license. If the license for a project included in CNCF is not Apache License, Version 2.0, approval of the Governing Board shall be required.

(f) All documentation will be received and made available by the CNCF under the Creative Commons Attribution 4.0 International License.

Thus all project materials must be available under the AL2, but all documentation must be available under CCBY. This language has always been contradictory.

Most projects have taken this to mean that documentation, particularly documentation that is embedded in code repos, may be licensed under either AL2 or CCBY, as circumstances warrant. However, recently, some folks involved in the CNCF ecosystem have taken this to mean that all documentation, even a README, must be licensed CCBY no matter what, even if that requires adding a separate license header to every file or even portions of a file. This interpretation of the policy appears to be based on the mistaken belief that the AL2 cannot legally be used for documentation (something the Apache Project would be very surprised to hear).

And it's stalled us in Contributor Strategy based on "what guidance do we put in the templates regarding license".

My proposal is that the GB clarify that projects must use AL2 for code, and can use either CCBY or AL2 for documentation and content (like websites).

@jberkus
Copy link
Author

jberkus commented May 26, 2023

BTW, note that many projects join the CNCF with all of their documentation under the Apache license. So requiring that documentation to be CCBY forces them to go through a relicensing effort.

@amye
Copy link
Contributor

amye commented May 26, 2023

This is currently scheduled for review in the June 8th meeting of the Legal Committee.

@amye
Copy link
Contributor

amye commented Sep 28, 2023

Approved by Legal Committee and GB as of a vote on 8-31, minutes will be approved as of the next governing board meeting

@amye amye closed this as completed Sep 28, 2023
@craigbox
Copy link
Contributor

craigbox commented Mar 4, 2024

I don't see any mention of this in the Sep 2023 or Dec 2023 meeting minutes, and the charter hasn't been changed. Can I check in on the next steps here please @amye?

@krook
Copy link
Member

krook commented Mar 20, 2024

This is what was approved by an email vote of the Governing Board on August 31, 2023:

RESOLVED, that the Governing Board hereby approves a license exception to permit CNCF project source code repositories’ documentation files to be published under either Apache-2.0 or CC-BY-4.0.

To answer a related question about relicensing existing APL2 docs as CC-BY-4.0 if desired, the answer from @joannalee333 is that they can be relicensed as long as each author of the docs approves the change of license. Relicensing documentation to CC-BY4.0 doesn't require any other approval of foundation staff or the GB.

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

4 participants