You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For votes/approvals/reviews it would be useful to have a github team that matches the voting members (which is what I'd expected).
I would propose we fix up these discrepancies (I can do PRs).
This would also require that any potential removals get added to a regular contributors group so they don't lose access.
Alternative we add new 'tsc-voting' or 'tac-voting' teams, but I think this is unnecessary.
This came about because I just wanted to update CODEOWNERS on pqcap tsc so that reviews were automatically generated for tsc members - something we could also do for the PQCA TAC.
I've noticed that for
That there is a tac/tsc github team. However these teams do not match the voted members, or the frequent attendees.
For example
For votes/approvals/reviews it would be useful to have a github team that matches the voting members (which is what I'd expected).
I would propose we fix up these discrepancies (I can do PRs).
This would also require that any potential removals get added to a regular contributors group so they don't lose access.
Alternative we add new 'tsc-voting' or 'tac-voting' teams, but I think this is unnecessary.
This came about because I just wanted to update CODEOWNERS on pqcap tsc so that reviews were automatically generated for tsc members - something we could also do for the PQCA TAC.
Thoughts @ryjones @maximilien . I can do appropriate PRs to fix.
The text was updated successfully, but these errors were encountered: