OK folks,

I have made spelling corrections in the proposal, and (amended summary).

Here's what you'll see in this week's FidoNews:



      FidoNet Policy Amendment process announcement

More than a year ago, several nodes gathered in the FIDOPOLS echo
to discuss drafting a Policy amendment proposal.  What started as
a trial change to the FidoNews Editor address, ended up becoming
what we believe is an answer to the "Policy can't be changed" theory.
With a few relatively simple adjustments to specific sections, and
some equitable additions, this proposed amendment will better enable
our network to enact future changes as times and events require.

As of this writing, some 32 RC's have connected to the IC echo to
read and discuss this proposal, debate any possibles changes to it,
and then (after consulting with their respective regions) vote on
whether they want to refer the ensuing draft to the network for
ratification.  We believe, given due consideration, this amendment
can, and should, succeed.

All Regional Coordinators not already linked to the IC echo are
asked to request it, and join in the process.  It is anticipated
that the process will take 60 days to complete (30 to discuss the
proposal, and 30 to refer it to the regional nodes).  As in all
matters regarding operation of the network,  your participation is
an important responsibility, one that should be neither ignored nor
taken lightly.

With the help of other originators, I will be in the echo to answer
any questions you might have, and offer as clear clarifications as
possible.  In addition, both Spanish and Russian translations of the
proposal and the summary are available on request from 1:105/38 or
fidobbs{at}juno.com.

Regards,

Bob Short
1:105/38
fidobbs{at}juno.com
------------------------------------------------------------------------

                Policy amendment proposal synopsis

Following is a summary of proposed changes to Policy 4.07.


- Removing specific contact info for the FidoNews editor, to allow for an
  editor outside of Zone one.

- Removing specific dates nad numbers from the opening historical preamble.

- Several changes to, and a clearer formatting of, section 8, including:

Enumeration of the 3 stages of policy change (Initiation, Referendum,
and Ratification).

Adding minimum votes required in each stage to validate each one.  IE:
5% for initiation, 10% for referendum, and 10% for ratification.

Designating "abstain" as a validating vote only, yet not counted either
as "yes" or "no".

Allowing the IC to name a delegate(s) to oversee the process of policy
change, and adding provisions for cases where the IC position is empty
during policy change proceedings.

Changing the requirements for referendum to a majority of responding
RC's, instead of all RC's.

Adding that initiations to policy be accompanied by a synopsis of the
proposed changes, with reasons why they are desired, and suggesting it
be preceded by informal debate and agreement among the drafters.

Placing specific lengths to periods of debate and voting during the
initiation and ratification stages, and minimum time periods for voting.

Removing the "voting on multiple documents" reference, and calling for
separate ballots for each proposal, yet allowing for sequential ballots
within a voting period.

Requiring that any proposal include amendments to all relevant sections,
to avoid inconsistencies to a ratified document.

Re-referencing pointers in 8.7 (Impeachment) to pertinent sections.

------------------------------------------------------------------------



                 Proposal to amend FidoNet Policy version 4.07
-----------------------------------------------------------

**Remove the following sentence:

(There are no differences between this version and 4.06 except the statement
above.)
-----------------------------------------------------------


1.1  Introduction

FidoNet is an amateur electronic mail system.  As such, all of its partici-
pants and operators are unpaid volunteers.  From its early beginning as a few
friends swapping messages back and forth (1984), it now (1989) includes over
5,000 systems on six continents.

**Be amended as follows:

1.1  Introduction

FidoNet is an amateur electronic mail system.  As such, all of its partici-
pants and operators are unpaid volunteers.  From it's beginning in 1984 as a
few friends exchanging messages, it has grown into a truly global network.
-----------------------------------------------------------------------------


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 be 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  Referenda

** Be replaced entirely by:

8  Policy Revision

The procedures described in this section are used to ratify a new version of
FidoNet Policy,  which is the mechanism by which Policy is changed,  and are
divided into three stages:  Initiation, Referendum, and Ratification.  Each
stage must attain a minimum number of votes for validation, before the next
stage may occur.  Only "Yes" and "No" responses are
counted.  Abstain is not
considered a valid vote, although does count toward any quorum.

Network and Regional Coordinators function as the representatives of the rank
and file members of FidoNet, and as such are expected to solicit the opinions
of their member nodes, and vote accordingly.

These procedures are also used to impeach a Zone Coordinator.  (see section
8.7)

8.1  Eligibility to vote

8.1.1

In the initiation and ratification stages, each FidoNet coordinator at and
above Network Coordinator is entitled to one vote.  In the referendum stage,
only Regional Coordinators may vote.  Echomail Coordinators can not vote.

8.1.2

A Coordinator holding the positions of both Network and Regional Coordinator
may cast only one vote according to the combined will of both the Network and
the Region served.

8.1.3

In the case of a coordinator position changing hands during any stage of the
process, the outgoing coordinator 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.

8.2 Initiation

8.2.1

A referendum on Policy modification is initiated when a 5% minimum, in any
combination, of all eligible voters (as defined in section 8.1) give notice to
the International Coordinator that they wish to consider an amendment to, or
a new version of, Policy.

8.2.2

The International Coordinator, or his delegate(s), must attempt to notify all
Regional Coordinators of the request via netmail within 21 days, and publish
a notification in the next edition of FidoNews.   Regional Coordinators will
then have 30 days to consult their constituents and respond to the referendum
according to the consensus of their respective regions.

8.2.3

If the International Coordinator position is vacant during a Policy amendment
initiation, referendum, ratification or enactment phase, the Zone Coordinator
Council (or their delegate) shall fulfill the prescribed duties in lieu of an
International Coordinator.

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.


8.3  Referendum

A vote to ratify amendments to, or new versions of, Policy is mandated when
a majority of Regional Coordinators responding to a referendum, indicate that
they wish to consider a Policy change.  Referendum validation requires that a
10% minimum of all Regional Coordinators respond.


8.4  Ratification

Upon successful initiation and referendum, the International Coordinator must
announce and conduct a ballot to ratify a Policy amendment. The actual voting
mechanism, including how the ballots are collected, verified, and counted, is
left to the discretion of the International Coordinator.

8.4.1

In order to provide a discussion period, the announcement of any ballot must
be made at least 30 days before the date of voting commencement. A balloting
period must be at least 21 days.

8.4.2

A Policy amendment is considered in force if, at the end of the balloting
period, it receives a majority of affirmative votes.  A 10% minimum of all
eligible voters (as defined in section 8.1) is required for validation.  For
example, if there are 600 coordinators, a minimum of 60 must vote to validate
the stage.  If 100 cast ballots, then at least 51 must vote yes to declare
the amendment in force.


8.5  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 therein, although the official announcement and voting dates are
tied to nodelist distributions.

If adopted, the International Coordinator sets the effective date for a new
version of 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.


8.6  Voting as individual ballots

Amendment proposals are presented and voted on as individual ballots, although
more than one ballot may be presented consecutively in a given voting period.


** The following changes are in references to sections 8.1 - 8.6 only.

8.7  Impeachment of a Zone Coordinator

8.7.1  Initiation

In extreme cases, a Zone Coordinator may be impeached by referendum.  Im-
peachment of a Zone Coordinator does not require a Policy violation.  An
impeachment proceeding is invoked when a majority of the Regional Coordina-
tors in a zone request the International Coordinator to institute it.

8.7.2  Procedure as in Policy Referendum

The provisions of sections 8.1 and 8.6 apply to impeachment referenda.

The definition of "majority" in section 8.4.2 applies.  Only
coordinators in
the affected zone vote (even if the zone coordinator is also the Internation-
al Coordinator).

8.7.3  Voting Mechanism

The balloting procedures are set, the votes are collected, and the results
are announced by a Regional Coordinator chosen by the Zone Coordinator who is
being impeached.  The removal of the Zone Coordinator is effective two weeks
after the end of balloting if the impeachment carries.

8.7.4  Limited to once per year

The removal of a Zone Coordinator is primarily intended to be a mechanism by
which the net as a whole expresses displeasure with the way Policy is being
interpreted.  At one time or another, everyone is unhappy with the way policy
is interpreted.  In order to keep the Zone Coordinators interpreting policy
as opposed to defending themselves, at least one full calendar year must
elapse between impeachment referenda (regardless of how many people hold the
position of Zone Coordinator during that year.)

Should a Zone Coordinator resign during an impeachment process, the process
is considered null and void, and does not consume the "once per year
quota".

---