Z1C Election Rules - Revised
From
Andrew Leary@1:320/219 to
All on Tue May 1 16:16:25 2018
Hello everybody!
=== Cut ===
01-May-2018 ZONE 1 COORDINATOR (Z1C) ELECTION RULES
============================================
RULES FOR CONDUCT OF THE Z1C ELECTION, 2018
* Schedule:
May 07 - May 20 Nominations accepted.
Discussion begins.
May 20 - Nominations END at 23:59:59 UTC.
May 21 - Final list of candidates posted in Z1_ELECTION.
Discussion continues.
May 27 - Discussion ends. Candidates stop campaigning.
May 28 - Voting begins.
Jun 10 - Voting ends at 23:59:59 UTC.
Jun 11 - Results posted in Z1_ELECTION.
Jun 11 - Jun 24 Opportunity to yell fowl and fix errors.
Jun 25 - Final results announced.
Jun 25 - Jun 28 Turnover from outgoing ZC to winning candidate.
Jun 29 - New ZC appears in the nodelist and begins work.
* Position to be Elected:
The election is for the position of Zone 1 Coordinator (Z1C). The
responsibilities of the Z1C include but are not limited to:
-- To compile the nodelists from all of the regions in the zone, and create
the master nodelist and difference file.
-- To represent Zone 1 on the Zone Coordinator Council.
-- See Policy 4 for further details.
* Voter Eligibility:
The eligible list is based on the Zone 1 segment of the FidoNet NodeList
published on Friday, May 4, 2018 (Day 124.)
Each sysop has one vote, regardless of how many nodes s/he operates.
Nodes with more than one sysop get only one vote.
Nodes marked 'Down' are not eligible to vote.
* Nominations, Candidates:
Nominations will be placed in the Z1_ELECTION echo conference. To be
a candidate, a FidoNet sysop must be a current member of Zone 1, and be
seconded by another FidoNet sysop. In addition, due to the technical
nature of the position, current or previous *C experience is required.
An individual may not nominate himself or second himself. Nominations,
seconds, and acceptances MUST be confirmed via netmail to the Enforcer at
1:128/2 BEFORE the close of the nomination period.
* Election:
At the close of balloting, the Enforcer will send all ballots to the
Verifier to verify the results, and a summary of the results will be
posted in Z1_ELECTION.
The Enforcer will not disclose any node's vote to any other node, except
for the Verifier.
In the event only there is only one candidate properly nominated
s/he will become the new Zone 1 Coordinator, effective May 25, 2018.
* Comments by the Candidates:
Comments by Z1C candidates are to be posted in Z1_ELECTION no later than
23:59:59 UTC on May 27. After that, they must STOP campaigning in
Z1_ELECTION until the voting period ends. All discussion will take place
in Z1_ELECTION.
* Who Wins?
The winner will be determined as the candidate receiving more than half
of the number of valid votes, otherwise known as an absolute majority.
In the event no candidate receives an absolute majority, the Enforcer
will schedule a run-off election between the two top vote getters.
* Challenges, Election Results:
The results may be challenged by sending netmail to the Enforcer at
1:128/2. It must be received before 23:59:59 UTC on Jun 24, 2018. No
complaints or contested votes will be considered if received late.
The Enforcer has the final say in all matters relating to the election,
including the eligibility of candidates and/or voters.
If the election is declared invalid, a new election shall begin as
soon as possible, within 14 days of the previous election being declared
invalid.
* How to SEND your vote:
ALL BALLOTS MUST BE NETMAIL ADDRESSED TO 'Enforcer' at 1:128/2.
You can route your ballot if you choose, but if you value your privacy
and want to ensure arrival, you should send it directly to 1:128/2.
Return receipts will be sent via direct or routed netmail. Those return
receipts will contain NO information except that a vote was received from
your node.
* HOW TO VOTE:
- Write a a NETMail message addressed to 'Enforcer' at 1:128/2.
- Subject line doesn't matter.
- Write the name of the valid candidate you want to vote for in the body
of the message. A final list of valid candidates will be posted on
May 21 in Z1_ELECTION. Write-in candidates are not allowed.
- Make up a password of ten (10) characters or less, and put that in the
body of the message too.
NOTE: Your password will be displayed (case insensitive) with your
choice in Z1_ELECTION so you can know that your ballot was counted
correctly.
In addition, votes received that do not meet ALL of the above conditions
will not be counted until corrected by the voter.
* SAMPLE BALLOT:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
| Date: May 28 2018 11:09 |
| From: Joe Sysop, 1:320/999 |
| To: Enforcer, 1:128/2 |
| Subj: My vote |
| -------------------------------------------- |
| <Candidate's Name> |
| |
| My password is Hoochie |
| |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
When your vote is received, it will NOT be machine-processed. Don't poll
to pick up a receipt. The Enforcer will send a direct or routed netmail
receipt to you confirming that he received a ballot but there will be no
other information in the receipt.
To ensure that your vote was counted properly, you may check the periodic
posting of passwords/candidates in Z1_ELECTION.
Thank you to Phil Kimble (1:128/2) for agreeing to serve as the Enforcer,
and Fred Riccio (1:132/174) for agreeing to serve as the Verifier.
* That's it. Enjoy the election!
=== Cut ===
Revised to explicitly state that candidates must be members of Zone 1, clarify the question of what happens if no candidate receives an absolute majority of the votes cast, and give the Enforcer final say on any questions of candidate and/or voter eligibility.
All, please review and get back to me ASAP.
Andrew
--- GoldED+/LNX 1.1.5-b20170303
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)