| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Situation on R2:50 |
03 May 06 10:58, Vladimir Donskoy wrote to Roy Witt: VD>>> Are you read Policy :-) ? RW>> Yes, I am. VD> This is a joke :-) . Nope. VD>>> === Begin Windows Clipboard === VD>>> 8.7 Impeachment of a Zone Coordinator VD>>> [...skip...] VD>>> 8.7.2 Procedure as in Policy Referendum VD>>> The provisions of sections 8.2 and 8.3 apply to impeachment VD>>> referenda. RW>> An impeachment referenda only. VD>>> The definition of "majority" in section 8.6 applies. Only VD>>> coordinators in the affected zone vote (even if the zone VD>>> coordinator is also the Internation- al Coordinator). VD>>> === End Windows Clipboard === RW>> In an impeachment referendum and that only. It says nothing about RW>> any other kind of elections, as in a referandum to secede from a RW>> Fidonet Zone. VD> Policy have information about elections only 3 places: VD> 1.2.5 - "Zone Coordinators are selected by the Regional Coordinators VD> in that zone." The word 'selected' means the same as appointed. Not elected. VD> 6.2 - "The Zone Coordinator is selected by an absolute majority vote VD> of the Regional Coordinators within the zone." The word 'selected' means the same as appointed. Not elected. VD> 7.2 - "The International Coordinator is selected (or removed) by an VD> absolute majority vote of the Zone Coordinators." The word 'selected' means the same as appointed. Not elected. VD> Another cases of elections is absent in Policy... That's because there are no *C elections mentioned in policy. Only selections. VD> So - 8.6 is one of the points with text of elections (system of *Cs VD> election). No, there is nothing mentioned about the (s)election of any *C in that section. 8.6 deals with a policy change and only a policy change. VD> Note - all of them are "selected", not "elected"! I am not sure in VD> different this words, and think that "elect" is "select by votes". Selected means that an NC is appointed by their RC, who in turn is appointed by their ZC. And in turn, the RCC selects and appoints the ZC. There are no *C elections mentioned in Fidonet policy. Voting, as in P4, section 8.6 is for policy changes and policy changes only. You may be thinking of 8.2 - 8.3, which is used in the case of an impeachment proceeding, as mentioned in 8.7.2, but it's only a guideline. VD> NB - "government of FIDO" is close system: RCs are appointed by ZC, VD> and they "selected" ZC! And IC is selected from ZCs... And NCs are VD> appointed by RC - so, we have "close circle". Now you've got it right. Make that a 'closed' circle. RW>>>>>> An election as you've described above would be administered RW>>>>>> under a region policy. If R50? doesn't have a region policy, RW>>>>>> there are plenty of examples in Z1 that can be used as a RW>>>>>> reference to make your region policy. Z1's R12, R13 and R18 all RW>>>>>> have a very good example and select their RC in this way by RW>>>>>> votes from every sysop in the region who wishes to participate RW>>>>>> in that election. I have a copy of each just for the asking. VD>>>>> All elections in our region have make to this principle - all VD>>>>> sysops voting. We have not "write" Regional Policy, but we have VD>>>>> it "in the head". RW>>>> Better to have it in writing so that there's no mis-understandings RW>>>> later. VD>>> May be, but now we have not it. RW>> I'll send you one and you can present it, edit it and mull it over RW>> so your region has one. VD> Thank you for your Regional Policy. I wait your ail. You should have it and a few other items by now. Check them out. Only the regional policy is in affect and approved by our ZC. I say approved because the Z1C still appoints the elected RC. If that person is acceptable to the ZC. And, one time, she fired an elected RC and appointed the runner-up in that election, claiming that she hadn't approved of their regional election policy. So, an RC election is not set in stone unless you get your ZC to approve it. The others were proposals that never got implemented, although they should have. And a comment about P4 by the founder of Fidonet, Tom Jennings. Roy --- Twit(t) Filter v2.1 (C) 2000* Origin: Hacienda de Rio de Guadalupe * South * Texas, USA * (1:1/22) SEEN-BY: 633/267 270 5030/786 @PATH: 1/22 379/1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.