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

Delegate/Community Voting #169

Open
lgarron opened this issue Apr 22, 2014 · 3 comments
Open

Delegate/Community Voting #169

lgarron opened this issue Apr 22, 2014 · 3 comments

Comments

@lgarron
Copy link
Member

lgarron commented Apr 22, 2014

Right now, I believe that a complicated protocol for changes (#108) isn't as important as making sure that enough people take the time to think about a big change before it becomes finalized. If something is put to a Delegate vote with proper pros/cons, I'm confident that we will make reasonable decisions.
Here's a rough outline for handling an important topic:

  • Gather the main ideas/concerns/proposals for a certain topic.
  • Start a discussion on the Delegate list, explaining that this topic will be put to a vote.
    • i.e. "This is serious. If you have something to say, say it now, or it won't go into the proposal."
  • With the help of the community/Delegates, the WRC submits a proposal containing the following (see the first post of issue Standard protocol for important proposed changes. #106):
    • An exact set of proposed changes (i.e. a git diff)
    • A list of pros
    • A list of cons
    • A list of community considerations
  • Hold a vote for a set period of time (1 week?)
    • Each person who has one of the following roles gets one vote: Delegate, Board member, WRC member
    • Each vote against the proposal must include the major "con" that influenced the decision (because proposals take a lot of work, and this allows future proposal to learn why previous ones failed).
    • Everyone's votes (and reasons) are completely public.
  • The Board makes an ultimate decision on whether to accept or reject the proposal, but is expected to follow the majority of votes unless it is close to a tie.

There are some details to be figured out:

  • Can "minor" details be tweaked if they come up after the start of a vote?
  • What is quorum?
  • Do we need timelines (e.g. some number of weeks for feedback before the vote can begin)?
  • What if there are more than 2 reasonable choices rather than a decision about whether to make one specific change?
  • How to hold the vote. I propose the following, because it is practical and doesn't require us to use something new/untested:
    • Create a new subforum on the WCA forum with the following permissions:
      • The WRC can create threads/polls.
      • Every voting member can vote and post in voting threads.
      • Every member of the public can view the entire subforum.
    • Each poll includes a simple accept/reject/abstain option for the proposal (to avoid biasing the main vote). In addition, I'd like to find a way to force "votes are accompanied with a reason". There are at least a few crude ways to accomplish this, which I don't think we need to discuss right now.
@lgarron
Copy link
Member Author

lgarron commented Apr 22, 2014

As a test, I think the first votes should be on the following topics:

Eventually:

  • Puzzle changes (stickerless/pillowed/"anything goes"). This would take a while to prepare.

@lgarron lgarron mentioned this issue Apr 22, 2014
8 tasks
@lgarron lgarron modified the milestone: mid-2014 Apr 22, 2014
@lgarron
Copy link
Member Author

lgarron commented Apr 22, 2014

Some thoughts on who should vote:

Why Delegates

  • Delegates have the most experience with the Regulations and how to enforce/interpret them.
  • Delegates are already a specially vetted set of people involved with the WCA.
  • Delegates are privy to more detailed discussions on the Delegates list, often related to specific incidents that can addressed with Regulation changes (I don't like this, but I'm not sure we can change that very soon).
  • Delegates are an international set of community members, and can connect us to parts of the world who don't participate on English-speaking forums.

Why Not Delegates?

  • Some Delegates have limited experience.
  • If discussions are not fully open for public participation, this limits the ability of experienced competitors from "cubing-dense" regions to contribute.
  • Delegates may have biases that don't align with organizers, competitors/the community, and the general public audience of the sport.
  • If Delegates become a body with special privileges like legislation (e.g. more of a "senate"), then the incentives for becoming a Delegate may change.
    • This is unlikely to be a concern in mid-2014, but we should be careful about going down that path.

Board and WRC Members

Most Board/WRC members are also Delegates, so allowing them to vote wouldn't change much.
My main reason for stating that all Board/WRC members should vote is so that their stance is revealed publicly, in the same way as every voting Delegate.

If votes are secret, I don't think it's important for them to be allowed to vote, but I would like as much transparency about voting as possible.

@lgarron
Copy link
Member Author

lgarron commented Apr 24, 2014

I originally suggested Delegates because this is a natural extension of the current de facto system, and is fairly straightforward.
However, the most common concern about the idea of voting on WCA proposals is limiting it to Delegate voting. Erik has been vocal about his concerns in this thread. I don't agree with all his concerns, but I agree that it would be nice to have a way to give a voting voice to experienced members of the community.

I was discussing this with @KitClement, and he gave the most reasonable suggestion I've heard so far:

  • Allow one vote for each competitor who:
    • out of all competitors in their region ranked by number of competitions attended, is in the top X% (e.g. region=continent, X=5)
    • has been to at least one competition in the past year

This is definitely not perfect, but I won't discuss merits/concerns in this comment.

@lgarron lgarron changed the title Delegate Voting Delegate/Community Voting Apr 24, 2014
@lgarron lgarron removed this from the 2015 milestone Jul 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants