Subj : FidoNews 33:24 [02/07]: General Articles To : All From : FidoNews Robot Date : Mon Jun 13 2016 00:08:34 ================================================================= GENERAL ARTICLES ================================================================= FN_SYSOP Moderator Election, call for Candidates Candidates for moderator of FN_SYSOP are invited to present themselves between Sunday 12 June 2016 00:00 UTC and Saturday 25 June 2016, 23:59 UTC. Candidates must be listed as a sysop in nodelist.162 of Friday 10th of June as issued by, or on behalf of, their ZC. Candidates must present themselves by posting a messages in the echo addressed to "Election Coordinator" with subject "Candidate". The message must arrive at the system of the election coordinator before the deadline of Saturday 25 June 2016 23:59 UTC. The election coordinator will acknowledge the candidacy with a message in the echo. Candidates are encouraged to post an "election platform", stating who they are, what rules they propose and why they think they will be up to the job. Michiel van der Vlist, 2:280/5555 Election Coordinator ----------------------------------------------------------------- FN_SYOP Moderator Election All times in UTC. The year is 2016. The moderator election for FN_SYSOP starts Sunday 12th of June. 1) Time frame 1.1) Sunday 12 June, 00:00 - Saturday 25 June 23:59 Candidates present themselves. Debating with candidates. 1.2) If there is only one candidate: goto 1.10 1.3) Sunday 26 June 00:00 - Saturday 9 July 23:59 Submission of votes 1.4) Sunday 10 July 00:00 - Saturday 16 July 23:59. Opportunity to file protests. 1.5) If a protest is filed, the election will be discontinued until the issue is resolved. It will then resume at point 1.6, if needed with an updated time table. 1.6) If there is a candidate that has an absolute majority of the votes (i.e more than half of the total number of vaild votes cast), that candidate will be the winner and the election ends. 1.7) If there is no candidate with an absolute majority of votes, a follow up election will be held between the candidate(s) that ha(s|ve) the most vote(s) and the candidate(s) that ha(s|ve) the second most votes. 1.8) Sunday 17 July 00:00 - Saturday 30 July 23:59 Submission of votes for the follow up election. Discussion with candidates. 1.9) Sunday 31 July 00:00 - Saturday 6 August 23:59. Opportunity to file protests. The winner of the follow up election will be the candidate with the highest number of votes. In case of a tie the winner will be eldest of the candidates that collected the most votes. If the remaining candidates can not agree among themselves who is the oldest, the election coordinator will decide who is the oldest. The election coordinator may require candidates to submit some kind of proof of age. - end of election - 1.10 Sunday 26 June 00:00 - Saturday 2 July 23:59 Opportunity to file protest. 1.11) If a protest is filed, the election will be discontinued until the issue is resolved. If there is still one candidate left, the election is terminated and the one candidate is the winner. If there is more than one candidate after all, the election will resume at 1.3 with an adapted time table. - end of election - 2) Who may be a candidate? 2.1) Candidates must be listed as a sysop in Nodelist.162 of Friday 10 June as issued by, or on behalf of, the ZC of the zone he/she resides. 2.2) Candidates must present themselves by placing a messages in the echo addressed to "Election Coordinator" with subject "Candidate". The message must arrive at the system of the election coordinator before the deadline of Saturday 25 June 23;59. Candidates are encouraged to post an "election platform", stating who they are and why they think they will be the best for the job. 2.3) The election coordinator will acknowledge the candidacy with a message in the echo. 2.4) To avoid confusion please use names as written in the nodelist. 2.5) Any participant may and is encouraged to challenge the candidates and enter into debate. 3) Who may vote and how to vote? 3.1) Sysops that are listed with a node that is not flagged as Down, Hold or Pvt in nodelist.162 as published by, or on behalf of, the ZC of the zone in which they reside may cast one vote. Unfortunately some NCs have been playing games with the nodelist thereby creating the suspicion that the nodelist contains nodes that only exist in the imagination of theNC. Since there is no independent objective way to verify if a Pvt or Hld node actually exists, sysops of Pvt or Hld nodes must unfortunately be excluded from voting. This includes nodes that are listed without the Pvt keyword, but that list no contact information for a mailer to connect. 3.2) Voting is confidential. A vote is cast by sending a netmail to "Election Coordinator" at 2:280/5555. The body of the netmail must contain the name of the candidate of choice and a password or pass frase. Please use the spelling as listed in the nodelist. When possible do not use routing, use direct mail when possible. Make sure the mail arrives on the election coordinator's system before the deadline. The time stamp of the election coordinator's tosser will be the deciding factor. Voters may send a copy of the vote to the verifying officer. This is a recomendation, not a requirement. At the time of publishing this announcement, the position of Verifying officer is still vacant. Candidates for the position are invited to contact the election coordinator. 3.3) The Election Coordinator will acknowlegde reception of the vote by netmail to the voter. 3.4) A vote cast is a vote cast. No second thoughts. 3.5) After the voting is closed, the election coordinator will publish a list of the passwords that were received for each candidate. The names of the voters will remain confidential. The verifying officer will confirm the results. Or publish a correction when applicable. Happy election. Michiel van der Vlist, 2:280/5555 Election Coordinator. ----------------------------------------------------------------- --- Azure/NewsPrep 3.0 * Origin: Home of the Fidonews (2:2/2.0) .