= Сообщение: 6337 из 7128 ====================================== FTSC_PUBLIC = От : Shaun Buzza 1:229/110 12 Mar 22 12:47:29 Кому : Dan Clough 12 Mar 22 12:47:29 Тема : Re: 2022 FTSC Standing Member Election - Votes Received FGHI : area://FTSC_PUBLIC?msgid=1:229/110+b18507c8 На : area://FTSC_PUBLIC?msgid=2587.fido_ftscpubl@1:123/115+26921835 = Кодировка сообщения определена как: ASCII ================================== Ответ: area://FTSC_PUBLIC?msgid=4:920/69.1+622cff7c ============================================================================== DC> SB> This has been made clear by more than one person. At this point, DC> SB> though, I am wondering why this is so. I strongly feel that it DC> SB> *should* be a majority decision due to the nature of the election DC> SB> in question. This is simply personal opinion. DC> DC> If you disregard abstentions, it is a majority decision. More yes's DC> than no's means you get in. I think the voter should have to pick one DC> or the other, and not be allowed to abstain from any candidate(s).
Effectively, that's the current vote. The voter is *not* allowed to abstain, if any abstention is not counted toward the total.
DC> I also wonder how it was decided that only RC's can vote for these DC> candidates. Why not NC's also. Why not the peasant-class of DC> nodelisted sysops? I saw somewhere in this conversation recently (I DC> think) that it was deemed that only RC's would have the requisite DC> intelligence/knowledge to know if a particular candidate was qualified DC> for such a job. I disagree with that assumption very strongly.
I, too, remember someone saying that recently. Personally, I cannot disagree with that assumption, as I fit the description a little too well. However, in theory, the RC votes are supposed to be an aggregate of all the votes in the controller's region, in a similar fashion to how a House Representative is supposed to (but doesn't) vote.
DC> Oh well. I shall go back to my peasantly duties now.
