The Drupal Association is holding its first round of elections for "at-large" (community-elected) board members under its new governance structure. This proposal was prepared by numerous community participants, including the Election Committee members, at http://groups.drupal.org/node/199178 and related sub-threads.
December 30 - January 14 (2 weeks): Election committee works with community to develop plan for elections.
January 15 - 17 (3 days): Final refinement of plan, get election tools in place.
January 18: Voting proposal submitted to BoD for ratification. Ratified, yeah!
January 18 - January 29: Nomination process (Note: extended by three days.)
January 30 - February 7: Questions, discussion, and debate
February 3 - February 7: Voting
February 8: Election results for at-large members submitted to board for ratification.
Candidates for the community board positions should be self-nominated. This prevents electing candidates who have the support of the community, but who are unable or unwilling to serve. If community members feel a particular member would make a great board member, they should encourage that individual to nominate themselves.
A nomination form will be set up on http://association.drupal.org to capture nominations, containing the following fields:
- Who am I? (biography/background)
- Why I'm running (mission/motivation)
- Why you should vote for me (qualifications)
- "I am willing and able to travel to in-person board meetings [Y/N]"
Other data (Name, Drupal.org username, Location, Company/Organization) will be pulled in from Drupal.org profile data and displayed on the nomination pages once they are public.
Beyond a valid drupal.org account, no additional restrictions shall be placed on nominees, including geographical location, company, and willingness to travel to in-person board meetings. However, these facts should be made clear in the nomination form so that community members can factor these into their voting process, if desired.
At no time will a nominee be required to disclose publicly any financial hardships which might prevent them from attending the in-person board meetings without financial assistance. If elected, the Drupal Association shall cover the travel expenses of members who are unable to find other means of subsidizing their attendance, or find alternate arrangements (e.g. Webex or similar) for folks who can't make it.
Submissions will be opened for public viewing and comment only once the nomination process has closed, to help prevent bias towards people who submit applications earlier. This posting will kick off a process where community members will have a chance to learn more about the nominees.
Individuals can ask questions to/about individual nominees on their nomination pages, and will be additionally encouraged to post on http://groups.drupal.org/drupal-association to ask broader questions/bring up issues to all nominees.
Finally, two meetings shall be set up by the election committee to allow the community and nominees to discuss issues in "real time." The two meetings will be held in opposite timezones, using both the phone and IRC simultaneously, to allow the most people to participate as possible. Meetings will also be recorded and archived for later review by people who couldn't make it.
Voting will be open to all individuals with at least one drupal.org account who have logged in during the past year and whose account was registered before nominations opened (February 8, 2012). While not representative of the entire Drupal community, this represents a significant enough cross-section while providing some ability to prevent voting fraud.
Voting will be done with the "Instant Run-Off Voting" (IRV) alternate voting system, in order to ensure the fairest representation of the community's views as possible. For elections, a form will be provided where voters rank the candidates according to their 1st, 2nd, 3rd... preferences.
Elections will be held on http://association.drupal.org, capturing anonymized voting results (the users who've voted will be logged, but not for whom they voted). A checkbox to certify that a voter has not already voted in an election will be placed on the form as a basic means of recognizing voter fraud concerns.
The only people who will have access to raw voting data are key individuals on the Drupal.org infrastructure team who also have access to all other sensitive Drupal.org data.
The elections committee, plus one community volunteer, will share election results publicly on the morning to the board meeting on February 8th. These results will then be sent to the board for final ratification.