Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

This document provides a collection of norms for how the Magma TSC operates.

Goals

  • Engage the community to define Magma roadmap
  • Co-ordinate priorities across different work streams
  • Monitor CI health and escalate requests from DevOps teams
  • Review and vote on technical proposals
  • Ensure that code-owners are active and PRs are not getting stale
  • Define best practices for the project and TSC

Weekly meetings

TSC weekly meetings cover the following agenda items, some of which are optional

  • Roadmap planning
  • Weekly check-ins on all work streams: PoCs of each work stream can bring in highlights/lowlights to TSCs attention 
    • Release updates
    • DevOps
    • Testing
    • Outreach
    • Security
    • Feature development
    • Better Engineering
  • (Optional) Demos/presentations:
    • New features
    • New deployments
  • TSC chair updates:
    • Governing Board meeting prep
    • Governing Board meeting debrief
  • Review proposals
    • Presentations from authors
    • Voting


Positions

TSC

Positions are elected via majority vote from the codeowners. Last until earliest of:

  • 1-year term (pending TSC-wide phase-adjustment)
  • Resignation
  • TSC-majority vote to end term early

TSC chair

Position is elected via majority vote from the TSC. Last until earliest of:

  • 1-year term (pending TSC-wide phase-adjustment)
  • Resignation
  • TSC-majority vote to end term early

Voting considerations

  • Majority vote means >50% of the vote -- a tie vote means the motion fails
  • There is no consideration for quorum for the following votes -- motions require yea votes from >50% of the full voting body
    • Ending a TSC member's term early
    • Voting in the TSC chair

Additional norms

  • In the event of disagreements within the TSC, codeowners, or community on whether bylaws and norms were followed, or whether the set of bylaws and norms are reasonable, escalation routes first through the Governance Board, then finally to LinuxFoundation when necessary
  • TSC chair election to align with calendar year
  • Phase-adjustment: TSC 1-year terms to be phased such that, at a uniform turnover rate, full turnover would not occur in less than 6 months. E.g., if the TSC had 6 members, phase the term end-dates out by 1 month each
  • TSC votes are held in the magma-tsc-voting@lists.magmacore.org mailing list
  • Codeowner votes are held as per the guidelines on Community Structure and Governance GitHub Wiki
  • No labels