...
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.
e.
Participation in the Project through becoming a Contributor and Committer is
open to
anyone so long as they abide by the terms of this 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
...