Skip to content

Latest commit

 

History

History
123 lines (88 loc) · 7.23 KB

TECH-OVERSIGHT-COMMITTEE.md

File metadata and controls

123 lines (88 loc) · 7.23 KB
Raw
title linkTitle weight type aliases
Knative technical oversight committee
Technical oversight committee
35
docs
/contributing/tech-oversight-committee/

The Knative Technical Oversight Committee (TOC) is responsible for cross-cutting product and design decisions.

Charter

  • Technical Project Oversight, Direction & Delivery

    • Set the overall technical direction and roadmap of the project.

    • Resolve technical issues, technical disagreements and escalations within the project.

    • Set the priorities of individual releases to ensure coherency and proper sequencing.

    • Approve declaring a new long-term supported (LTS) Knative release.

    • Approve the creation and dissolution of working groups and approve leadership changes of working groups.

    • Create proposals based on TOC discussions and bring them to the relevant working groups for discussion.

    • Approve the creation/deletion of GitHub repositories, along with other high-level administrative issues around GitHub and our other tools.

  • Happy Healthy Community

    • Establish and maintain the overall technical governance guidelines for the project.

    • Decide which sub-projects are part of the Knative project, including accepting new sub-projects and pruning existing sub-projects to maintain community focus

    • Ensure the team adheres to our code of conduct and respects our values.

    • Foster an environment for a healthy and happy community of developers and contributors.

Committee Mechanics

The TOC is elected by the community.

The TOC’s work includes:

  • Regular committee meetings to discuss hot topics, resulting in a set of published meeting notes.

  • Create, review, approve and publish technical project governance documents.

  • Create proposals for consideration by individual working groups to help steer their work towards a common project-wide objective.

  • Review/address/comment on project issues.

  • Act as a high-level sounding board for technical questions or designs bubbled up by the working groups.

Committee Meeting

Community members are encouraged to suggest topics for discussion ahead of the TOC meetings, and are invited to observe these meetings and engage with the TOC during the community feedback period at the end of each meeting.

Artifact Link
Google Group [email protected]
Community Meeting VC See the top of the Meeting notes
Community Meeting Calendar Thursdays at 8:30a-9:15a
Calendar
Meeting Notes Notes
Document Folder Folder

Committee Members

The current members of the TOC are shown below.

  Member Company Profile Term Start Term End
Dave Protasowski VMware @dprotaso 2021-05-26 2024
David Simansky Red Hat @dsimansk 2022-06-01 2024
Evan Anderson VMware @evankanderson Bootstrap 2023
Scott Nichols Chainguard @n3wscott 2022-01-11 2024
Zbynek Roubalik Red Hat @zroubalik 2022-06-01 2024

Emeritus Committee Members

To recognize the folks that have served in the TOC in the past, below we list the previous members of the TOC (sorted by their 'Term End').

  Member Profile Term Start Term End
Ville Aikas @vaikas Bootstrap 2020
Nghia Tran @tcnghia 2020 2021
Matt Moore @mattmoor Bootstrap 2021
Grant Rodgers @grantr 2020 2021
Markus Thömmes @markusthoemmes 2020-06-09 2021-12-16
Julian Friedman @julz 2021-05-26 2022-02-07
Roland Huß @rhuss 2021-02-16 2022
Matt Moore @mattmoor 2022-02-07 2022

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License.