Difference between revisions of "Ladle/Guidelines/Voting"
(→Past Votes: corrected Ladle 34 voting thread link) |
|||
Line 112: | Line 112: | ||
| '''yes''' (11), no (1) | | '''yes''' (11), no (1) | ||
|- | |- | ||
− | | rowspan="5" | [http://forums3.armagetronad.net/viewtopic.php?p= | + | | rowspan="5" | [http://forums3.armagetronad.net/viewtopic.php?p=224244#p224244 L-34] |
|- | |- | ||
| team size | | team size |
Revision as of 15:26, 14 July 2010
Ladle Voting
The decision-making process for Ladle-related issues was sketchy at best before the voting system was in place. Previously, community members might make a forum poll or some complaint thread, and people would argue a point. Very little was ever accomplished and every change was a challenge to authority of sorts.
At one point, people began to question the nature of the Ladle rules themselves and the authority for which they had been created. [1] It was clear something needed to be done. By February 2009, just about everything related to the Ladle was in question again. A discussion of rules broke out, but this time it was about not just what rules we should have, but how to decide on them as a community.[2] Lackadaisical pointed out a vote from Ladle-16 where the teams successfully decided on settings.[3] Eventually it was decided to try out a quarterly voting schedule using the previous method from Ladle-16. The first quarterly vote coincided with Ladle-21 and has been used rather consistently, with great success. [4]
The process is simple. Every third Ladle, a discussion thread is created to talk about Ladle issues. Ideas are flushed out, argued, and generally put through the ringer. One week before the Ladle sign-ups close, a voting thread is created. The thread contains the choices for the teams to vote on. Only teams signed up can vote, one vote per team (if you have a large clan with 2 teams, that means 2 votes). Voting closes when sign-ups close.
Past Votes
Ladle | Issue | Results, Choices |
---|---|---|
L-16 | score_hole | 0 points (4), 1 point (2) |
2v2 fortress conquering | unconquerable (5), conquerable (1) | |
scoring distribution | 6/4 (4), 10/0 (2) | |
winzone / deathzone | no (6), yes, expanding, when? (0) | |
L-21 | ||
team size | 6v6 (4), 7v7 (0), 8v8 (2) | |
score_hole | 0 points (6), 1 point (0) | |
scoring distribution | 6/4 (6), 10/0 (0) | |
brackets / team placement | random (6), seeded (0) | |
servers | balance of EU/US (5), random (1) | |
rotate finals between US/EU servers | yes (4), no (2) | |
coordinated server names | yes (6), no (0) | |
players use name on Challenge Board | yes (5), no (1) | |
L-24 | ||
team size | 6v6 (6), 7v7 (2), 8v8 (0) | |
score_hole | 0 points (7), 1 point (0) | |
2v2 fortress conquering | unconquerable (6), conquerable (2) | |
scoring distribution | 6/4 (8), 10/0 (0) | |
brackets / team placement | random (5), seeded (3) | |
finals are best of 3 | yes (5), no (3) | |
Ladle start time | 1 hour early (4), 1.5 (1), same (2) | |
Ladle should be on which day | Sunday (5), Saturday (2) | |
Ladle should be 2 days | no (7), Sat/Sun (0), consecutive Sundays (1) | |
L-27 | ||
moderators | global (4), team leaders (1), both (3) | |
Ladle start time | 18:45 GMT (6), 17:45 GMT (2) | |
double elimination | none (6), light (2), full (0) | |
L-29 | ||
adjust Ladle date for New Years/January | yes (7), no (2) | |
L-30 | ||
Ladle follows daylight savings time | yes (12), no (0) | |
adjust Ladle date for New Years/January | yes (12), no (0) | |
Challenge Board cutoff-time/day | Thursday (6), Friday (5), Saturday (1) | |
elect global moderators | yes (11), no (1) | |
L-34 | ||
team size | 6v6 (9), 7v7 (2), 8v8 (0) | |
hole size (explosion_radius) | 0.75m (7), 2 (3), 0 (1) |