* Originally in Z1C
* Crossposted in Z1_ELECTION

Hello everybody!

=== Cut ===
02-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 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 ===

The RCs have made a few minor changes to clarify things and ensure that the election runs smoothly. As of now, the election is in the hands of the Enforcer, Phil Kimble of 1:128/2. Please contact him with any questions.

Regards,

Andrew

--- GoldED+/LNX 1.1.5-b20170303
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Just a reminder that under Voter Elgibility, each sysop only has 1 vote.

RULES FOR CONDUCT OF THE Z1C ELECTION, 2018
* 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.

So while this isnt mentioned under the Nominations paragrah, I am going to apply as if. Unless directed otherwise.

Currently we may have some confusion with a nomination where the person nomiated 2 different people on 2 seperate netmails. I am discounting the 2nd nomiation unless the group wants to allow it. Its still early inthe process...

Phil

--- Msged/LNX 6.1.2
* Origin: Bayhaus.net - Colorado Springs - Serving the FrontRange (1:128/2)

Hey Phil!

Currently we may have some confusion with a nomination where the
person nomiated 2 different people on 2 seperate netmails. I am discounting the 2nd nomiation unless the group wants to allow it.

Which nomination is in question? If it helps any I and willing to take up the slack and use my one nomination to compensate. Also, while I have your attention, is a nodelisted zone 1 sysop allowed a nomination as well as a second as long as they are two different proposed candidates?

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.4.19(1)-release (x86_64-silvermont-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Hi Phil,

Just a reminder that under Voter Elgibility, each sysop only has 1 vote.

True.

RULES FOR CONDUCT OF THE Z1C ELECTION, 2018
* Voter Eligibility:

[...]

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

[...]

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.

So while this isnt mentioned under the Nominations paragrah, I am going to apply as if. Unless directed otherwise.

I agree here - hopefully others will speak up as to whether they also feel that
each sysop may nominate, second, just one candidate. I am not involved in the voting procedure except as a normal node <g>.. Andrew mentioned we should pose any questions to you.

Currently we may have some confusion with a nomination where the person nomiated 2 different people on 2 seperate netmails. I am discounting the 2nd
nomiation unless the group wants to allow it. Its still early inthe process...

Can you show a list of who you currenty show as nominee, seconded, accepted, nominated by?

Right now here is what I show, please confirm :)


Nominee Node# Seconded Accepted Nominated by:
============= ===== ======== ======== ============
Dallas Hinton 1:153/7715 Yes Yes Janis Kracht
Nick Andre 1:229/426 Yes Yes Carol Shenkenberger
Mark Lewis 1:3634/12 Yes ? Carol Shenkenberger ==============================================================
| |
Mark still Carol has
has to accept nominated two
I think? just candidates I
a note :) believe.


Personally, I don't think it's a bad thing <tm> to nominate more than one candidate, but we have to decide exactly what is allowed and what is not IMO.

Thanks for everything Phil :)

Take care,
Janis

--- BBBS/Li6 v4.10 Toy-3
* Origin: Prism bbs (1:261/38)

Hi Maurice,

Currently we may have some confusion with a nomination where the
person nomiated 2 different people on 2 seperate netmails. I am
discounting the 2nd nomiation unless the group wants to allow it.

Which nomination is in question? If it helps any I and willing to
take up the slack and use my one nomination to compensate. Also,
while I have your attention, is a nodelisted zone 1 sysop allowed a nomination as well as a second as long as they are two different
proposed candidates?

This is a question that is under review. Please hold the nomination as we still
have plenty of time remaining.

More to follow...

Life is good,
Maurice

... Don't cry for me I have vi.
-+- GNU bash, version 4.4.19(1)-release (x86_64-silvermont-linux-gnu)
+ Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Phil

--- Msged/LNX 6.1.2
* Origin: Bayhaus.net - Colorado Springs - Serving the FrontRange (1:128/2)

Re: IMPORTANT: Z1C Election Rules REVISED
By: Phil Kimble to All on Tue May 08 2018 09:31 pm

So while this isnt mentioned under the Nominations paragrah, I am going
to apply as if. Unless directed otherwise.

Hi Phil, that was me. Normally we've never limited how many nominations a person can make in any elections I've been part of. Yes, one at vote time as normal, but nominations in reasonable limits allowed.

When Janis ran for Z1C, I nominated her and pretty sure the other was Dallas Hinton?

If it's a problem though, could one of the others add another nomination for Nick Andre?

xxcarol
--- SBBSecho 2.12-Win32
* Origin: Shenk's Express, shenks.synchro.net (1:275/100)

A reminder to everyone,

And to MYSELF, included.


To be elgible to particpate in the nomination or election process, a sysop must
be listed in the 4 May 2018 nodelist.

Nominations occur in Z1_Election AND confirmed by netmail to the Enforcer.

Sysops are only allowed 1 vote. Even if they have an entire net with thier name
on it... ONLY 1 VOTE!

No, you can NOT nominate yourself. But you can nominate your bff!!


REHASH OF THE RULES:
* 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.


I think I have this figured out, finally. Hopefully you do too...

Phil

--- Msged/LNX 6.1.2
* Origin: Bayhaus.net - Colorado Springs - Serving the FrontRange (1:128/2)

Hey Phil!

I think I have this figured out, finally. Hopefully you do too

No. You still haven't answered my question about whether or not a sysop retains a second when nominating ... or the other way around for that matter.

Nominations occur in Z1_Election AND confirmed by netmail to the Enforcer.

As the nodelisted sysop of 1:153/7001, I hereby nominate Nick Andre, the nodelisted sysop of 1:229/426. Hopefully I am giving the correct nodenumber as
there are others (administrative) listed under his name.

I already sent netmail to the Enforcer, but will repeat if needed. As of this writing it was not confirmed.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.4.19(1)-release (x86_64-silvermont-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)

Re: IMPORTANT: Z1C Election Rules REVISED
By: Phil Kimble to ALL on Wed May 09 2018 01:13 pm

To be elgible to particpate in the nomination or election process, a sysop must be listed in the 4 May 2018 nodelist.

Nominations occur in Z1_Election AND confirmed by netmail to the Enforcer.

Sysops are only allowed 1 vote. Even if they have an entire net with thier name on it... ONLY 1 VOTE!

One vote I understand, but does that also apply to Nominations/Seconds?

Personaly I don't think we need to limit nominations/seconds but if there is a limit, what is it.

One Nomination / Second per node/sysop?

Ttyl :-),
Al


... Circular Definition: see Definition, Circular
--- SBBSecho 3.04-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 2018 May 02 08:36:04, Andrew Leary wrote to you:

02-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.

so today is the 21st and i'm guessing that phil is waiting until 0:00GMT (another 6 hours and 54 minutes as of this writing) to post the final list so discussion may continue ;)

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.

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... If swimming is so good for you, why are whales so fat ?
---
* Origin: (1:3634/12.73)

Hi Mark,

[...]

May 21 - Final list of candidates posted in
Z1_ELECTION.
Discussion continues.

so today is the 21st and i'm guessing that phil is waiting until 0:00GMT (another 6 hours and 54 minutes as of this writing) to post the final list so discussion may continue ;)

I expect so :)

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.

Take care,
Janis

--- BBBS/Li6 v4.10 Toy-3
* Origin: Prism bbs (1:261/38)

On 2018 May 21 17:58:08, you wrote to me:

May 21 - Final list of candidates posted in
Z1_ELECTION.
Discussion continues.

so today is the 21st and i'm guessing that phil is waiting until 0:00GMT
(another 6 hours and 54 minutes as of this writing) to post the final
list so discussion may continue ;)

I expect so :)

only 30 minutes left... wonder what discussion will flow forth?

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.

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Every engineer carries a screwdriver.... just in case.
---
* Origin: (1:3634/12.73)