 Updated: 19 Aug 94                              By: HOST SYS
                          TriNET Network Growth
                          ~~~~~~~~~~~~~~~~~~~~~

           Each TriLINK Hub can sponsor nodes in their areas.
        This means, the Hub can recommend other systems in their
        area as participants on the TriLINK Network. The sysops
        of these Hubs can forward the names of nodes downloading
        and uploading mail to their BBS by entering all of the
        node's information in the TriLINK Administration message
        conference. If a node is recommended by a Hub, the node
        will automatically be added to the Trinode.Lst file. The
        sysop of the Hub recommending the node will be responsible
        for the conduct of the node, in that, messages entered to
        Network conferences are acceptable. Normal common sense
        applies. It is important that the messages be kept clean
        and entered into the proper conferences.

           If a BBS wishes to join the TriLINK Network that is 
        not running TriBBS software, this is permissable as long
        as they can upload messages to the Hub in a format that
        is compatible to the QWK format used by TriBBS. They must
        carry the required conferences (first three) and any of
        the others available that they wish to choose. The whole
        idea of the Network is to allow systems to link together
        in order to provide the users of the paticipating BBSs
        with a means of communication with users in other areas.
        So, with this in mind, the more the merrier.

           If the TriLINK Network continues to expand, it will be
        necessary to devise a more organized method of identifying
        new nodes and Hubs joining and, perhaps moderators for
        each of the conference areas. If the volume of messages get
        to a certain point, it is difficult for one person to be
        able to monitor what is being entered and where. This is
        where a moderator comes in. One person volunteers to be the
        moderator for a specific conference. It would probably be
        that the sysops for each Hub would act as moderator for a
        number of conferences first and then, if the volume
        continues to increase, other moderators would be used and
        the number of conferences each individual is looking after
        would be reduced. Moderators are necessary to keep the
        conferences in some sort of order and on topic. They are
        not monitoring the conference(s) to act as God, they read
        the messages entered into their conferences to ensure that
        the messages are not flamming anyone or contains something
        like foul language or unsutable for family reading. It is
        a self policing method to keep things decent. They also
        would do what they could to keep a conference moving if
        they find that message traffic is slow or non-existent.

           The proceedure for adding a new Hub or Node to the
        Network is as follows:

        1. Either the local Hub sysop contacts a BBS sysop and asks
           if that person would be interested in joining TriLINK or,
           a BBS sysop contacts the Hub sysop requesting to join the
           network and draw mail from him.

        2. Once the "link" has been established and mail is being
           transferred between both systems, the Hub sysop enters
           the Nodes information - BBS Name, City, Prov. Telephone
           and BBS Sysop's Name into the TriLINK Network Admin.
           Conference. 

        3. When the HOST System for TriLINK receives this info in
           the TriLINK Administration Conference, the details will
           be added to the Trinode.lst file and the updated version
           will be placed in the TriLINK Files directory for
           downloading. 

        4. A message to EVERYONE will be placed in the TriLINK Admin.
           Conference to inform everyone a new updated node listing
           is available.


        Adding new conferences proceedure:


        1. If a user requests a node, or a Hub to add a new
           conference to the TriLINK conference listing then the
           node or the Hub receiving the request should post a
           message in the TriLINK Administration conference and
           enter the proposed Name of the new conference along with
           a description of what is to be contained/entered in that
           conference. Address message to: TRINET SYSOPS.

        2. Each node and Hub reading this conference (all systems
           who are paticipating in the TriLINK Network) will reply
           either yes or no to adding the new conference to the
           listing. If 50% (half) of the nodes and Hubs say "yes",
           the conference will be included in the conference list
           and added to the HOST systems message area. Other BBSs
           on the Network have the option of carrying the new
           conference or not. If less than 50% of the paticipating
           systems say "yes", then it will not be carried however,
           at some future time, when more nodes join the Network,
           the request can be made again following the same
           procedure. There is a chance this time that more than
           50% could say "yes". This seems to be a fair and 
           reasonable way to add new conferences.

        
        Removal of a Node or Hub procedure

        1. If a node or Hub on the system does not maintain a
           reasonable amount of control over its users and, does
           not monitor the messages entered by its users to ensure
           that they are in good taste, no foul language, and not
           written to bomb somebody (other than politicians of 
           course <grin>, then the Sysop can be brought to task by
           ANY OTHER SYSOP on the Network by simply entering a
           message in the TriLNK Administration conference saying
           what the problem is. The TriLINK Network belongs to
           everyone paticipating and if there is a problem with one
           or two areas then there has to be a method to resolve
           the problem.

        2. The offending sysop has the right to reply to the 
           charge, in a message, also in the TriLINK Administration
           message area. These messages will be addressed to the
           sysop and not made private. If, after several exchanges
           of messages between the alledged offender and the person
           who is filing the complaint the problem is not resolved,
           then the person complaining can request a SYSOP'S VOTE.

        3. The Sysop's Vote works the same as with adding new
           conferences. The message is posted calling the vote and,
           if 75% of the paticipating sysops vote "yes", the node
           or Hub is given a 30 day period to clean up its act. If
           after that period of time the problem continues, the node
           or Hub sysop's name is removed from the HOST system and
           the system to which it calls for messages.

        4. No other sysop participating in the TriLINK Network can
           allow a removed Hub or node to download messages from
           their BBS.

        5. After a period of six months, the removed node or Hub can
           request to its nearest Hub to be re-instated on the
           Network. A message should be left in the TriNET Admin.
           conference to the effect that the node or Hub is asking
           to be re-instated.

        6. Where a removed node or Hub has requested to be re-
           instated, another Sysop Vote is to be called. If 50% of
           the paticipating syops agree, the node or Hub will be
           reinstated otherwise they will not. There is no further
           provisons to be re-instated if 50% of the sysops say "no".
