Subj : 2022 FTSC Standing Member Election - Eligibility of Tim Schattkowsky
To : Michiel van der Vlist
From : August Abolins
Date : Mon Feb 21 2022 11:22 am
Hello Michiel van der Vlist!
** On Monday 21.02.22 - 12:21, Michiel van der Vlist wrote to Andrew Leary:
MvdV> 1) Changing the rules during the game is alway a no-no, no matter the
MvdV> intentions.
But why can't the rules adjust and accomdate "the times" as
circumstances change? Even the contracts that we sign and UA's
that we agree to have "subject to change without notice".. and
that is also done for valid reasons.
MvdV> 2) The requirement that FTSC members run a fully fledged fidonet node
MvdV> i.e. a node that can make outgoing calls AND accept incoming calls to
MvdV> and from other fidonet nodes is a technical requirement, not a
MvdV> technicality.
Yes.. a fully fledged node is a technical thing, but is that
required for the actual job? Do the rules state that the FTSC
member must have a consistently nodelisted system, or is that
just during the nominations/voting system. The whole thing
seems a bit pedantic or anal.
MvdV> 3) There are good reasons that these technical requirements are laid
MvdV> down in the rule that candidates MUST accept their nomination with a
MvdV> message originating from their listed node which was nodelist before
MvdV> the start of the elections. It serves to check that the candidate
MvdV> actually runs an operational node and it also serves to prevent "ghost
MvdV> nodes" to be created on the fly for the occasion. As is happening
MvdV> now...
Again.. so that is JUSt during the voting period?
MvdV> 4) Ommitting the Pvt keyword for a node that advertises no contact
MvdV> information is in violation of FTS-5000. The FTSC going along with such
MvdV> a violation of their own standards is not a technicallity.
Why can't the node enable full operations during nominations
period and revert back to Pvt when suitable?
