                 -----------------------------------------
                   New England Network Policy Guidelines
                -----------------------------------------
                  [Formerly known as RI-Net since 1988]
                     Revision 1.07 - As of 03/01/93


I    Network Overview
     ================

     New England Net (NE-Net) is a co-operative effort of many high quality
     bulletin board systems and users.  The network welcomes any computer
     type or bbs software which is capable of exchanging net mail with other
     systems.  We currently support the following networking technologies:
     Postlink, Fido echomail, Qnet/QWK(Rnet, Tnet, Cnet, etc). We are a small
     general interest network serving the New England area. Boards outside of
     the NE area are also welcomed to join. 

     Network Motto:    "It's ONLY A Hobby!"  <GRIN>

     Our goal is to provide a friendly environment where users can discuss
     social and technical related topics. The network is divided into Special
     Interest Group conferences (SIGs), and each area is managed by a worthy
     Conference Host.  The network is privately managed as if it was a BIG
     BBS, with member systems subscribing for their echomail feeds(free). 
     The "sysop" in this BIG BBS CONCEPT is a group of volunteers known as
     the Steering Committee.  The Steering Committee is responsible to guide
     the network in all matters and gather opinions from the member sysops. 
     Important matters will be voted on by the SC.  NE-Net is operated as a
     private organization by the Steering Committee.  Membership to the SC is
     done by appointment of the present SC Membership. We feel that this
     structure provides a minimum of politics, while simply getting the mail
     through.  Sysop feedback is VERY important and will help to guide the
     network - however, final decisions will be made by the Steering
     Committee.
   
     The network's Steering Committee currently includes:
       -  Ray Joyce, Conference/Membership Coordinator
       -  Mike Labbe, Network Coordinator
       -  Terry O'Dowd, Conference/Quality Coordinator
       -  Sally Renehan, Information Manager/PR


II   Operational Concept and Definition
     ==================================

                  -NETHUB-
            Ŀ
                             
                             
                 NODE        NODE
           HUB           HUB   
           / \           / \
        NODE NODE     NODE NODE


     HUB -- A hub is any board that distributes mail to other systems.  Hubs
       are established in new calling areas to distribute mail to other
       local boards.  This method minimizes toll charges.

     NODE -- A node is any participating BBS.  Nodes can call a regional hub,
       or directly into the NETHUB as long as arrangements are made in
       advance.  Nodes are not called by any other systems in the net.
 
     NET HUB -- The nethub is where the network originates, and does not make
       outgoing calls for mail.  The nethub sysop will be responsible for
       overall network operation and direction.  The nethub supports
       multiple networking technologies, and is responsible for moving the
       mail between the various packet formats and to keep it flowing
       properly without duplicates.  The NE-Net nethub system is Eagles Nest
       Communications.


III  Conference Hosts
     ================

     Each special interest group is GUIDED by a dedicated volunteer whose
     responsibilities include 
       -  assuring that net guidelines are used
       -  posting topic information approximately monthly to define the
          goals of the base
       -  preventing bashing
       -  keeping the mail flowing by introducing new topics and suggestions
          in the area of interest.

     Conference hosts are present to encourage friendly discussion and
     introduce new topics -- enforcement of policies should not be done in a
     heavy-handed manner. Problems with users may sometimes arise in the
     SIGS.  If a situation cannot be remedied by a friendly reminder to the
     user, hosts are asked to contact the Steering Committee.  In those rare
     cases, the SC will handle the situation according to its discretion
     which may include asking the sysop(s) of that board to address the
     situation discreetly and personally.  

     A current list of conferences can be found on the nethub, or in the
     latest NENETxxx.ZIP "Information Pack".  Conference suggestions and host
     volunteers are heartily welcomed, and can be directed to NE-Net Common. 
     One person may host up to two NE-Net conferences.


IV   New England Net Policies
     ========================

     Although we are a friendly, social type of network, some rules are 
     required.  Our common sense guidelines have been spelled out here to
     head off most problems before they happen and to answer questions.  Some
     conferences have additional guidelines, which are defined in the
     NENET.CNF document.
       a) Private and/or confidential mail is NOT supported via the network,
          pursuant to the Electronic Communications Privacy Act of 1986. 18
          USC 2510, et al.  All systems operators participating in the
          network have access to any mail which is sent with the R/O flag. 
          Although the messages will be passed, this is discouraged except
          for sysop communications.

       b) Quality Assurance:  All users are to be verified, either by
          call-back door, voice, post card, etc., prior to being granting
          "post" access in the NE-NET bases.  We reserve the right to
          request member sysops to confirm user identity when a situation
          warrants it.

       c) ANSI messages and signatures are limited to the BBS ADS
          conference.  Some users and participating systems have equipment
          which is not compatible with ANSI, and these messages should be
          discouraged.

       d) BBS Ads are limited to the BBS ADS conference. Sysops are
          encouraged to post ads for their bbs in this base, but no more
          than once in 14 days.

       e) Profanity, abusive language, personal attacks, and bashing will
          not be tolerated under any circumstances. It is the responsibility
          of the conference host, the SC, and the node sysop to deal with
          offenders of this policy in a professional and timely manner.  If
          all parties are not satisfied with the resolution, the SC may, at
          its discretion, have the user's access to the network suspended
          for a period of time.  The SC will send a note to the sysop
          informing them of the situation.  If the sysop does not address
          the problem in 36 hours, that system may be temporarily suspended.

       f) Handles and aliases are not permitted in message headers, but are
          welcomed within messages and tag lines.
          Handles ARE allowed in certain bases. See NE-NET.CNF for details. 
          
       g) All member boards must carry the NE-NET COMMON message base.  This
          conference will contain network announcements and information.

       h) System operators are responsible to inform their  users of the
          NE-NET guidelines and are encouraged to extract any portion of
          this file or the conference description file for public
          posting/bulletins/news files.  Sysops are responsible for messages
          leaving their system and are asked to post this file for public
          download (NENET???.ZIP).

       i) Distribution and exchange of NE-NET messages with other systems is
          strictly prohibited, unless system has been admitted by the SC. 
          All gateways with other networks must be under direction of the
          nethub. We will make every effort to verify a recommended board
          within 24 hours.

       j) Any commercial use of the network is strictly prohibited.
          Vendors may post a sale message no more than once in a two week
          period. These messages are allowable in the FOR SALE section only.
          See NE-NET.CNF for more information on this policy.

       k) All nodes and regional hubs are expected to transfer   mail no
          less than 3 times per week with approved and tested net software. 
          A DAILY event would be perfect for this purpose. If a system is
          unable to meet this requirement due to sysop vacation or technical
          problems, we would appreciate notification.

       l) System tag lines should be in a standard format. For Example:
          "NE-Net * Eagles Nest Communications * Providence, RI *(401)732-5290"

       m) These policies may be amended at any time without prior notice. 
          All member sysops are encouraged to give their input, and these
          discussions should take place in the NE-Net Sysops' conference. 
          Management reserves the right to suspend transfers with any system
          on the network whenever it deems necessary to ensure that the
          goals of the network are met.
------------------------------------------------------------------------------

          NE-Net:  "The Network for the USERS"


          Please Refer All Inquiries To:

          New England Network
          P.O. Box 23392
          Providence, RI  02903

          Nethub: (401) 732-5290
          Fido ID: 1:323/126
