The sigstore Technical Steering Committee is responsible for technical oversight of sigstore's projects.
The TSC will be responsible for all aspects of oversight relating to the Project:
- Coordinating the technical direction of the Project;
- Approving project or system proposals (including, but not limited to, incubation, deprecation, and changes to a sub-project’s scope);
- Organizing sub-projects and removing sub-projects;
- Creating sub-committees or working groups to focus on cross-project technical issues and requirements;
- Appointing representatives to work with other open source or open standards communities;
- Establishing community norms, workflows, issuing releases, and security issue reporting policies;
- 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 the technical charter.
- Discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; and coordinating any marketing, events, or communications regarding the Project.
Informal discussions occur in the tsc channel of the sigstore Slack.
Use GitHub Issues to request and discuss agenda items.
The TSC meetings minutes.
Meetings are also recorded and posted to the sigstore YouTube channel.
| Name | Organization | |
|---|---|---|
| Bob Callaway | bcallaway@google.com | |
| Luke Hinds (TSC Chair) | luke@stacklok.com | Stacklok |
| Priya Wadhwa | priya@chainguard.dev | Chainguard |
| Trevor Rosen | trevrosen@github.com | GitHub |
| Santiago Torres-Arias | santiagotorres@purdue.edu | Purdue University |
The TSC is technical charter is available here docs/CHARTER.MD