-
Notifications
You must be signed in to change notification settings - Fork 598
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
Comments
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. |
This is currently scheduled for review in the June 8th meeting of the Legal Committee. |
Approved by Legal Committee and GB as of a vote on 8-31, minutes will be approved as of the next governing board meeting |
This is what was approved by an email vote of the Governing Board on August 31, 2023:
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. |
Our charter has this confusing language about documentation licensing:
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).
The text was updated successfully, but these errors were encountered: