• 2017 FTSC Election, call for nominations

    From Michiel van der Vlist@2:280/5555 to All on Saturday, October 21, 2017 11:57:36
    2017 FTSC election, call for nominations
    ========================================


    An election for FTSC standing members starts on Sunday 22th of
    October 2017 at 20:00 UTC.

    As per FTA-1000.002 the number of FTSC members should be no less than
    7 and no more than 30. Presently there are 12 FTSC members, 7 of them
    have their term expire this year. That leaves room for a maximum of 30-(12-7)=25 members to be (re)elected.


    From FTA-1001.007

    3.2 FTSC Standing Members
    -------------------------

    FTSC members are appointed for a two year renewable term. [50 % of
    appointments on initial formation of the FTSC shall be for a 3 year
    renewable term, to ensure continuity of the Committee on expiry of
    the terms.]

    To be selected as a FTSC member, an individual must be a Fidonet
    node, and should be actively involved in Fidonet. Examples include
    having put out a Fidonet-related product or having updated a product
    in the preceding two years, or having experience as a Coordinator,
    Echomail Coordinator or mail or file Hub.

    Standing members may be nominated Fidonet-wide by all of the
    following methods:

    1. Any RC.
    2. A nominating committee established for the purpose by the FTSC.
    3. A nominating committee established for the purpose by the ZCC.

    A nominating committee may not consist of any current member or
    officer of the FTSC.

    Standing members are appointed on the basis of a vote by all RCs
    who are nodelisted as holding those positions at the time the
    nominations are published. A successful candidate must receive
    approval by a majority of votes.

    Publication of the nomination and the voting procedure, and posting
    of RC votes, shall take place openly in the FTSC_PUBLIC echo, and
    voting shall close three weeks after publication of the vote.


    The status of RC's will be determined by nodelist.293 of this year by
    the list as issued by the ZC in the zone where they reside.

    All RCs and members of a nominating committee are hereby
    invited to nominate members. Nominations must be posted in the
    FTSC_PUBLIC echo.

    Nominations start at Sunday, 22 October 2017. 20:00 UTC and end at
    Sunday 5 November 2017, 20:00 UTC.

    Nominators are advised to sound out prospective nominees before
    filing a nomination. There is little or no point in nominating
    someone that has not shown interest and expressed willingness to
    accept.

    Note to candidates: The main task of the FTSC is to document current
    practise. Contrary to what the name suggests, the FTSC does not create standards out of the blue. Current Fidonet practise evolves and when
    it has stabilized, it may become a standard through FTSC documentation.
    Also, the FTSC is not an enforcement body. Those who wish to join the
    FTSC in order to "engineer Fidonet" may be in for a disappointment.
    Our main job is that of a clerk. We write the technical manual, we do
    not design the machine. To avoid disappointment, sysops interested in
    joining the FTSC are strongly advised to read the following documents:

    http://ftsc.org/docs/fta-1000.002
    http://ftsc.org/docs/fta-1001.007


    Michiel van der Vlist
    FTSC Election Coordinator



    --- Fmail, Binkd, Golded
    * Origin: http://www.vlist.org (2:280/5555)
  • From Bob Seaborn@1:140/12 to Michiel van der Vlist on Sunday, October 22, 2017 16:28:00
    2017 FTSC election, call for nominations
    ========================================


    An election for FTSC standing members starts on Sunday 22th of
    October 2017 at 20:00 UTC.

    As per FTA-1000.002 the number of FTSC members should be no less than
    7 and no more than 30. Presently there are 12 FTSC members, 7 of them
    have their term expire this year. That leaves room for a maximum of 30-(12-7)=25 members to be (re)elected.


    From FTA-1001.007

    3.2 FTSC Standing Members
    -------------------------

    FTSC members are appointed for a two year renewable term. [50 % of
    appointments on initial formation of the FTSC shall be for a 3 year
    renewable term, to ensure continuity of the Committee on expiry of
    the terms.]

    To be selected as a FTSC member, an individual must be a Fidonet
    node, and should be actively involved in Fidonet. Examples include
    having put out a Fidonet-related product or having updated a product
    in the preceding two years, or having experience as a Coordinator,
    Echomail Coordinator or mail or file Hub.

    Standing members may be nominated Fidonet-wide by all of the
    following methods:

    1. Any RC.
    2. A nominating committee established for the purpose by the FTSC.
    3. A nominating committee established for the purpose by the ZCC.

    A nominating committee may not consist of any current member or
    officer of the FTSC.

    Standing members are appointed on the basis of a vote by all RCs
    who are nodelisted as holding those positions at the time the
    nominations are published. A successful candidate must receive
    approval by a majority of votes.

    Publication of the nomination and the voting procedure, and posting
    of RC votes, shall take place openly in the FTSC_PUBLIC echo, and
    voting shall close three weeks after publication of the vote.


    The status of RC's will be determined by nodelist.293 of this year by
    the list as issued by the ZC in the zone where they reside.

    All RCs and members of a nominating committee are hereby
    invited to nominate members. Nominations must be posted in the
    FTSC_PUBLIC echo.

    Nominations start at Sunday, 22 October 2017. 20:00 UTC and end at
    Sunday 5 November 2017, 20:00 UTC.


    It is now 22:10 UTC, and RC17, 1:17/0, hereby nominates Dallas Hinton, Carol Shenkenburger to stand for election as as members of the FTSC.

    --- GEcho/32 & IM 2.50
    * Origin: RC17 (email to rc17@fidonet.ca) (1:140/12)
  • From Ward Dossche@2:292/854 to Michiel van der Vlist on Monday, October 23, 2017 00:53:19
    Michiel,

    Presently there are 12 FTSC members, 7 of them
    have their term expire this year.

    And who might these be?

    \%/@rd

    --- D'Bridge 3.99
    * Origin: I will always keep a PC running WinXP (2:292/854)
  • From Bob Seaborn@1:140/12 to Michiel van der Vlist on Sunday, October 22, 2017 19:45:00
    2017 FTSC election, call for nominations
    ========================================


    An election for FTSC standing members starts on Sunday 22th of
    October 2017 at 20:00 UTC.

    As per FTA-1000.002 the number of FTSC members should be no less than
    7 and no more than 30. Presently there are 12 FTSC members, 7 of them
    have their term expire this year. That leaves room for a maximum of
    30-(12-7)=25 members to be (re)elected.


    From FTA-1001.007

    3.2 FTSC Standing Members
    -------------------------

    FTSC members are appointed for a two year renewable term. [50 % of
    appointments on initial formation of the FTSC shall be for a 3 year
    renewable term, to ensure continuity of the Committee on expiry of
    the terms.]

    To be selected as a FTSC member, an individual must be a Fidonet
    node, and should be actively involved in Fidonet. Examples include
    having put out a Fidonet-related product or having updated a product
    in the preceding two years, or having experience as a Coordinator,
    Echomail Coordinator or mail or file Hub.

    Standing members may be nominated Fidonet-wide by all of the
    following methods:

    1. Any RC.
    2. A nominating committee established for the purpose by the FTSC.
    3. A nominating committee established for the purpose by the ZCC.

    A nominating committee may not consist of any current member or
    officer of the FTSC.

    Standing members are appointed on the basis of a vote by all RCs
    who are nodelisted as holding those positions at the time the
    nominations are published. A successful candidate must receive
    approval by a majority of votes.

    Publication of the nomination and the voting procedure, and posting
    of RC votes, shall take place openly in the FTSC_PUBLIC echo, and
    voting shall close three weeks after publication of the vote.


    The status of RC's will be determined by nodelist.293 of this year by
    the list as issued by the ZC in the zone where they reside.

    All RCs and members of a nominating committee are hereby
    invited to nominate members. Nominations must be posted in the
    FTSC_PUBLIC echo.

    Nominations start at Sunday, 22 October 2017. 20:00 UTC and end at
    Sunday 5 November 2017, 20:00 UTC.


    It is now 22:10 UTC, and RC17, 1:17/0, hereby nominates Dallas Hinton,
    Carol Shenkenburger to stand for election as as members of the FTSC.


    Further to the above, I also have the honor of nominating RJ Clay, and Mark Hoffmn.


    RC17

    --- GEcho/32 & IM 2.50
    * Origin: RC17 (email to rc17@fidonet.ca) (1:140/12)
  • From Alexey Vissarionov@2:5020/545 to Ward Dossche on Monday, October 23, 2017 11:07:00
    Good ${greeting_time}, Ward!

    23 Oct 2017 00:53:18, you wrote to Michiel van der Vlist:

    Presently there are 12 FTSC members, 7 of them
    have their term expire this year.
    And who might these be?

    http://ftsc.org/docs/fta-1003.022 may give you some hints...


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

    ... that's why I really dislike fools.
    --- /bin/vi
    * Origin: http://openwall.com/Owl (2:5020/545)
  • From Alexey Vissarionov@2:5020/545 to Bob Seaborn on Monday, October 23, 2017 11:08:00
    Good ${greeting_time}, Bob!

    22 Oct 2017 16:28:00, you wrote to Michiel van der Vlist:

    RC17, 1:17/0, hereby nominates Dallas Hinton, Carol Shenkenburger
    to stand for election as as members of the FTSC.

    Carol's term expires on 19 Dec 2018.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

    ... that's why I really dislike fools.
    --- /bin/vi
    * Origin: http://openwall.com/Owl (2:5020/545)
  • From Ward Dossche@2:292/854 to Alexey Vissarionov on Monday, October 23, 2017 11:17:15

    Alex,

    And who might these be?

    http://ftsc.org/docs/fta-1003.022 may give you some hints...

    Great customer service ... 8-(

    \%/@rd

    --- D'Bridge 3.99
    * Origin: I will always keep a PC running WinXP (2:292/854)
  • From Ward Dossche@2:292/854 to Alexey Vissarionov on Monday, October 23, 2017 11:19:44

    Alex,

    RC17, 1:17/0, hereby nominates Dallas Hinton, Carol Shenkenburger
    to stand for election as as members of the FTSC.

    Carol's term expires on 19 Dec 2018.

    No, no ... that is Carol Shenkenberger, Bob nominates Carol Shenkenburger.
    " "
    \%/@rd

    --- D'Bridge 3.99
    * Origin: I will always keep a PC running WinXP (2:292/854)
  • From Election Coordinator@2:2/20 to Bob Seaborn on Monday, October 23, 2017 11:38:36
    Hello Bob,

    On Sunday October 22 2017 19:45, you wrote to me:

    It is now 22:10 UTC, and RC17, 1:17/0, hereby nominates Dallas Hinton,

    Ack

    Carol Shenkenburger to stand for election as as members of the FTSC.

    There is no sysop by the name of "Carol Shenkenburger" in nodelist.293. So:

    Nack.

    Perhaps you meant Carol Shenkenberger? In that case I point that that her term does not expire this year. Do you wish to nominate het anyway?

    Further to the above, I also have the honor of nominating RJ Clay,

    Ack.

    and Mark Hoffmn.

    There is no sysop by the name of "Mark Hoffmn" in nodelist.293. So:

    Nack.

    Perhaps you meant Mark Hofmann?



    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:2/20)
  • From mark lewis@1:3634/12.73 to Alexey Vissarionov on Monday, October 23, 2017 10:16:30

    On 2017 Oct 23 11:07:00, you wrote to Ward Dossche:

    Presently there are 12 FTSC members, 7 of them
    have their term expire this year.
    And who might these be?

    http://ftsc.org/docs/fta-1003.022 may give you some hints...

    why not just post the list one time so that everyone knows and doesn't have to go digging trying to find said list? :smh:

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... We need guns, really Big guns !
    ---
    * Origin: (1:3634/12.73)
  • From mark lewis@1:3634/12.73 to Ward Dossche on Monday, October 23, 2017 10:17:32

    On 2017 Oct 23 11:17:14, you wrote to Alexey Vissarionov:

    And who might these be?

    http://ftsc.org/docs/fta-1003.022 may give you some hints...

    Great customer service ... 8-(

    exactly... but be careful! if you say or do something he doesn't like, he'll (threaten to?) DDoS you off the net...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Everyone has a scheme that won't work.
    ---
    * Origin: (1:3634/12.73)
  • From Michiel van der Vlist@2:280/5555 to mark lewis on Monday, October 23, 2017 17:04:27
    Hello mark,

    On Monday October 23 2017 10:16, you wrote to Alexey Vissarionov:

    http://ftsc.org/docs/fta-1003.022 may give you some hints...

    why not just post the list one time so that everyone knows and doesn't have to go digging trying to find said list? :smh:

    This is about he FTSC, not about kindergarten. Those concerned should not have to be spoonfed with information that is publically available. If they can not perform a task as simple as finding the information themselves, then perhaps they should just watch from the sideline.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:280/5555)
  • From Bob Seaborn@1:140/12 to Election Coordinator on Monday, October 23, 2017 10:26:00
    Hello Bob,

    On Sunday October 22 2017 19:45, you wrote to me:

    It is now 22:10 UTC, and RC17, 1:17/0, hereby nominates Dallas Hinton,

    Ack

    Carol Shenkenburger to stand for election as as members of the FTSC.

    There is no sysop by the name of "Carol Shenkenburger" in nodelist.293.
    So:

    Nack.

    Perhaps you meant Carol Shenkenberger? In that case I point that that
    her term does not expire this year. Do you wish to nominate het anyway?

    yes, but never mind



    Further to the above, I also have the honor of nominating RJ Clay,

    Ack.

    and Mark Hoffmn.

    There is no sysop by the name of "Mark Hoffmn" in nodelist.293. So:

    Nack.

    Perhaps you meant Mark Hofmann?


    yes, please consider that I've nominated him





    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:2/20)

    --- GEcho/32 & IM 2.50
    * Origin: RC17 (email to rc17@fidonet.ca) (1:140/12)
  • From Election Coordinator@2:2/20 to Bob Seaborn on Monday, October 23, 2017 19:58:24
    Hello Bob,

    On Monday October 23 2017 10:26, you wrote to me:

    Perhaps you meant Mark Hofmann?


    yes, please consider that I've nominated him

    Ack


    Cheers, Election

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:2/20)
  • From Ward Dossche@2:292/854 to mark lewis on Monday, October 23, 2017 20:19:02
    mark,

    Great customer service ... 8-(

    exactly... but be careful! if you say or do something he doesn't like, he'll (threaten to?) DDoS you off the net...

    I have been bullied one time too many out of a valid FTSC-discussion in the closed FTSC-echo where the moderator happens to be the moderator of this echo too, the RC of my former region, the FTSC-chairman and the Election Coordinator.

    It's very difficult to state it more plain ...

    \%/@rd

    --- D'Bridge 3.99
    * Origin: I will always keep a PC running WinXP (2:292/854)
  • From mark lewis@1:3634/12.73 to Michiel van der Vlist on Monday, October 23, 2017 22:14:38

    On 2017 Oct 23 17:04:26, you wrote to me:

    http://ftsc.org/docs/fta-1003.022 may give you some hints...

    why not just post the list one time so that everyone knows and doesn't
    have to go digging trying to find said list? :smh:

    This is about he FTSC,

    exactly...

    not about kindergarten.

    point made...

    Those concerned should not have to be spoonfed with information that
    is publically available.

    you assume that everyone interested knows what to google for?? if it even shows
    up on google??

    If they can not perform a task as simple as finding the information themselves, then perhaps they should just watch from the sideline.

    yet, ""you"" are asking the voters to do that, eh?? interesting...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Confucius Say: To make egg roll, push it.
    ---
    * Origin: (1:3634/12.73)
  • From Mark Hofmann@1:261/1304 to Bob Seaborn on Wednesday, October 25, 2017 15:29:19

    There is no sysop by the name of "Mark Hoffmn" in nodelist.293. So:

    Nack.

    Perhaps you meant Mark Hofmann?


    yes, please consider that I've nominated him

    ACK.

    - Mark

    --- WWIVToss v.1.52
    * Origin: http://www.weather-station.org * Bel Air, MD -USA (1:261/1304.0)
  • From Carol Shenkenberger@1:275/100 to mark lewis on Sunday, October 29, 2017 12:16:47
    Re: 2017 FTSC Election, call for nominations
    By: mark lewis to Alexey Vissarionov on Mon Oct 23 2017 10:16 am

    http://ftsc.org/docs/fta-1003.022 may give you some hints...
    why not just post the list one time so that everyone knows and doesn't have to go digging trying to find said list? :smh:

    I think this is the first time it wasn't posted right with the election note.

    Interestingly, XP didnt resolve the list. WIN7 did with no problem. You and i aren't this year.

    I figure someone posted by now but if not, I will in a bit.

    Carol
    --- SBBSecho 2.12-Win32
    * Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)
  • From Carol Shenkenberger@1:275/100 to Michiel van der Vlist on Sunday, October 29, 2017 12:26:17
    Re: 2017 FTSC Election, call for nominations
    By: Michiel van der Vlist to mark lewis on Mon Oct 23 2017 05:04 pm

    http://ftsc.org/docs/fta-1003.022 may give you some hints...

    why not just post the list one time so that everyone knows and
    doesn't have to go digging trying to find said list? :smh:

    This is about he FTSC, not about kindergarten. Those concerned should not have to be spoonfed with information that is publically available. If they can not perform a task as simple as finding the information themselves, then perhaps they should just watch from the sideline.

    It's also the first time the list was not added with the dates that i have seen.

    I am not sure what is happening elsewhere, but the standard Z1 method is to have nodes vote up to the RC (often by NC collecting a count to the RC for their net).

    It's a more fair vote than just RC's voting on their own which does lead to a dual hat issue these days.

    Carol
    --- SBBSecho 2.12-Win32
    * Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)
  • From Markus Reschke@2:240/1661 to Carol Shenkenberger on Sunday, October 29, 2017 18:01:48
    Hi Carol!

    Oct 29 12:26 2017, Carol Shenkenberger wrote to Michiel van der Vlist:

    I am not sure what is happening elsewhere, but the standard Z1 method
    is to have nodes vote up to the RC (often by NC collecting a count to
    the RC for their net).

    It's a more fair vote than just RC's voting on their own which does
    lead to a dual hat issue these days.

    I don't know if it would be a job for the FTSC, but there is an idea of creating some kind of election / voting standards paper, describing proper election / voting procedures for all the different cases. That could be simply referenced by all other documents. So R24 could say that the RC's votes for the
    FTSC member election will be determined by DOC-0001 paragraph 3.4, for example.
    And 3.4 would define how the process works.

    ciao,
    Markus

    ---
    * Origin: *** theca tabellaria *** (2:240/1661)
  • From Carol Shenkenberger@1:275/100 to Michiel van der Vlist on Sunday, October 29, 2017 14:40:48
    Re: 2017 FTSC Election, call for nominations
    By: Carol Shenkenberger to Michiel van der Vlist on Sun Oct 29 2017 12:26 pm

    For those unsure, here's ypir vote list:

    1. FTSC Administrator
    ---------------------

    Michiel van der Vlist, 2:280/5555. Term ends 12 October 2019

    2. FTSC Standing Members
    ------------------------

    Name Node Term ends
    --------------------------------------------------------
    Nicholas Boel 1:154/10 19 Dec 2018
    Robert "Jame" Clay 1:120/544 9 Dec 2017
    Bj?rn Felten 2:203/2 9 Dec 2017
    Dallas Hinton 1:153/715 9 Dec 2017
    Mark Hofmann 1:261/1304 9 Dec 2017
    Andrew Leary 1:320/119 19 Dec 2018
    mark lewis 1:3634/12 19 Dec 2018
    Richard Menedetter 2:310/31 19 Dec 2018
    Markus Reschke 2:240/1661 9 Dec 2017
    Carol Shenkenberger 1:275/100 19 Dec 2018
    Alexey Vissarionov 2:5020/545 9 Dec 2017
    Michiel van der Vlist 2:280/5555 9 Dec 2017
    --- SBBSecho 2.12-Win32
    * Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)
  • From Carol Shenkenberger@1:275/100 to Markus Reschke on Sunday, October 29, 2017 14:46:39
    Re: 2017 FTSC Election, call for nominations
    By: Markus Reschke to Carol Shenkenberger on Sun Oct 29 2017 06:01 pm

    Hi Carol!

    Oct 29 12:26 2017, Carol Shenkenberger wrote to Michiel van der Vlist:

    I am not sure what is happening elsewhere, but the standard Z1
    method is to have nodes vote up to the RC (often by NC collecting a
    count to the RC for their net).

    It's a more fair vote than just RC's voting on their own which does
    lead to a dual hat issue these days.

    I don't know if it would be a job for the FTSC, but there is an idea of creating some kind of election / voting standards paper, describing proper
    election / voting procedures for all the different cases. That could be simply referenced by all other documents. So R24 could say that the RC's votes for the FTSC member election will be determined by DOC-0001 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?

    Carol
    --- SBBSecho 2.12-Win32
    * Origin: SHENK'S EXPRESS telnet://shenks.synchro.net (1:275/100)
  • From Election Coordinator@2:2/20 to Carol Shenkenberger on Sunday, October 29, 2017 20:21:57
    Hello Carol,

    On Sunday October 29 2017 12:26, you wrote to me:

    This is about he FTSC, not about kindergarten. Those concerned should
    not have to be spoonfed with information that is publically
    available. If they can not perform a task as simple as finding the
    information themselves, then perhaps they should just watch from the
    sideline.

    It's also the first time the list was not added with the dates that i
    have seen.

    Wrong. I have never published that list in here. The reason for not doing that has been published several times in the previous years.

    I am not sure what is happening elsewhere, but the standard Z1 method
    is to have nodes vote up to the RC (often by NC collecting a count to
    the RC for their net).

    RCs have always been encouraged to consult the region before casting their vote.



    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:2/20)
  • From Election Coordinator@2:2/20 to Carol Shenkenberger on Sunday, October 29, 2017 20:27:56
    Hello Carol,

    On Sunday October 29 2017 14:46, you wrote to Markus Reschke:

    I think the first thing would be posting a list of who you are voting
    for is expected.

    There is no such list yet as we are still in the nomination fase. The list of candidates that can be voted on, will be published after the nomination fase is
    completed.


    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.org (2:2/20)