Date: Wednesday, December 6, 2023 - 9AM/12PM PT/ET | Google Meet Link
Participants:
- Ann Ming Samborski (BastionZero)
- Ethan Heilman (Bastionzero)
- Joel Kamp (Docker)
- Jonny Stoten (Docker)
- Lucie Mugnier (BastionZero)
- TSC chair election
- Discuss how we document and standardize OpenPubkey
- What format do we use? RFC-like Mediawiki?
- Where do we store the standards?
- How do we propose, review and approve /reject it?
- Ownership of non-core OpenPubkey repositories
- Standardizing admin/write access to repositories
Ethan is chair by unanimous agreement by TSC members.
RFC is a nice format, but there are concerns it is too formal to serve the community as a whole.
The goal is to give the community a structured way to interact with the design of OPK rather than just the code.
For now, we think a Markdown file in GitHub makes sense (within the openpubkey/openpubkey repo) so folks can make PRs against it. Two examples for consideration: in-toto/attestation and secure-systems-lab/dsse. We would like to adopt RFC-2119 that defines usage of "must," "should," and "may." Diagrams in Markdown can use Mermaid or if a more complex diagram is necessary, can always embed an image.
Ethan is taking an action item to draft this proposal up to discuss in the next community meeting.
The repositories will remain in the OPK repository for now.
The desire is for all members of the TSC to have admin/write access to the OpenPubkey repositories.
Rather than fight with group permissions, Ethan changed all members of TSC to owners of OpenPubkey. They agreed they will not make org-level changes without making the other members aware and making sure there is agreement.
- Ethan to put a proposal together for how to document and standardize OpenPubkey. He will share it with community and discuss this at the next community meeting.