Seconds! Defining alternate project representatives #203
Replies: 4 comments 6 replies
-
|
You're saying we won't track the "primary" between the 2 names? And if both vote, we only take primary. If only secondary votes we take that one. Is that correct? How do we handle two votes with different choices? Particularly if the secondary has concerns the primary hasn't raised? |
Beta Was this translation helpful? Give feedback.
-
|
Primary has precedence.
Correct. This is (by definition) a trust exercise, but training a successor and having a backup leader is always a trust exercise, isn't it? As far as raising concerns goes, both will be able to see and contribute to the discussion. So if there are concerns to raise, both would have the opportunity to raise them. |
Beta Was this translation helpful? Give feedback.
-
|
That all sounds good. Do we need to have anything related to handling a primary voting "yes" and a secondary voting "no". Or do we just take the "primary" vote and leave it to the project to resolve their different perspectives? |
Beta Was this translation helpful? Give feedback.
-
|
Tooling will handle taking the primary... and yes, the project will have to handle their differences of opinion. |
Beta Was this translation helpful? Give feedback.
-
|
👍🏻 There is value in also showing when a primary and secondary do agree, both as a matter of cohesion, and for legal matters since these would be in written records in the case of later conflict. |
Beta Was this translation helpful? Give feedback.
-
|
This vote has been closed by ebullient:
✅ 9 of 13 members of @commonhaus/cf-egc have voted (reaction, quorum=2/3).
Additional input (🙏 🥰 🙌): |
Beta Was this translation helpful? Give feedback.
-
|
Seems like something we've discussed about? @cowtowncoder |
Beta Was this translation helpful? Give feedback.
-
|
Yes @JooHyukKim . |
Beta Was this translation helpful? Give feedback.
-
|
Exactly. This is mechanically how I bring you in, @JooHyukKim. ;) |
Beta Was this translation helpful? Give feedback.
-
|
vote::result We're in agreement. I'll get to work. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Proposal
We've made it pretty clear that each project gets one vote.
What should also be clear is that we want to move away from single points of failure, too.
I'd like to encourage all projects to have a "second" EGC rep.
In my mind, the second vote is counted only when the primary is missing. When that is the case, that vote also does count when tallying quorum.
In some sense, it then is up to the project who is the primary and who is the secondary depending on time commitments, etc. Both would have access to egc discussions and lists.
Anything I missed?
Voting group
@commonhaus/cf-egc
Consensus mechanism
Please use emoji reactions to indicate your support:
Ask questions or raise concerns in comments.
Beta Was this translation helpful? Give feedback.
All reactions