Home » Previous Page » Article:

FamilyNet BBS Network Policy Statement

FamilyNet BBS Network Policy Statement

The G Rated BBS Network

 

FamilyNet International

The G Rated BBS Network

 

Revised  11/19/96 FAMILYNET INTERNATIONAL
FAMILYNET  is  a  private  association  of  NETMAIL  compatible nodes.  
Members  of  FAMILYNET  have no rights per se, every BENEFIT available  to  FAMILYNET  Nodes is conditional, and revokable at any time with no 
advanced  notice,  and  without  cause  by  any level of management in  FAMILYNET.  Membership  in  FAMILYNET is a privilege, revokable at any 
time without cause by the management of FAMILYNET.

 

Having  said  the  above  -  let  me  add:  FAMILYNET  is  a  means to  alternatives.  We  were  founded to offer sysops a choice. If you have  problems  with  one manager, you are able to contact any other manager  that  will  have  you. This gives the managers a free hand, and allows  people  to peacefully coexist. All levels of FAMILYNET managers should  subscribe  to the theory - if one node is having problems, they should  do whatever they need to do to help solve the problem for EVERYONE.
                        Requirements for Membership
1) Netmail Compatible mailer - All members must have a "mailer" that    is capable of communicating with other mailers in FAMILYNET. 2) G Rated System - All systems must be "G" rated. No profanity,    obscenity on member systems. Each member should be a 'FAMILY'    type/rated system. 3) No illegal activities - credit card numbers, phreaking (illegal    long distance) codes, passwords, pirating of software, are some of    the illegal activities that are expressly forbidden. This list is    not by any means intended to be all inclusive. 4) No threats are permitted to any other node in FAMILYNET, or    outside FAMILYNET. Threats include damage to software/systems, law    suits, personal harm, etc. Local/National Managers will make the    determination as to what constitutes a "threat."
                        Applying for Membership 1) Obtain a current copy of the FMLYLIST (this is the list of nodes    in FAMILYNET). 2) If you are a member or if you join a SIGNET, your SIGNET    membership entitles you to all the benefits of membership in    FamilyNet.  3) Send a message to the manager that would handle your geographical    area, or area of interest (Special Interest Nets).
           The message should contain:                 Name of Your System.                Name of System Operator (Your name).                Location of System (ie Los Angelas, Ca).                Phone number of System (where other nodes can                     deliver) mail - pvt or unlisted nodes are not                     permitted).                Baud rate of your system                Name and version of mailer (or proper flags if known).                     Allowable flags are listed at bottom of FMLYLIST.                Hours that system is available for mail.                Type of Modem system is running (For flags).                Voice Phone Number - a number where your manager can                     call you in the case of problems.
Note: Points can be issued a regular node number in the network as       long as their 'boss node' phone number is listed under their       listing.
If  you  are  having problems with a manager, contact the next manager  up  the  line  and  request a node number from him/her. If you have at  least  three nodes, you can request another network, even if a network  is  existing  in the same geographical area. Note: Members may only be  members of ONE geographical network if two exist in the same area.                              Positions *   Node - One system (may be a BBS or Point) *   Point - A system connected to FAMILYNET that is not public/has no     users other than the operator. *   Local FAMILYNET (Net) - A group of nodes in a local     (geographical) area, or areas of special interests (SIGNETS),     Managed by a FAMILYNET Manager (Host). *   Regional Manager - Has a REGION in the FMLYLIST. A Region is     comprised of a group of NETS. Regions should have at least 50     separate nodes at the minimum. *   Zone Manager - Has a group of REGIONS in the FMLYLIST. Can be     SIGNET, or Geographical. *   International Director - Gives direction to the entire network.     Day to day operation rests with the Managers. The director will     set policy and have the final say in resolving disputes. Disputes     should be settled at the lowest level in the heirarchy. Managers     are empowered to resolve any disputes at their level. *   Moderator - Runs an echomail conference. A moderator of an     echomail conference has complete control of that conference.     All FAMILYNET nodes acknowledge the rights of the moderator to     take whatever measures necessary to control the integrety of     their conference. This includes dictating the guidelines for     participating in a conference, and the power to order feeds be     cut for a given conference (a conference will include both     echomail and groupmail for the purpose of this document). *   Echomail Coordinator - This position is responsible for     making sure that echomail flows smoothly. This person will also     be responsible for creating and maintaining an echomail list     for all FAMILYNET Echoes/Groups. The echomail Coordinator will     have the final say in where feeds may be made - by permission     of the moderators, in the case of disputes/problems. Free flow     of echomail dictates that any node can go anywhere to get any     feed they like (exception is gated echomail).
                            Required Conferences The  following  conferences  are required for all FAMILYNET nodes. You  are  NOT  required to get them, but are responsiblible for the content  in  them.  If  an  announcement is made in these conferences that puts  you  in  policy violation, for example, the fact you are not tied into  the  conference does not constitute a valid defense for not conforming  to  the  policy!  As  such it is STRONGLY suggested all nodes tie into  these conferences where applicable.
FAMILY_MGRS - All FAMILYNET managers and coordinators should be    tied into this echo/conference. This is where policy will be made    and discussed. This is also where all problems are discussed. By    default, the moderator of this conference will be the    International director. Only managers and coordinators may tie    into this conference. This conference is restricted.
FAMILY_SYSOP - This is the FAMILYNET sysop's echo. This is where    announcements are made, and topics of discussion of interest to    all sysops will take place. All FAMILYNET systems SHOULD have a    tie in to this conference. Announcements made in this conference    will be binding on all nodes. This conference should not need a    moderator. Only topics of interest to ALL sysops in FamilyNet    should be discussed here. Users may NOT have access to this    conference.
ECHOES - This is the place where echoes are searched for, commented    on, new echoes are announced, and notice of terminations are made.    Any Echo news should be made in the conference. By default, the     FamilyNet Echomail Coordinator is the moderator of this    conference. This conference is open to users and sysops.
                            Responsibilities                                  Node *  The  system  operator  running  a node is responsible for providing  correct information to list their node to their manager.
*  The node operator is responsible for notifying the manager when any  information  changes,  so  the FamilyList can be updated, and when the  node will go down for more than a 24 hour period. 
*  The  Node  must turn off their echomail and file areas before going  down,  or  make  arrangements  with their feed to hold mail for a pre- determined  period that the node will be down. Note: the mail and file  feeder does NOT have to accomodate the node to hold mail and files.
*  The Node must poll their immediate manager (this could be a Network  Manager,  a  Regional Manager, or a Zone Manager, depending on how the  node  is  listed  in  the  Familylist)  on  a weekley basis to pick up  routed mail.
*  The  node must paricipate in any local Network Conferences that are  required  by  the local Network, as well as the required International  Conferences and Regional Conferences.
                            Network Manager *  The  Network  Manager  compiles  their  local  network  segemnt for  inclusion in the FamilyList.
*  The  Network  Manager  must  make  available  to  his/her nodes the  current Fmlylist and/or Fmlydiff files on a weekly basis.
*  The  Network  Manager  is  responsible  for  creating  a FamilyList  segment  and  delivering  it  to  the appropriate manager (Regional or  Zone)  for  inclusion  in  the FamilyList in the timeframe required by  their manager.
*  The  Network  Manager  must  additionally meet all the requirements  stated for a node.
                            Regional Manager *  The  Regional  Manager  compiles  their  local  network segemnt for  inclusion in the FamilyList.
*  The  Regional  Manager  must  make  available  to  his/her nets the  current Fmlylist and/or Fmlydiff files on a weekly basis.
*  The  Regional  Manager  is  responsible  for  creating a FamilyList  segment  and  delivering  it  to  the  appropriate  manager (Zone) for  inclusion  in  the  FamilyList  in  the  timeframe  required  by their  manager.
*  The  Regional  Manager  must additionally meet all the requirements  stated for a node.
                            Zone Manager *  The Zone Manager compiles their local network segemnt for inclusion  in the FamilyList.
*  The  Zone  Manager  must make available to his/her nets the current  Fmlylist and/or Fmlydiff files on a weekly basis.
*  The  Zone  Manager is responsible for creating a FamilyList segment  and  delivering  it  to the appropriate manager (Zone 8) for inclusion  in the FamilyList
*  Zone  managers  have full control over their own Zones. SIGNETS are  fully  independent  zones  and may withdraw from the FamilyList at any  time for any reason. 
*  The Zone Manager must additionally meet all the requirements stated  for a node.
                        International Director *   The   International  Director  is  responsible  for  creating  and  distributing the FamilyList every Friday.
*   The   International   Director  must  additionally  meet  all  the  requirements stated for a node. 
             -----------------------------------------
If  a  manager  does  not  perform  any  of  their  defined roles in a  reasonable  amount  of  time,  that manager can be removed.  There are  three grounds for removal of a manager:
A) Violation of policy
B) Non-perfomance - a failure to perform the job as described in the    job descriptions as stated above.
C) Missing in Action - Failure to respond to netmail, phone calls or    messages in the Family_mgrs conference. (Note, any one of these    conditions is all that is necessary, all three are NOT necessary. 
The following guidelines apply.
1)  Any  node  getting  no response from a given manager should post a  message  in  the  Family Sysop Conference stating the problem and what  was  done  to  resolve  the  problem  (for  example,  state  that  you  requested  a FamilyList entry be updated and received no response from  your  manager,  and  the  list was not updated). State the time period  involved.  (This  will  not  be applicable for new member requests - a  node requesting membership should go to 2 as their first step).
2)  Address  a  netmail  message to the next level manager stating the  problem, and what you expect to happen.
3)  The  next  level  of  manager  will  send a netmail message to the  manager  that  is  not performing stating the problem and requesting a  resolution.  This  message  should  also  be  copied publically in the  FAMILY_MGRS  conference (a required conference for Managers). The non- performing  manager  should  reply  to  the  message  in the Manager's  conference  and  stated  what  was  done  (for example that he/she did  reply,  did  add to the FamilyList - but file did not go out, or state  reason  for  denying  access  to  node or Net). Additionally, the non- performing  manager  should be state what he or she will do to rectify  the  problem.  The  non-performing  manager  must  respond by the next  Friday  (minimum  of  one  week  is  given for the response) after the  complaint was filed.
4)  If the problem is not resolved, or the non-performing manager does  not  respond  in  the Family_mgrs conference, a second netmail message  and  posting  in  the  Family_mgrs  conference  will be made. The non- performing  manager  will  again have at least one full week (the next  Friday after second notification is made) to respond. as above.
5)  If  the  problem is not resolved (non-performance), or if the non- performing  manager does not respond (missing in action), they may, at  the discretion of the next manager be replaced. 
                      Replacement of Managers
Replacement  of  managers  is at the sole discretion of the next level  of  management.  It  is  not  automatic. It is recognized there may be  extenuating  circumstances that may have led to non-performance or MIA  status.

Tags:   BBS Documentation
 PDF  Print this article
Rating: 0.00 (0 votes) Rate this article
Bookmark and share this article: