This content is moving to the L3AF Governance Repository on Github. Please see this issue to track the progression of that work:
Technical Steering Committee
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 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)
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/
Committers and Process for Selecting Maintainers
Committers and Process for Adding/Removing Them
Process for Adding Repositories
Adding projects/repos to l3af-project
...
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.
Participation in the Project through becoming a Contributor and Committer is
open to anyone so long as they abide by the terms of the project Charter and established governance.
f.
The TSC may (1) establish work flow procedures for the submission, approval,
and closure/archiving of projects, (2) set requirements for the promotion of
Contributors to Committer status, as appl
icable, and (3) amend, adjust, refine
and/or eliminate the roles of Contributors, and Committers, and create new roles,
and publicly document any TSC roles, as it sees fit.
g.
The TSC may elect a TSC Chair, who will preside over meetings of the TSC and
will s
erve until their resignation or replacement by the TSC.
h.
Responsibilities: The TSC will be responsible for all aspects of oversight relating
to the Project, which may include:
i.
coordinating the technical direction of the Project;
ii.
approving project or system proposals (including, but not limited to,
incubation, deprecation, and changes to a sub
-
project’s scope);
iii.
organizing sub
-
projects and removing sub
-
projects;
iv.
creating sub
-
committees or working groups to focus on cross
-
project
tec
hnical issues and requirements;
v.
appointing representatives to work with other open source or open
standards communities;
DocuSign Envelope ID: 0F398833-D926-477D-8CD7-735475E30340
3
vi.
establishing community norms, workflows, issuing releases, and security
issue reporting policies;
vii.
approving and implementing policies a
nd processes for contributing (to be
published in the CONTRIBUTING file) and coordinating with the series
manager of the Project (as provided for in the Series Agreement, the
“Series Manager”) to resolve matters or concerns that may arise as set
forth in S
ection 7 of this Charter;
viii.
discussions, seeking consensus, and where necessary, voting on technical
matters relating to the code base that affect multiple projects; and
ix.
coordinating any marketing, events, or communications regarding the
Project.
3.
TSC Voting
a.
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 voting member basis.
b.
Quorum for TSC meetings requires at least fift
y 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 at the meeting.
c.
Except as provided in Section 7.c. and 8.a, 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.
d.
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 for assistance in reaching a resolution