Text 3673, 151 rader
Skriven 2004-12-20 03:52:26 av FidoNews Robot (2:2/2.0)
Ärende: FidoNews 21:51 [05/09]: General Articles
================================================
clear.   Continued use  of aberrant  software after  this  period
shall be deemed excessively annoying.


VII.  ADOPTION OF POLICY

1.     ADOPTION:     This  policy  shall  become  effective  upon
ratification by  a  simple  majority  of  those  voting.    Those
eligible to  vote shall be the IC, ZCs, RCs, NCs, ZECs, RECs, and
NECs.   Those individuals holding more than one position can cast
only one vote.

2.   GRANDFATHER CLAUSE:   Within  60 days  of adoption  of  this
policy, moderators  shall be  appointed for all existing Echomail
Conferences which  do not now have a moderator.  Moderators shall
be appointed  by the  ZEC from those volunteering as moderator or
if no  volunteer is  available then  the ZEC  shall  request  and
appoint a  moderator for  the conference.  In the case where more
than one  individual claims to be the conference moderator and no
agreement can  be reached,  the  ZEC  may  order  the  conference
retired and  ban the further use of the specific conference name.
Failure of the individuals to retire the conference name shall be
deemed excessively annoying behavior.


VI.  BACKBONE STRUCTURE

This section  is for information purposes only.  It gives a plain
English description of the current structure and operation of the
Backbone.   The ZEC  may change  this structure  without amending
this document.

At the  top of  the  Echomail  distribution  network,  there  are
systems  commonly  called  Stars.    These  systems  are  usually
dedicated  to  passing  Echomail.    The  stars  operate  at  the
discretion and direction of the ZEC.  At the time of this writing
there are  3 stars, each has a backup system/plan in the event of
a failure.   In  general, the  Stars link to one another and feed
the RECs.

The RECs  are then  responsible for  distribution of the echomail
within their  Region.   Normally, the  REC will  feed the NECs in
that region.

The NEC  is responsible  for  distribution  of  Echomail  to  the
individual Sysops within a net.

Note that  the RECs  and NECs  can appoint  Hubs to  help in  the
distribution of  Echomail.  That is, they do not have to directly
feed the lower level.

This is  the distribution  GOAL.  Because of less expensive phone
rates and other reasons, this distribution method is not followed
exactly.  Any change to the above requires agreement of the *EC's
involved.   All *ECs  will use  all the  tools at their disposal,
such as hubs, high speed modems, ROA, Wide Area Calling plans, PC
Pursuit, corporate sponsorship, etc., to provide fast, efficient,
and cost effective movement of echomail.


Echopol Committee

Mike Ratledge
Norm Henke
Rick McWilliams
Barry Shatswell

-----------------------------------------------------------------
                          What is???
                          Matt Mc Carthy
                          1:396/45.17


The first paragraph below is taken from the already approved and
functioning document "FidoNet(tm) Internetwork Gateway Policy",
dated July 22, 1990.  Added to it represents what I believe to be
"Common Practice" at this time, as stated by many in MODERATOR and
FIDOECHOPOL, with a few of my own ideas included.  A few words have
been changed since it's original posting in 1989.

The purpose of this writing is:

1) To define "Echomail"
2) To define "Moderator"
3) To define "EchoList"
4) To assign Moderator responsibilities and limitations
5) To provide a link for review proceedures should this
   ever become 'policy'.



   "Echomail"
   ----------
   Echomail is the term used within FidoNet to refer to electronic
   "Conference Mail" messages that, while possibly containing
   the name of a particular individual in the "To:" field, are
   copied and distributed to multiple (possibly several hundred)
   destination systems.  Echomail messages are segregated into
   "Conferences" based upon the topic being discussed.  Echomail
   message content is usually restricted to the topic(s) for which
   the particular conference was created.

   The originators of each of these Conferences, as well as their
   designees and successors are called "Moderators".  The "name" of
   each Conference is called its "Echotag".

   A listing of FidoNet Conferences, their respective Moderator(s),
   and those Moderators' electronic addresses, is contained in the
   monthly publication of the holder of FidoNet address 1:1/201.
   The title of this listing is "ELIST", short for EchoList.

   A Moderator is the owner of the Echotag of the respective
   Conference, but not its content.  A Moderator is empowered to
   establish and enforce rules of conduct and topicality to which
   users are enjoined to adhere.

   A Moderator grants permission to all participants to add the
   Moderator's Echotag to messages they post, in so far as the
   messages they post follow the rules of conduct and topicality
   as set forth in periodic postings by the Moderator.

   Each Moderator is solely responsible for insuring the conduct and
   topicality of their respective Conferences in consonance with
   their published rules.  No responsibility or authority beyond the
   Moderator's respective Conference is intended or implied.

   In accordance with this responsibility, a user's failure to adhere
   to the published rules of a Moderator is considered grounds for
   immediate revocation or restriction from use of said Echotag.

   A user who feels he is having a bad time because of a Moderator
   should let his local BBS System Operator (SysOp) know.  The SysOp
   can discuss the situation with the Moderator, resolve the dispute,
   or drop the echo in question in cases where the Moderator is
   unreasonable.

   A Moderator request for action must receive immediate action by
   the recipient.

   As always, any errors may be subject to normal FidoNet review
   proceedures under existing policy, should a complaint be lodged.


(Ver. JJ6)

M.

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

--- Azure/NewsPrep 3.0
 * Origin: Home of the Fidonews (2:2/2.0)