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

async voting process #292

Merged
merged 3 commits into from
Sep 6, 2018
Merged

async voting process #292

merged 3 commits into from
Sep 6, 2018

Conversation

ultrasaurus
Copy link
Contributor

this is based on what I've observed in TOC votes and seems to work well in practice (though I've only followed a few votes)

GOVERNANCE.md Outdated
@@ -54,6 +54,11 @@ If a vote is taken during a WG meeting, the follow rules will be followed:
[here](https://docs.google.com/spreadsheets/d/1bw5s9sC2ggYyAiGJHEk7xm-q2KG6jyrfBy69ifkdmt0/edit#gid=0).
Members must acknowledge their presence verbally, meaning, adding yourself
to the "Attendees" section of the Agenda document is not sufficient.
* When a vote is called, votes will be collected over the following week:
Copy link
Collaborator

@duglin duglin Aug 16, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer if we didn't mandate a week since its possible all voting members are on the call when the vote is started. So what about:

  • When a vote is called if all voting members are present in the meeting, and they all agree to vote at that time, then votes will be tallied during that meeting.
  • If not all voting members are present, or some wish more time, then those members will be allowed one week to vote asynchronously. In the case of a PR vote, they will post a comment to the PR with their vote. In other cases an email to the CloudEvents mailing list is expected.
  • In the case of yes/no votes, each vote will be either "yes", "no" or "abstain". In the case of non-yes/no votes, the WG will agree on the valid responses prior to starting the vote.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking that async voting would replace the roll-call style voting on the call, making better use of people's time, and it can also serve to capture any statements people make about why they are voting one way or another, which would be great to know if the group decides to revisit a decision in the future.

@duglin
Copy link
Collaborator

duglin commented Aug 16, 2018

Can you sign your commit? The DCO check is not happy

this is based on what I've observed in TOC votes and seems to work well in practice (though I've only followed a few votes)

Signed-off-by: Sarah Allen <sarahallen@google.com>
Signed-off-by: Sarah Allen <sarahallen@google.com>
@ultrasaurus
Copy link
Contributor Author

Clarification: wait +1 week is only if everyone hasn't voted

GOVERNANCE.md Outdated
@@ -54,6 +54,14 @@ If a vote is taken during a WG meeting, the follow rules will be followed:
[here](https://docs.google.com/spreadsheets/d/1bw5s9sC2ggYyAiGJHEk7xm-q2KG6jyrfBy69ifkdmt0/edit#gid=0).
Members must acknowledge their presence verbally, meaning, adding yourself
to the "Attendees" section of the Agenda document is not sufficient.
* When a vote is called, unless all viting members have voted, the vote will be
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/viting/voting/

GOVERNANCE.md Outdated
* When a vote is called, unless all viting members have voted, the vote will be
tallied no less than one week after calling the vote.
* Voting process:
* Comment on the PR: "agree, yes, +1", "disagree, no, -1", or "abstain".
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make this a bit more concrete and less chance of someone using the word "agree" w/o realizing they're voting.
Comment on the PR: LGTM, NOT LGTM or ABSTAIN

Signed-off-by: Sarah Allen <sarahallen@google.com>
@duglin
Copy link
Collaborator

duglin commented Sep 6, 2018

Approved during the 9/6 call

@duglin duglin merged commit 1adb7cf into cloudevents:master Sep 6, 2018
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

Successfully merging this pull request may close these issues.

2 participants