...
Technical Steering Committee
The Technical Steering Committee (the “TSC”) will be responsible for all
technical oversight of the open source Project.
"Transition Period”: From the effective date of this Charter, up to but no more
than twentyfour (24) months or such other date as determined by the TSC (such
period the “Transition Period”), the TSC voting members would consist of all
founding participants who participate in the development process prior to project
announcement. The list of voting members of the TSC will be maintained on the “CONTRIBUTING” file within the Project’s code repository.
"Steady State”: After the Startup period, the size, makeup and procedure for
determining voting members of the TSC will be as determined by the TSC and
documented within a TSC procedures document that is maintained on
“PROCEDURES” file within the Project’s code repository.
Contributors and Committers
TSC projects generally will involve Contributors and Committers. The TSC may
adopt or modify roles so long as the roles are documented in the CONTRIBUTING file. Unless otherwise documented:
- Contributors include anyone in the technical community that contributes
code, documentation, or other technical artifacts to the Project; - Committers are Contributors who have earned the ability to modify
(“commit”) source code, documentation or other technical artifacts in a
project’s repository; and - A Contributor may become a Committer by a majority approval of the
existing Committers. A Committer may be removed by a majority
approval of the other existing Committers.
...
Charter (Mission and Scope of the Project, TSC, TSC Voting, Compliance with Policies, Community Assets, General Rules and Operations, Intellectual Property Policy, Amendments)
Current Members
Project
- coordinating the technical direction of the Project;
- approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);
- organizing sub-projects and removing sub-projects;
- creating sub-committees or working groups to focus on cross-project technical issues and requirements;
- appointing representatives to work with other open source or open standards communities;
- establishing community norms, workflows, issuing releases, and security issue reporting policies;
- approving and implementing policies and processes for contributing (to be published in the CONTRIBUTING file)
- resolve matters or concerns that may arise;
- discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and
- coordinating any marketing, events, or communications regarding the Project.
...
While the Project aims to operate as a consensus- based community, if any TSC decision requires a vote to move the Project forward, the voting members of the TSC will vote on a one vote per TSC member basis.
Quorum for TSC meetings requires at least fifty percent of all voting members of the TSC to be present. The TSC may continue to meet if quorum is not met but will be prevented from making any decisions by vote at the meeting.
Except as provided in Section 7.c. and 8.a, of the Technical Charter decisions by vote at a meeting require a majority vote of those in attendance, provided quorum is met. Decisions made by electronic vote without a meeting require a majority vote of all voting members of the TSC.
In the event a vote cannot be resolved by the TSC, any voting member of the TSC may refer the matter to the Series Manager or LFN TAC for assistance in reaching a resolution.
Project Roles
- An initial TSC has been established per above. TSC eligibility is defined per above and aligns with the Technical Charter . Contributor and Committer are defined per above. TSC Chair, TAC representative, and MAC liaison roles will be assigned through nomination, then TSC voting. Additional roles, including Project Technical Leads (PTLs) may be defined as project needs arise.
- The TSC Representation table is here. The TSC represents the top-level decision-making body for the project.
- Additional project roles, as needed, are filled by TSC voting (majority)
- Removal from a Project Role-
- A person may voluntarily resign from a project role by making a public announcement to the TSC.
- A person in a project role who is disruptive, or has been inactive on that project for an extended period (e.g., six or more months), or is not abiding by the project charter or code of conduct may have his or her role status revoked by the TSC.
- Disputes are resolved by TSC voting (majority)
(Proposal) Code of Conduct
The community follows and abides by the L3AF Code of Conduct and Reporting process set forth by the Linux Foundation herein: https://events.linuxfoundation.org/about/code-of-conduct/
(Proposal) Diversity & Inclusivity
The community follows and abides by the Diversity & Inclusivity initiatives set forth by the Linux Foundation: https://linuxfoundation.org/diversity-inclusivity/
Current list of Committers (Placeholder - in progress)
Process for Adding Repositories (Placeholder- in progress)
Process for Selecting Maintainers of Each Repository (Placeholder- in progress)
Committers and Process for Selecting Maintainers
Committers and Process for Adding/Removing Them
Process for Adding Repositories
Adding projects/repos to l3af-projectSelecting maintainers for repositories shall be established by a nomination period, followed by TSC vote (majority). Who is eligiable to send forth a nomintation. Project Commiters.