= Сообщение: 2514 из 7127 ====================================== FTSC_PUBLIC = От : Carol Shenkenberger 1:275/100 29 Oct 17 14:46:39 Кому : Markus Reschke 29 Oct 17 14:46:39 Тема : 2017 FTSC Election, call for nominations FGHI : area://FTSC_PUBLIC?msgid=5248.ftsc_pub@1:275/100+1e5b6c8f На : area://FTSC_PUBLIC?msgid=2:240/1661+59ee62a0 = Кодировка сообщения определена как: ASCII ================================== Ответ: area://FTSC_PUBLIC?msgid=2:2/20+59f62c98 ============================================================================== Re: 2017 FTSC Election, call for nominations By: Markus Reschke to Carol Shenkenberger on Sun Oct 29 2017 06:01 pm
MR> Hi Carol!
MR> Oct 29 12:26 2017, Carol Shenkenberger wrote to Michiel van der Vlist:
CS>> I am not sure what is happening elsewhere, but the standard Z1 CS>> method is to have nodes vote up to the RC (often by NC collecting a CS>> count to the RC for their net).
CS>> It's a more fair vote than just RC's voting on their own which does CS>> lead to a dual hat issue these days.
MR> I don't know if it would be a job for the FTSC, but there is an idea of MR> creating some kind of election / voting standards paper, describing proper MR> election / voting procedures for all the different cases. That could be MR> simply referenced by all other documents. So R24 could say that the RC's MR> votes for the FTSC member election will be determined by DOC-0001 MR> paragraph 3.4, for example. And 3.4 would define how the process works.
I could work with that! A general guideline.
I think the first thing would be posting a list of who you are voting for is expected. This thread has been 5 days long and i finally posted 'whos up for revote'. Really?
