Skip to content
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

Standards Committee Voting Process #1

Open
sierra-moxon opened this issue Feb 27, 2025 · 1 comment
Open

Standards Committee Voting Process #1

sierra-moxon opened this issue Feb 27, 2025 · 1 comment

Comments

@sierra-moxon
Copy link
Member

When voting on topics for the Standards Committee, we will use an Issue like this one. Each committee member will be tagged here and will be expected to vote.

A Thumbs-up 👍 will be viewed as a vote FOR the motion, and a Thumbs-down 👎 will be viewed as a vote AGAINST the motion. The "eyes" 👀 emoji will represent an abstention.

Once an outcome has been reached, the group leader or PM will post a final decision message listing the votes for each option and close the issue.

@sierra-moxon
Copy link
Member Author

sierra-moxon commented Feb 27, 2025

Questions for review during the first Standards Committee Meeting:

  1. What is the level of decision that requires an official vote? (do PRs and PR reviews constitute voting?)
  2. What is the granularity of an official voting decision issue (can we bundle a week's worth of agenda items into a vote, or is each agenda item its own vote?)
  3. Who follows up with voters yet to cast their vote?
  4. What is the timeframe for a vote, and how do we plan for votes that need time while also being agile in development?
  5. How do votes in the Standards Committee bubble up to the Planning Committee (e.g., if we have a TRAPI release, where do we report that information and is it up to the Standards committee to initiate a vote of its members, or is that a consortium-wide vote).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant