Skip to content

Latest commit

 

History

History
41 lines (37 loc) · 4.15 KB

CONTRIBUTING.md

File metadata and controls

41 lines (37 loc) · 4.15 KB

See the Contributor Guide for information on developer onboarding, workflow, contribution conventions, presubmit checks and more.

Please read also the DCO for details regarding regarding the sign-off rules for a contribution.

  1. TSC Responsibilities

    1. As outlined in the Magma Technical Charter, the TSC will be responsible for all aspects of oversight relating to the Project, which may include:
      1. coordinating the technical direction of the Project;
      2. approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);
      3. organizing sub-projects and removing sub-projects;
      4. creating sub-committees or working groups to focus on cross-project technical issues and requirements;
      5. appointing representatives to work with other open source or open standards communities;
      6. establishing community norms, workflows, issuing releases, and security issue reporting policies;
      7. approving and implementing policies and 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 Section 7 of this Charter;
      8. discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and
      9. coordinating any marketing, events, or communications regarding the Project.
    2. Allocations recommendations to the Linux Foundation as per approved budgets.
  2. TSC Voting Members

    1. The TSC will be composed of seven (7) members.
    2. Each TSC member will be elected to a one year term.
      1. If a TSC member is inactive, the other TSC members have the authority to vote the inactive member off the TSC with a two thirds vote.
      2. In the case that a TSC member resigns or is removed, a special election to fill the open seat would occur following the same election process outlined in section 3. 3.There will be an annual election to determine the composition of the TSC.
    3. Employees from the same organization/company should not hold more than one TSC seat.
  3. TSC Elections

    1. Candidate Eligibility
      1. Current TSC members and active contributors are eligible to run for a voting seat on the TSC.
      2. Candidates may self-nominate or be nominated by an individual who is qualified as a TSC voter as defined in Section 3.b.ii.
    2. Voter Eligibility
      1. Any individual who has contributed to a Magma repo in the twelve months prior to the election is eligible to vote and run for a voting seat in the TSC election.
      2. Contributions include, but are not limited to, opening PRs, reviewing and commenting on PRs, opening and commenting on issues, writing design docs, commenting on design docs, participating in mailing list or Slack discussions and participating in working groups.
      3. Each election cycle, an initial set of voters will be identified through automated reporting. Any individual who has at least 20 measurable contributions in the last 12 months will be automatically added to the eligible voter list.
      4. If a community member has contributed over the past year but is not captured in automated reporting, they will be able to submit an eligibility form to the current TSC who will then determine whether this member will be eligible.
    3. Election Method and Tools
      1. If the number of candidates is equal to or less than the number of TSC seats available to be elected, the candidates shall be approved after the nomination period has closed.
      2. If there are more Qualified Nominees than open TSC seats available for election, all eligible voters shall elect the TSC members using a time-limited Condorcet ranking method.
      3. Elections may be run via OpaVote.