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.
Presently there are 12 FTSC members, 7 of them
have their term expire this year.
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.
Presently there are 12 FTSC members, 7 of themAnd who might these be?
have their term expire this year.
RC17, 1:17/0, hereby nominates Dallas Hinton, Carol Shenkenburger
to stand for election as as members of the FTSC.
And who might these be?
http://ftsc.org/docs/fta-1003.022 may give you some hints...
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.
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.
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...
And who might these be?
http://ftsc.org/docs/fta-1003.022 may give you some hints...
Great customer service ... 8-(
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:
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)
Perhaps you meant Mark Hofmann?
yes, please consider that I've nominated him
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...
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.
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
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:
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.
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.
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.
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).
I think the first thing would be posting a list of who you are voting
for is expected.
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,050 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 73:58:07 |
| Calls: | 236,056 |
| Calls today: | 4 |
| Files: | 60,364 |
| D/L today: |
65 files (60,518K bytes) |
| Messages: | 289,785 |