TSC members
- Norman Ashley (Cisco)
- Michael Baentsch (independent contributor)
- Thomas Bailleux (SandboxAQ)
- Basil Hess (IBM Research)
- Brian Jarvis (AWS)
- Christian Paquin (Microsoft Research)
- Douglas Stebila (University of Waterloo)
Other attendees
- Nigel Jones (IBM)
- Alex Bozarth (IBM)
- Michael (Max)imilien, IBM
- Ry Jones (Linux Foundation)
- Hart Montgomery, Linux Foundation
- The chair thanks members for being patient as we get up and running
- TSC aims to be consensus driven & friendly
- TSC will discuss & make strategic decisions on technical matters. Developer call handlers regular operational matters
- Agreed
- Nigel will take this week's notes. Agreed that we would ask at the beginning of each meeting & do in rotation.
- Last meeting's notes are open as PR #14. Comments/reviewers invited. TSC members asked to approve.
- will use direct links to recordings in future minutes - portal not available to all (has been requested)
- Issue #12 open for discussion
- online/async voting to allow broadest engagement
- open votes for technical matters
- differing opinions on whether personal matters (including voting such as ranking) should be public or secret, or referred up to the board.
- noted that most decisions consensus driven in any case
- mechanism - git (simple), gitvote, Helios are possible options
- discussion to continue in issue 12
- Vlad is maintainer of language wrappers
- Intent had been he was in the TSC from launch
- Christan proposed, Basil seconded motion to add Vlad. Agreed by verbal vote of TSC members with no objections
- Monthly still seems appropriate - lots of topics
- Two suggestions:
- in PQCA TAC timeslot (alt. weeks) in off-week
- offline poll to accommodate most TSC members, and consider time rotation to handle differing timezones. This may require a higher frequency than monthly
- Agreed poll will be conducted
- Project Lifecycle.
- Early draft
- PQCA TAC suggests oqs tsc review and develop as most active project.
- objective is clarity for consumers as to what state the code is in - production, experimental, how good is security, maintenance - don't want to set wrong expectations.
- Also covers adoption of new projects. Similar to apache incubation approach
- may apply at sub-project or component level
- should map existing oqs subprojects/components to proposal for validation
- clear separation may require feature flags, restructuring of liboqs, additional projects etc
- should delegate to OQS dev meeting to decide/discuss in github issues
- Issue will be opened for followup
- Security
- PQCA setting up security workgroup
- Hoping to arrange presentation from OSSF around scorecard & other best practices. TSC members will be invited
- Also Use of sigstore, CBOMs, SBOMs, vulnerability reporting process
- Issue #13 has background
- Current project charter requires contributions under MIT license
- Discussed allowing Apache 2.0 as an exception for this work, or changing charter to allow generally
- Issue #17 for TSC members to vote on exception
No discussion beyond 8. above - timeout
No discussion beyond 8. above - timeout
None
A transcript and recording of this meeting is available