Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
icableapplicable, 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 serve 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;

...

  • 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 a

...

  • nd 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.


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 TSC member basis.
b.

Quorum for TSC meetings requires at least fift
y 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.
c.

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.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 or LFN TAC for assistance in reaching a resolution.