Text 126, 298 rader
Skriven 2002-07-13 16:30:20 av Goran Eriksson (2:201/505.1)
Ärende: Pleas pass on...
========================
* Original message posted in: R20_ADMIN.
* Crossposted in: R20_INFO2, R20_FIDONET.
* Forwarded (from: netmail242) by Goran Eriksson using timEd/2 1.10.y2k+.
* Originally from Bob Short (1:105/38) to Goran Eriksson (2:20/0).
* Original dated: Wed Jul 10, 22:56
* Original to: Marc Blakely (1:17/0)
cc: Brenda Donovan, gary gilmore, Tony Summerfelt, Thom LaCosta
cc: Michael McCabe, Bob Adkins, Jerry Schwartz, Ross Cassell
cc: Steve Quarrella, Torbjorn Mohn, Tommi Koivula, Kaare Olsen
cc: Werner Blatt, David Rance, Sean Rima (TEMP RC), Francois Thunus
cc: Jan Vermeulen, Johan Zwiekhorst, Ruedi Kneubuehler, Michael Herzog
cc: Eric Van Hyfte, Marcello Ardini, Angel Ripoll, Pedro Lima, Erno Petro
cc: Gregor Jeromen, Wadim A. Sigalov, Jim Andritsakos, Jakub Vanek
cc: Temporary RC, Pavel Gulchouck, Svajunas Laukineitis, Wojciech Scigala
cc: Hanno Liiva, Yuri Safronov, Gatis Berzins, Vladimir Hrusca
cc: Khaled Al-Bassam, Johan Zwiekhorst, Malcolm Miles, Noel Roberts
cc: Stephen Gibbs, Peter Knapper, Renato Zambon, Ariel Nardelli
cc: Joe Rinck, Rob Borland, Doug Rigby, Michael Reed, Lishan Adam
cc: Mark Bennett, Moussa Fall, Chuma Agbodike, Michael Cracknell
cc: tempRC (Anatoli Tung), tempRC (Fatman Wong), Tommy Wu
cc: Carol Shenkenberger, Terry Roati, Lawrence Fan, Bill Harms
Hi guys and gals!
Well, well... it's been 5 months since we began penning a P4 proposal.
In that time, we have arrived at a relatively agreeable document, with
the possible exception of whether to require a minimum number of
voters in the initiation, referendum, and/or balloting stages. There've
been a few small wording changes to the original draft, but mostly for
clarification. Once the question of quora is resolved, we will have the
revised draft ready to put before the RC's for referendum.
This will all be redundant however, if the RC's aren't adequately and
fairly informed of the proposal. I am disappointed that this has not yet
happened, to the point of exercising some persuasion of my own. I've
netmailed all the RC's, with an invitation/request to link and rescan the
FIDOPOLS echo, but haven't heard back from any of them. Nor have I
seen them in the echo.
So, I would enlist your added assistance in contacting your RC's and
NC's, via whatever means are at you disposal, with (preferrably fair and
unbiased) information regarding our efforts (if you have not already
done so), and ask them for their attention and participation.
I understand that it has been many years since a change in Policy has
been realised, though several attempts have been made, and that few
are willing to jump into this without due consideration. On the other
hand, delaying the process (perhaps to the point of killing it) too long
may have the same negative effect as earlier views of "it can't be done"
and reinforcing general apathy and/or disallusionment.
If any of you are unaware or unclear of the latest proposed changes, I
will be more than happy to send you a synopsis. :)
Thank you for you help. Together we can reassure the members of
FidoNet that we aren't as stagnent as was previous thought.
Bob Short
bsbbser@juno.com
* Forwarded (from: FIDOPOLS) by Goran Eriksson using timEd/2 1.10.y2k+.
* Originally from Bob Short (1:105/38) to All.
* Original dated: Thu Jul 11, 23:16
This message contains extracted text from the Policy 4 amendment proposal
as revised by Bob Short, Dale Shipp, et al, referencing the sections to be
amended (denotated with preceding **).
-----------------------------------------------------------------------------
**Remove the following sentence
(There are no differences between this version and 4.06 except the statement
above.)
-----------------------------------------------------------------------------
1.3.1 FidoNews
FidoNews is a weekly newsletter distributed in electronic form throughout
the network. It is an important medium by which FidoNet sysops communicate
with each other. FidoNews provides a sense of being a community of people
with common interests. Accordingly, sysops and users are encouraged to
contribute to FidoNews. Contributions are submitted to node 1:1/1; a file
describing the format to be used is available from 1:1/1 and many other
systems.
**Be amended as follows:
1.3.1 FidoNews
FidoNews is a weekly newsletter distributed in electronic form throughout
the Network. It is a very important medium by which FidoNet participants,
including SysOps, points, and users alike, communicate with each other, and
helps to provide a communal sense of people with common interests. Thusly,
participants are encouraged to both read and contribute to FidoNews. All
contributions are submitted to the FidoNews Editor via the contact method(s)
listed at the beginning of each issue, or may addressed to the node number
listed under FidoNews_Editor in the latest FidoNet nodelist. A description
of the required format for submissions is listed at the bottom of each issue,
and available on file from the Editor, as well as many other FidoNet systems.
-----------------------------------------------------------------------------
8.1 Initiation
A referendum on policy modification is invoked when a majority of the FidoNet
Regional Coordinators inform the International Coordinator that they wish to
consider a proposed new version of Policy.
**Be amended as follows:
8.1 Initiation
A Referendum on Policy modification is initiated when a 5% minimun, in any
combination, of eligible voters (as defined by section 8.3), inform the
International Coordinator that they wish to initiate a Policy referendum.
The International Coordinator, or his delegate, must then notify all Regional
Coordinators of the request via netmail within two weeks. After notification
is sent, the request must be published in the next edition of FidoNews.
Regional Coordinators will then have 30 days to consult their constituants
and respond according to the consensus of their respective regions. A vote
is required when a majority of responding Regional Coordinators indicate that
they wish to consider an amendment to, or new version of, current Policy.
8.1.1
Any request for referendum initiation must be accompanied by a description of
the proposed changes, and include a synopsis of why the changes are desired.
Ideally, such a request will be preceeded by informal discussions, wherein a
preliminary proposal draft is agreed upon by the presenting group.
8.1.2
If the International Coordinator position is vacant during a Policy amendment
initiation, referendum, ratification or enactment phase, the Zone Coordinator
Counsel (or thier delegate) shall fulfill the prescribed duties in lieu of an
International Coordinator.
-----------------------------------------------------------------------------
8.2 Announcement and Results Notification
Proposed changes to Policy are distributed using the same structure which is
used to distribute nodelist difference files and FidoNews. Results and
announcements related to the referendum are distributed by the coordinator
structure as a part of the weekly nodelist difference file. The Interna-
tional Coordinator provides copies to the editor of FidoNews for inclusion
there, although the official announcement and voting dates are tied to
nodelist distributions.
If it is adopted, the International Coordinator sets the effective date for a
new policy through announcement in the weekly nodelist difference file. The
effective date will be not more than one month after the close of balloting.
**Be amended as follows:
8.2 Announcement and Results Notification
Proposed changes to Policy are distributed using the same structure used to
distribute the weekly nodelist difference files and FidoNews. Announcements,
proposals and results related to the referendum and balloting are distributed
by the Coordinator structure as a part of the weekly nodelist difference
file. The International Coordinator provides copies to the editor of FidoNews
for inclusion there, although the official announcement and voting dates are
tied to nodelist distributions.
If it is adopted, the International Coordinator sets the effective date for a
new policy through announcements in the weekly nodelist difference files and
in the next issue of FidoNews. The effective date will be not more than one
month after the close of balloting.
-----------------------------------------------------------------------------
Bob
___ GEcho 1.00
- Origin: BS BBS - Get yer BS here... (1:105/38)
* Forwarded (from: FIDOPOLS) by Goran Eriksson using timEd/2 1.10.y2k+.
* Originally from Bob Short (1:105/38) to All.
* Original dated: Thu Jul 11, 23:16
-----------------------------------------------------------------------------
8.3 Eligibility to Vote
Each member of the FidoNet coordinator structure at and above Network Coordi-
nator is entitled to one vote. (Hub coordinators do not vote.) In the case
of the position changing hands during the balloting process, either the
incumbent or the new coordinator may vote, but not both. If a person holds
more than one coordinator position, they still receive only one vote.
Network coordinators are expected to assess the opinions of the members of
their network, and to vote accordingly. A formal election is not necessary,
but the network coordinator must inform the net of the issues and solicit
input. The network coordinator functions as the representative of the rank
and file members of FidoNet.
**Be amended as follows:
8.3 Eligibility to Vote
Each member of the FidoNet coordinator structure at and above Network Coordi-
nator is entitled to one vote. (Echomail Coordinators do not vote.) In the
case of a coordinator position changing hands during the balloting process,
the outgoing incumbent votes. If the outgoing coordinator can not cast the
vote for any reason, the new coordinator does so, according to the consensus
arrived at by the previous coordinator. Coordinators holding more than one
position have one vote, and must cast it at the highest level.
Network and Regional Coordinators function as the representatives of the rank
and file members of FidoNet, and as such are required to elicit the opinions
of their member nodes and vote accordingly.
-----------------------------------------------------------------------------
8.4 Voting Mechanism
The actual voting mechanism, including whether the ballot is secret and how
the ballots are to be collected, verified, and counted, is left to the
discretion of the International Coordinator. Ideally, ballot collection
should be by some secure message system, conducted over FidoNet itself.
In order to provide a discussion period, the announcement of any ballot must
be made at least two weeks before the date of voting commencement. The
balloting period must be at least two weeks.
**Be amended as follows:
8.4 Voting Mechanism
The actual voting mechanism, including how the ballots are to be collected,
verified, and counted, is left to the discretion of the International Coordi-
nator. Ideally, ballot collection should primarily be by a secure message
system, conducted over FidoNet itself, but must be publicly announced, and
voting made available in an open and internationally available echomail
conference. The echo tag, and moderator of this conference, is left to the
discretion of the International Coordinator.
In order to provide a discussion period, the announcement of any ballot must
be made at least two weeks before the date of voting commencement. The
balloting period must be at least 21 calendar days.
-----------------------------------------------------------------------------
8.5 Voting on a whole Policy Document
Given that Policy is intertwined and self referencing, a relatively simple
change may require several alterations of the document. In order to simplify
the process, balloting is done on choices between whole documents, rather
than individual amendments. In the simplest case, this means voting yea or
nay to a new document. If a number of alternatives are to be considered,
they must be presented as whole documents, from which one is chosen.
**Be amended as follows:
8.5 Voting as individual ballots
Amendment proposals are presented and voted on individual ballots, although
more than one ballot may be presented consecutively in a given voting period.
8.5.1
In order to avoid inconsistancies in a ratified document, amendment proposals
must include provisions amending all other relevant sections and subsections
before they are presented for ratification.
-----------------------------------------------------------------------------
8.6 Decision of vote
A Policy amendment is considered in force if, at the end of the balloting
period, it has received a majority of the votes cast. For example, if there
were 350 eligible voters, 100 of which cast a vote, then at least 51 affirma-
tive votes would be required to declare the amendment in force.
In the case of multiple policy changes which are considered on the same
ballot, a version must receive more than 50% of the votes cast to be consid-
ered ratified. "Abstain" is a valid vote in this case, effectively being a
vote for not changing the current policy as it simply increases the number of
votes required to ratify the proposed change.
**Be amended as follows:
8.6 Decision of vote
A Policy amendment is considered in force if, at the end of the balloting
period, it has received a majority of the eligible votes cast. For example,
if there are 100 eligible votes cast, then at least 51 affirmative votes
would be required to declare the amendment in force.
(repealing the second paragraph.)
-----------------------------------------------------------------------------
Bob
___ GEcho 1.00
- Origin: BS BBS - Get yer BS here... (1:105/38)
---
* Origin: GET, Lulea, Sweden, +46-920-257910 (2:201/505.1)
|