docs(governance): adopt Community Specification license framework

CHARTER.md

@@ -45,7 +45,7 @@ Upon host organization acceptance, governance transitions from the current Proje
 
 All contributions must be made under the terms of [LICENSE](LICENSE). Contributors must sign commits with the Developer Certificate of Origin (DCO). No contribution may incorporate material covered by a patent the contributor is unwilling to license royalty-free to conforming implementations.
 
-Specification text, schema, examples, and code are licensed under Apache 2.0, the Project License, with Patent Promise. Documentation other than specification text is licensed under CC BY 4.0. Specification text published before the Project License took effect stays available under CC BY 4.0. See [LICENSE](LICENSE).
+Normative specification text and the normative TRACE JSON Schema are licensed under the Community Specification License 1.0. Source code, examples, workflows, and tests are licensed under Apache License 2.0. Documentation other than specification materials is licensed under CC BY 4.0. Earlier specification publications remain available under the licenses stated when they were published. See [LICENSE](LICENSE) and the [license map](Governance/License.md).
 
 ## 5. Trademark Policy
 

CONTRIBUTING.md

@@ -90,4 +90,4 @@ Maintainer response targets are commitments to you, not minimums. Ping the PR if
 
 Anyone who submits a PR, files an issue, or participates in discussion on the repository is a Contributor bound by the license terms.
 
-Code and specification contributions are made under the Apache License, Version 2.0, the Project License. Documentation contributions other than specification text are made under CC BY 4.0. You keep the copyright in your contributions: no contributor is asked to assign copyright to the project. See [LICENSE](LICENSE) and [General Project Policies](GOVERNANCE.md#general-project-policies).
+Specification contributions are made under the [Community Specification License 1.0](Governance/COMMUNITY-SPECIFICATION-LICENSE.md) and the [Community Specification Contributor License Agreement](Governance/CLA.md). Source-code contributions are made under Apache License 2.0. Documentation contributions other than specification text are made under CC BY 4.0. You keep the copyright in your contributions: no contributor is asked to assign copyright to the project. See [LICENSE](LICENSE), the [license map](Governance/License.md), and [General Project Policies](GOVERNANCE.md#general-project-policies).

GOVERNANCE.md

@@ -6,13 +6,13 @@ TRACE Specification has been established as TRACE Specification a Series of LF P
 
 TRACE Specification participants acknowledge that the copyright in all new contributions will be retained by the copyright holder as independent works of authorship and that no contributor or copyright holder will be required to assign copyrights to the project.
 
-Except as described below, all code and specification contributions to the project must be made using the Apache License, Version 2.0 available at http://www.apache.org/licenses/LICENSE-2.0 (the "Project License").
+All specification contributions to the Project must be made under the [Community Specification License 1.0](Governance/COMMUNITY-SPECIFICATION-LICENSE.md) and the [Community Specification Contributor License Agreement](Governance/CLA.md).
 
-All outbound code and specifications will be made available under the Project License. The Maintainers may approve the use of an alternative open license or licenses for inbound or outbound contributions on an exception basis.
+All code contributions to the Project must be made under the Apache License, Version 2.0, available at https://www.apache.org/licenses/LICENSE-2.0 (the "Source Code License"). Outbound code will be made available under the Source Code License. The Maintainers may approve an alternative open source license for code on an exception basis.
 
 All documentation (excluding specifications) will be made available under the Creative Commons Attribution 4.0 International license, available at: https://creativecommons.org/licenses/by/4.0.
 
-Specification text published before this policy took effect stays available under the license it was published under. See [LICENSE](LICENSE).
+Specification text published before this policy took effect stays available under the license under which it was published. See [LICENSE](LICENSE) and the [license map](Governance/License.md).
 
 ## Roles
 
@@ -48,6 +48,34 @@ The Project makes decisions through a consensus process ("Approval" or "Approved
 
 Decisions may be appealed via a pull request or an issue, and that appeal will be considered by the Project Lead in good faith, who will respond in writing within a reasonable time.
 
+## Ways of Working
+
+Inspired by [ANSI's Essential Requirements for Due Process](https://share.ansi.org/Shared%20Documents/Standards%20Activities/American%20National%20Standards/Procedures,%20Guides,%20and%20Forms/2020_ANSI_Essential_Requirements.pdf), the Project adheres to consensus-based due-process requirements for approving, revising, reaffirming, and withdrawing TRACE specifications. Any person or organization with a direct and material interest has the right to express a position and its basis, have that position considered, and appeal a decision.
+
+### Openness
+
+Participation is open to all persons and organizations directly and materially affected by the work. There are no undue financial barriers to participation. Voting or decision-making eligibility is not conditional on membership in another organization or unreasonably restricted by technical qualifications.
+
+### Lack of dominance
+
+The specification-development process must not be dominated by any single interest category, individual, or organization to the exclusion of fair and equitable consideration of other viewpoints.
+
+### Balance
+
+The Project seeks participation from diverse interest categories, including implementers, technology providers, users, security and privacy experts, and other materially affected parties.
+
+### Coordination and harmonization
+
+The Project makes good-faith efforts to identify and resolve conflicts between TRACE deliverables and existing industry standards.
+
+### Consideration of views and objections
+
+The Project promptly considers written views and objections from all Contributors. The Project Lead documents the evidence used to determine Consensus, including material objections and their disposition.
+
+### Written procedures
+
+This governance document and other materials describing the Community Specification development process are publicly available to any interested person.
+
 ### Review periods by change class
 
 Review periods are minimums. The Project takes as much time as it needs to reach a consensus decision, and a period does not expire a discussion that is still live.
@@ -76,7 +104,7 @@ A Draft Specification is not stable. Normative requirements, wire formats, and c
 
 ### Final
 
-Once the Project believes it has achieved the objectives for its specification as described in the Scope, it will Approve that Draft Specification and progress it to "Final" status.
+Once the Project believes it has achieved the objectives for its specification as described in the [Scope](Governance/Scope.md), it will Approve that Draft Specification and progress it to "Final" status. A Final specification is an "Approved Specification" for purposes of the Community Specification License 1.0.
 
 A Final specification is stable. Its normative content does not change except through errata, which are corrections that do not alter what a conformant implementation must do. New requirements are made in a new version, not in the published one. Conformance claims are made against a Final version, and the conformance suite tracks Final versions.
 

Governance/CLA.md

@@ -0,0 +1,18 @@
+# Community Specification Contributor License Agreement 1.0
+
+By making a Contribution to this repository, I agree to the terms of the following documents:
+
+(a) [Community Specification License 1.0](COMMUNITY-SPECIFICATION-LICENSE.md)
+
+(b) [TRACE Governance Policy](../GOVERNANCE.md)
+
+(c) [TRACE Contribution Policy](../CONTRIBUTING.md)
+
+(d) [TRACE Code of Conduct](../CODE_OF_CONDUCT.md)
+
+
+In addition, for source code contributions, I certify that:
+
+(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. (d) I understand and agree that this working group and the contribution may be public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this agreement or the open source license(s) involved.
+
+I represent that I am legally entitled to make the grants set forth in the documents above.  If my employer(s) has rights to intellectual property that may be infringed by the materials developed by this Project, I represent that I have received permission to enter these agreements on behalf of that employer.