Forum OpenACS Improvement Proposals (TIPs): TIP #22 (Approved): Fall 2003 OCT Election Process

Collapse
1: TIP #22 (Approved): Fall 2003 OCT Election Process
Posted by Joel Aufrecht on 10/02/03 12:23 PM
(Edited 3 Oct 2003 to add Approval Voting Option - OCT voters, please choose Alternative 1 or Alternative 2) (Edited 5 Oct 2003 to make voting one-week and add absentee ballots)
  1. The OpenACS Core Team is responsible for decision-making on the technological direction of OpenACS. The OCT comprises nine people, elected for 1-year terms by the OpenACS community. OCT members have these powers:
    1. A vote on formal decisions, via the TIP process
    2. commit code to the OpenACS CVS Tree
    3. edit the openacs.org forums
    4. administer the openacs.org bug system
    5. modify text content on openacs.org
    6. Grant powers two through four to other people
    and these formal responsibilities:
    1. Subscribe to the TIP forum and participate in TIP voting at least weekly
    2. take turns filling more active roles (such as Bug Czar) as determined by the OCT
    and these informal responsibilities:
    1. Support community participation in OpenACS development
  2. Candidates. All people listed in https://openacs.org/governance/aut03nominees are eligible candidates in this election.
  3. Voters. All people in the current OCT current OCT, CVS committers, and anybody who posted in the forums at least twice between 25 May and 25 Aug 2003 can vote.
  4. Ballots. A ballot consists of an email to electionaut2003@openacs.org. A ballot template, consisting of a list of all candidate names, separated by line breaks, in random order, will be available at https://openacs.org/governance/aut03ballot. A line which does not exactly match one of the original names is null, but does not spoil the ballot. A line which repeats a name on the same ballot is null, but does not spoil the ballot.
    • Alternative 1 (One Vote Per Seat): A voted ballot consists of a list of up to nine candidate names in any order, one name per line, separated by line breaks. A ballot with more than nine names is a spoiled ballot.
    • Alternative 2 (Approval Voting): A voted ballot consists of a list of any number of candidate names, in any order, one name per line, separated by line breaks.
  5. Election. The election will commence at noon Friday 10 Oct 2003 UTC, and end noon Friday 17 Oct 2003 UTC. Ballots (ie, emails) recieved before this period are valid. Ballots received after this period are not considered. Ballots from email addresses not on the voter pool list are void. If more than one ballot is received from a single email, the last one is counted. A list of email addresses which have provided valid ballots will be maintained at https://openacs.org/governance/aut03valid_ballots.
  6. Counting. Each time a candidate's name appears on a ballot, the candidate recieves one vote. The nine candidates with the most votes win. The list of vote totals will be provided at https://openacs.org/governance/aut2003results/ as soon as possible after the voting period concludes. Ballot counting will be performed by one or more persons approved by the current OCT who are not themselves election candidates.
  7. Special terms. The four winning candidates with the least votes are elected to six-month, rather than one-year, terms. This is establish the staggered election of the OCT; in the future, all terms are intended to last for one year.
  8. Up to two winners per organization.. If more than two people from one organization (company, foundation, university) are elected, all votes for all such persons except the two with the most votes within that set are nullified.
Collapse
2: Re: TIP #22 (Proposed): Fall 2003 OCT Election Process (response to 1)
Posted by Peter Marklund on 10/02/03 03:06 PM
Approved
Collapse
3: Re: TIP #22 (Proposed): Fall 2003 OCT Election Process (response to 1)
Posted by Peter Marklund on 10/03/03 03:38 PM
Approved
Collapse
4: Re: TIP #22 (Proposed): Fall 2003 OCT Election Process (response to 1)
Posted by Don Baccus on 10/05/03 03:04 AM
Well, we've just exposed the dangers of such a short voting period without any "absentee" provisions.

I am travelling much of the 10th and 11th and am not certain of internet access until the 13th ... is there any particular reason we can't leave voting open for a week?

I realize we'll never make it possible for everyone to vote who is eligible and may be caught up with travel plans ...

Collapse
5: Re: TIP #22 (Proposed): Fall 2003 OCT Election Process (response to 4)
Posted by Joel Aufrecht on 10/05/03 11:54 AM
I've made voting one week long and added a provision for early ballots.  Would an openacs.org maintainer please make mailto:electionaut2003@openacs.org a valid mail account on the system and have it store mail?  We haven't selected a vote counter yet (volunteers?).
Collapse
6: Re: TIP #22 (Proposed): Fall 2003 OCT Election Process (response to 1)
Posted by David Cotter on 10/07/03 12:38 AM
I'm available to count.
Collapse
7: Re: TIP #22 (Proposed): Fall 2003 OCT Election Process (response to 1)
Posted by Lars Pind on 10/07/03 12:21 PM
Seconded. No opinion on option #1 vs 2.
Collapse
8: Re: TIP #22 (Proposed): Fall 2003 OCT Election Process (response to 1)
Posted by Andrei Popov on 10/08/03 05:57 PM
Option 1 is more disciplined and maybe easier to count, but is also potentioally a bit more prone to errors of having 8 or 10 nominees instead of correct 9.  Therefore 2 might be safer (but more counting work).

On counting -- couldn't this be scripted?

Collapse
9: Re: TIP #22 (Proposed): Fall 2003 OCT Election Process (response to 1)
Posted by Andrei Popov on 10/08/03 05:59 PM
One more: names will be expected to appear as it would be on the referred template, right?  As in Firstname Lastname (not the other way around, no comma, etc.).
Collapse
10: Re: TIP #22 (Proposed): Fall 2003 OCT Election Process (response to 9)
Posted by Joel Aufrecht on 10/08/03 06:06 PM
Names should be an exact copy-paste match from the ballot.  I'll generate two name lists, one with ballot statements, and one with just names and no formatting, to make it easy.
We could do automated counting, and I would hope that whoever does the counting uses a computer, but in order to take humans out of the cycle we would need to have produced and tested an automated counting tool already.