This is the organizational charter for the SCITT Community Organization (the "Organization"). By adding their name to the Steering Committee.md file, Steering Committee members agree as follows.
Work as a community to facilitate adoption of IETF Supply Chain Integrity, Transparency & Trust (SCITT) specifications.
2.1 Purpose. The Steering Committee will be responsible for all technical oversight, project approval and oversight, policy oversight, and trademark management for the Organization.
2.2 Composition. The Steering Committee voting members are listed in the STEERING-COMMITTEE.md file in the repository. Voting members may be added or removed by no less than 3/4 affirmative vote of the Steering Committee. The Steering Committee will appoint a Chair responsible for organizing Steering Committee activity. The Steering Committee shall be composed of not less than 7 and not more than 9 members at any given time.
2.3 Term Length Steering Committee members shall serve for a two year term.
3.1. Decision Making. The Steering Committee will strive for all decisions to be made by consensus. While explicit agreement of the entire Steering Committee is preferred, it is not required for consensus. Rather, the Steering Committee will determine consensus based on their good faith consideration of a number of factors, including the dominant view of the Steering Committee and nature of support and objections. The Steering Committee will document evidence of consensus in accordance with these requirements. If consensus cannot be reached, the Steering Committee will make the decision by a vote.
3.2. Voting. The Steering Committee Chair will call a vote with reasonable notice to the Steering Committee, setting out a discussion period and a separate voting period. Any discussion may be conducted in person or electronically by text, voice, or video. The discussion will be open to the public. In any vote, each voting representative will have one vote. Except as specifically noted elsewhere in this Charter, decisions by vote require a simple majority vote of all voting members.
In addition to the method set out in section 2.2, the membership of a Steering Committee member will terminate if any of the following occur:
4.1 Resignation. Written notice of resignation to the Steering Committee.
4.2 Unreachable Member. If a member is unresponsive at its listed handle for more than three months the Steering Committee may vote to remove the member.
Any names, trademarks, service marks, logos, mascots, or similar indicators of source or origin and the goodwill associated with them arising out of the Organization's activities or Organization projects' activities (the "Marks"), are controlled by the Organization. Steering Committee members may only use the Marks in accordance with the Organization's trademark policy. If a Steering Committee member is terminated or removed from the Steering Committee, any rights the Steering Committee member may have in the Marks revert to the Organization.
The Steering Committee is bound by the Organization's antitrust policy.
Information disclosed in connection with any of the Organization's activities, including but not limited to meetings, Contributions, and submissions, is not confidential, regardless of any markings or statements to the contrary.
A Project may be represented by one or more git repositories. In order to be eligible to be a Organization project, a project must:
- Be approved by the Steering Committee.
- Agree to follow the guidance and direction of the Steering Committee.
- Use only the following outbound licenses or agreements unless otherwise approved:
- For code, a license on the Open Source Initiative's list of Popular Licenses.
- For data, a license on the Open Knowledge Foundation's list of Recommended Conformant Licenses.
- For specifications, a community developed and maintained specification agreement, such the Open Web Foundation Agreements or Community Specification Agreement.
- Include and adhere to the Organization's policies, including the trademark policy, the antitrust policy, and the code of conduct.
- When a project uses multiple repositories, one root repository will maintain the project governance files. The governance files are copied from project-docs, while the related repositories will maintain the same named files that link back to the root repository.
See PROJECTS.md for the current SCITT Community projects.
New projects, that agree to the above criteria, may be created by opening an issue, asking for a vote from the steering committee.
Amendments to this charter, the antitrust policy, the trademark policy, or the code of conduct may only be made with at least a 3/4 affirmative vote of the Steering Committee.
Part of MVG-0.1-beta. Made with love by GitHub. Licensed under the CC-BY 4.0 License.