(Part 4 of 6)

The Zone Coordinator is responsible for insuring the smooth operation of
gates between that zone and all other zones for the transfer of interzonalmail.

The Zone Coordinators are responsible for the selection of the International
Coordinator from among their ranks.


6.2  Selection

The Zone Coordinator is selected by an absolute majority vote of the Regional
Coordinators within the zone.


7  International Coordinator Procedures

7.1  General

The International Coordinator is the "first among equals" Zone Coordinator.

The International Coordinator has the primary task of coordinating the
creation of the master nodelist by managing the distribution between the
Zones of the Zone nodelists.  The International Coordinator is responsible
for definition of new zones and for negotiation of agreements for communica-
tion with other networks.  ("Other network" in this context means other
networks with which FidoNet communicates as peer-to-peer, not "network" in
the sense of the FidoNet organizational level.)

The International Coordinator is also responsible for coordinating the
distribution of Network Policies and FidoNews to the Zone Coordinators.

The International Coordinator is responsible for coordinating the activities
of the Zone Coordinator Council.  The International Coordinator acts as the
spokesman for the Zone Coordinator Council.

In cases not specifically covered by this document, the International Coordi-
nator may issue specific interpretations or extensions to this policy.  The
Zone Coordinator Council may reverse such rulings by a majority vote.

7.2  Selection

The International Coordinator is selected (or removed) by an absolute majori-
ty vote of the Zone Coordinators.


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.

8.2.4

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.


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".


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.2 and 8.3 apply to impeachment referenda.

The definition of "majority" in section 8.6 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".


9  Resolution of Disputes

9.1  General

The FidoNet judicial philosophy can be summed up in two rules:

     1) Thou shalt not excessively annoy others.

     2) Thou shalt not be too easily annoyed.

In other words, there are no hard and fast rules of conduct, but reasonably
polite behavior is expected.  Also, in any dispute both sides are examined,
and action could be taken against either or both parties. ("Judge not, lest
ye be judged!")

The coordinator structure has the responsibility for defining "excessively
annoying".  Like a common definition of pornography ("I can't
define it, but
I know it when I see it."), a hard and fast definition of acceptable FidoNet
behavior is not possible.  The guidelines in this policy are deliberately
vague to provide the freedom that the coordinator structure requires to
respond to the needs of a growing and changing community.

The first step in any dispute between sysops is for the sysops to attempt to
communicate directly, at least by netmail, preferably by voice.  Any com-
plaint made that has skipped this most basic communication step will be
rejected.

Filing a formal complaint is not an action which should be taken lightly.
Investigation and response to complaints requires time which coordinators
would prefer to spend doing more constructive activities.  Persons who
persist in filing trivial policy complaints may find themselves on the wrong
side of an excessively-annoying complaint.  Complaints must be accompanied
with verifiable evidence, generally copies of messages; a simple word-of-
mouth complaint will be dismissed out of hand.

Failure to follow the procedures herein described (in particular, by skipping
a coordinator, or involving a coordinator not in the appeal chain) is in and
of itself annoying behavior.


9.2  Problems with Another Sysop

If you are having problems with another sysop, you should first try to work
it out via netmail or voice conversation with the other sysop.

If this fails to resolve the problem, you should complain to your Network
Coordinator and the other sysop's Network Coordinator.  If one or both of you
is not in a network, then complain to the appropriate Regional Coordinator.
Should this fail to provide satisfaction, you have the right to follow the
appeal process described in section 9.5.


9.3  Problems with your Network Coordinator

If you are having problems with your Network Coordinator and feel that you
are not being treated properly, you are entitled to a review of your situa-
tion.  As with all disputes, the first step is to communicate directly to
attempt to resolve the problem.

The next step is to contact your Regional Coordinator.  If your case has
merit, there are several possible courses of action, including a change of
Network Coordinators or even the disbanding of your network.  If you have
been excommunicated by your Network Coordinator, that judgement may be
reversed, at which point you will be reinstated into your net.

If you fail to obtain relief from your Regional Coordinator, you have the
right to follow the appeal process described in section 9.5.


9.4  Problems with Other Coordinators

Complaints concerning annoying behavior on the part of any coordinator are
treated as in section 9.2 and should be filed with the next level of coordi-
nator.  For example, if you feel that your Regional Coordinator is guilty of
annoying behavior (as opposed to a failure to perform duties as a coordina-
tor) you should file your complaint with the Zone Coordinator.

Complaints concerning the performance of a coordinator in carrying out the
duties mandated by policy are accepted only from the level immediately below.
For example, complaints concerning the performance of Regional Coordinators
would be accepted from Network Coordinators and independents in that region.
Such complaints should be addressed to the Zone Coordinator after an appro-
priate attempt to work them out by direct communications.


9.5  Appeal Process

A decision made by a coordinator may be appealed to the next level.  Appeals
must be made within two weeks of the decision which is being appealed.  All
appeals must follow the chain of command; if levels are skipped the appeal
will be dismissed out of hand.

An appeal will not result in a full investigation, but will be based upon the
documentation supplied by the parties at the lower level.  For example, an
appeal of a Network Coordinator's decision will be decided by the Regional
Coordinator based upon information provided by the coordinator and the sysop
involved; the Regional Coordinator is not expected to make an independent
attempt to gather information.

The appeal structure is as follows:

   Network Coordinator decisions may be appealed to the appropriate Region-
   al Coordinator.

   Regional Coordinator decisions may be appealed to the appropriate Zone
   Coordinator.  At this point, the Zone Coordinator will make a decision
   and communicate it to the Regional Coordinators in that zone.  This
   decision may be reversed by a majority vote of the Regional Coordina-
   tors.

   Zone Coordinator decisions may be appealed to the International Coordi-
   nator.  The International Coordinator will make a decision and communi-
   cate it to the Zone Coordinator Council, which may reverse it by majori-
   ty vote.

If your problem is with a Zone Coordinator per se, that is, a Zone Coordina-
tor has committed a Policy violation against you, your complaint should be
filed with the International Coordinator, who will make a decision and submit
it to the Zone Coordinator Council for possible reversal, as described above.


9.6  Statute of Limitations

A complaint may not be filed more than 60 days after the date of discovery of
the source of the infraction, either by admission or technical evidence.
Complaints may not be filed more than 120 days after the incident unless they
involve explicitly illegal behavior.


9.7  Right to a Speedy Decision

A coordinator is required to render a final decision and notify the parties
involved within 30 days of the receipt of the complaint or appeal.


9.8  Return to Original Network

Once a policy dispute is resolved, any nodes reinstated on appeal are re-
turned to the local network or region to which they geographically or techni-
cally belong.

---