Skip to content

Latest commit

 

History

History
135 lines (85 loc) · 6.16 KB

governance.md

File metadata and controls

135 lines (85 loc) · 6.16 KB
Raw

The Spinnaker OSS project is run by a group of appointed members who hold specific roles, managed by the technical oversight committee. The steering committee manages the governance structure of the project, revisiting and refining it as needs evolve.

The broader community is organized around a set of special interest groups (SIGs) focused on particular areas of interest.

Roles

To make clearer to community members how they might progressively get more involved and take more ownership in the project, we define the following appointed roles with their respective duties and qualifications.

Roles are appointed by the Technical Oversight Committee (TOC). Roles can be revoked for reasons such as falling out of qualification, inactivity, or for violations of community guidelines.

Active Community Members

Everyone is a welcome community member! Here are some things that we find extraordinarily helpful:

  • Answering questions in our Slack team
  • Leave feedback on PRs - questions, code style, and bug spotting are all helpful
  • Help new developers get started
  • Reproduce bugs and add detail to issues
  • Join (or lead!) a SIG and discuss issues facing our community

Reviewers

Duties

  • Review, provide meaningful feedback and LGTM PRs
  • Triage GitHub issues, community forum submissions
  • Provide general support in Slack

Qualification guidelines

  • Known active participant in the community
  • Has submitted at least 5 PRs of significant scope that are correspondingly merged
  • Sponsored by 2 Approvers

Current Reviewers

If you’d like to nominate yourself as a Reviewer, please create an Issue in the governance repository.

Approvers

Duties

  • Final review for PRs
  • Merge code into master
  • All Reviewer duties

Qualification guidelines

  • Is already fulfilling the Reviewer role
  • Belongs to an organization with significant stake in project
  • Known active participant in the community
  • Has submitted at least 5 PRs of significant scope that are merged
  • Has reviewed 5 PRs of significant scope
  • Sponsored by 2 Approvers

Current Approvers

If you’d like to nominate yourself as an Approver, please create an Issue in the community repository.

SIG Leads

SIG Leads are responsible for management of a particular Special Interest Group within the project, managing day-to-day operations of their interest scope. If a particular SIG involves altering Spinnaker's codebase, then SIG leads must be active Approvers.

Duties

  • Set agenda for, facilitate, and drive SIG meetings
  • Review and sponsor proposals related to the SIG
  • Triage inbound spinnaker/spinnaker issues related to the SIG
  • Review and merge or decline pull requests from the community

Technical Oversight Committee

The TOC is responsible for the overall technical management of the project, ultimately managing the day-to-day running of the project.

Duties

  • Set agenda for, facilitate, and drive consensus in the TOC meetings
  • Final escalation point for technical guidance
  • Review, approve and revoke appointments for Reviewers and Approvers
  • Drive technical management and any specific guidelines (e.g. code requirements/conventions, SLA on PR reviews)
  • Promote the best interests of the project

Qualifications

  • Nominated and Appointed by Steering Committee
    • 2-year terms, term limit of consecutive 4 years (after, individual must take at least 1 year off)
    • Terms should be staggered within the TOC and off by 6 months from SC
    • Staggering should result in approximately half of the committee up for election each year
    • Term starts mid-calendar year (i.e. July 1st)

Election to the TOC requires a majority of the SC.

Technical Oversight Committee

The TOC will have three, five, or seven members, as deemed appropriate by the Steering Committee. In the event that someone from the TOC leaves during their term, the Steering Committee shall appoint someone to fill the remainder of the term. Each year, the TOC will nominate a member to serve as the Chairperson for that year. The Chair's duties will include calling and runnings meetings, calling votes, and ensuring that meeting notes are recorded.

Steering Committee

The steering committee’s responsibility and function lies in the continual shaping of the governance structure to serve the project’s needs best.

Duties:

  • Set governance structure of the project
  • Address questions or concerns from the community about project culture, structure, and clarifications of roles, responsibilities and duties
  • Ratify new SIGs

Qualifications:

  • Nominated and Appointed by Steering Committee
    • 2 year terms, term limit of 4 years consecutively^ (after which, an individual must take off at least 1 year)
    • Terms should be staggered, which should result in approximately half of the committee up for election each year
    • Terms run from February 1st to January 31st two years later

^ - SC members whose terms were extended by one month when the terms were shifted from starting January 1st to starting February 1st may serve 4 years and one month consecutively.

Logistics

Current SC members:

  • Edgar Magana (Salesforce) - Term expires 2023.01.31
  • Isaac Mosquera (Armory) - Term expires 2022.01.31
  • Matt Duftler (Google) - Term expires 2022.01.31
  • Paul Roberts (AWS) - Term expires 2023.01.31
  • Peter Stout (Netflix) - Chair - Term expires 2022.01.31

Election to the SC requires a majority of the SC. If a person is up for reelection they are not allowed to vote for their reelection.

Special Interest Groups

Special Interest Groups (SIGs) are created as community interest and demand around particular topics become self evident, and continue on as their relevance and needs do. SIGs and their Leads are ratified and green-lit by the Steering Committee via a SIG proposal process.