-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minutes from 2024-03-11 TSC meeting #14
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,82 @@ | ||
# OQS Technical Steering – 2024-03-11 – minutes | ||
|
||
## Attendees | ||
|
||
TSC members | ||
|
||
- [x] [Norman Ashley (Cisco)](https://github.com/ashman-p) | ||
- [x] [Michael Baentsch (independent contributor)](https://github.com/baentsch) | ||
- [x] [Thomas Bailleux (SandboxAQ)](https://github.com/) | ||
- [x] [Basil Hess (IBM Research)](https://github.com/bhess) | ||
- [x] [Brian Jarvis (AWS)](https://github.com/brian-jarvis-aws) | ||
- [x] [Christian Paquin (Microsoft Research)](https://github.com/christianpaquin) | ||
- [x] [Douglas Stebila (University of Waterloo)](https://github.com/dstebila) | ||
|
||
Other attendees | ||
|
||
- Alex Bozarth | ||
- Deirdre Connolly | ||
- Jason Goertzen | ||
- Nigel Jones | ||
- Ry Jones | ||
- Michael Maximilien | ||
- Hart Montgomery | ||
- Massimiliano Pala | ||
- Spencer Wilson | ||
|
||
## 0. Welcome | ||
|
||
Douglas welcomes attendees to the first meeting of the OQS TSC. | ||
|
||
## 1. Election of a TSC chair | ||
|
||
Douglas opens the floor to nominations for a TSC chair. | ||
|
||
Ry recommends that the TSC appoint a chair and a co-chair, who can lead meetings in the chair's absence and assist with organization. | ||
|
||
The following names are nominated for chair or co-chair: | ||
|
||
- Douglas | ||
- Max | ||
- Basil | ||
- Brian | ||
- Thomas | ||
|
||
It is noted that the chair and co-chair need to be a voting member of the TSC, so Max is not eligible. | ||
|
||
Douglas asks each nominee if they would like to stand for chair or co-chair. The responses are: | ||
|
||
- Douglas: chair or co-chair | ||
- Basil: co-chair | ||
- Brian: co-chair | ||
- Thomas: co-chair | ||
|
||
Decision: For election of the chair, a roll call vote is held. Douglas is elected chair. | ||
|
||
Decision: For election of a co-chair, each TSC member is asked to send a private message to Ry Jones via Zoom chat, who will tally the votes. Ry reports that Basil received the largest vote. | ||
|
||
## 2. Establishing a voting procedure | ||
|
||
Action: Douglas and Ry will initiate a voting procedure discussion on Github which will be brought back to this body at a future meeting for approval. | ||
|
||
## 3. Meeting cadence | ||
|
||
A discussion is held about how frequently the TSC wants to meet, with options suggested including bi-weekly or monthly. Rough consensus appears to be around monthly, but that it could change as needed. There is a suggesting to have a rotating meeting time to accommodate multiple time zones. | ||
|
||
Action: Douglas to poll for a meeting time for the next meeting April. | ||
|
||
## 4. Reviewing status of sub projects (https://github.com/open-quantum-safe/tsc/issues/2) | ||
|
||
Action: Douglas to create an issue in the TSC repository for continuing discussion of subproject lifecycle. We will look to see what the PQCA TAC establishes for its project lifecycle and consider whether those levels are appropriate for our subprojects, or whether another classification (e.g., 3 tiers: fully supported, best effort, inactive) is better for us. | ||
|
||
## 5. Identifying a representative from the OQS TSC to the PQCA Technical Advisory Committee | ||
|
||
Douglas opens the floor to nominations for the representative from the OQS TSC to the PQCA TAC. | ||
|
||
Thomas is nominated. No further nominations are received. | ||
|
||
Decision: An approval vote for Thomas is held via Zoom DM to Ry. The vote passes. | ||
|
||
## 6. Discussing plan for level of code support and the production vs. research tracks | ||
|
||
Deferred to a later meeting. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not recall general agreement to the secret voting procedure executed at this point.
This comment is not to question the election of @bhess particularly seeing it as a bellwether to more contributions by IBM. This comment shall just serve to give the other companies in the project a chance to also voice (publicly) their agreement (or otherwise) of this:
IMO OQS should remain as vendor-independent as it always was and this election should not be considered a departure from this principle.
Considering #12 addresses the issue going forward I don't see a reason to not approve the minutes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Michael, since indeed there was not a TSC decision about the voting procedure used during that meeting, I didn't want to convey that there had been a decision about the voting procedure, and rather wanted the minutes to reflect what voting procedure was used in that moment so at least that was recorded.