TSC Processes

Owned by Kendall Perez
Last updated: Jun 06, 2022 by Shruti Sanadhya
2 min read

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, so they are all aligned with the roadmap execution

  • Monitor CI health and escalate requests from DevOps teams

  • Steer technical proposals to ensure timely review and decision

  • Ensure that code-owners are active and PRs are not getting stale

  • Provide quarterly updates to the governing board on the progress of the project

  • Define best practices for the project and TSC

Weekly meetings

TSC weekly meetings cover the following agenda items

  • 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

    • Security

    • Feature development

    • Better Engineering

    • (Optional) Outreach

  • (Optional) Demos/presentations:

    • New features

    • New deployments

  • TSC chair updates:

    • Governing Board meeting prep

    • Governing Board meeting debrief

  • Review proposals

    • Assign TSC PoCs for each proposal

    • Presentations from authors

    • Voting

 

Positions

TSC voting members

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

Responsibilities: Contribute towards the TSC goals, listed above.

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

Responsibilities:

  • Be the interface between TSC and Governing Board

  • Support the DevOps team in prioritizing CI issues and improvements

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