home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR21
/
TAP_0294.ZIP
/
RULES.TAP
< prev
next >
Wrap
Text File
|
1994-01-29
|
11KB
|
200 lines
TAP-Net (tm)
Technical and Programmers E-Mail Network
POLICY-1, Rev 6/93
System Coordinator: Thom Allen
TAP-Net Home System: Home Line BBS
801-569-3261
801-569-0099 10pm-7am
FIDO 1:311/27
Internet rn.6431@rose.com
Associate Coordinator: **
International Coordinator: **
Files Distribution Coordinator: **
Marketing Director: **
Public Relations: **
Senior Moderator: **
I. Mission Statement:
The mission of this network is to combine all areas of the computer world
into the largest single information network available. Interests will
include all computer platforms, OS's, machines and companies. Our goal
to bring information to all levels of users and to introduce the cutting
edge of technology.
II. Network Layout:
The layout of the network will consist of several layers of smaller
networks, making up the wide or whole body. The Central Network System
(CNS) will be located in Salt Lake City, Utah, USA. All information, except
that which is CRASHED or directly routed, will reside on the central
system. There will be several Regional Network Systems, (RNS), that will
control information flow to the CNS from its network systems. Within the
RNS, there will be local HUBS, that will act as a distribution point for
local systems, lowering the costs. Cost sharing is highly recommended.
CNS
|
_____________________________|________________________________
| | | | | | |
RNS-1 FDC-1 RNS-2 RNS-3 RNS-4 RNS-5 RNS-6
| | | | | |
--HUB-1 --HUB-1 --HUB-1 --HUB-1 --HUB-1 --HUB1
| | | |
--HUB-2 --HUB-2 --HUB-2 --HUB-2
| |
--HUB-3 --HUB-3
We will also have several File Distribution Networks, (FDC). These are
voluntary and will be up to the individual systems if they are to
participate. We will need 1 system to act as the FDC, which maintains
the active files available. All HUBS or individual systems will be
responsible for obtaining the files from the FDC at there own cost. If
an RNS or a HUB request to maintain a file point on there system, they
will have to obtain them from the FDC. No routed mail will go through
the FDC, but will have to notify the network as a whole of all new
additions to the library of files. The file system will be broken down
into several catagories, and for several computer types. More will be
added as requested.
There will be a public conference for the purpose of requesting addendums
to or changes of the network POLICY. This will not be a debate conference
and all information is non-binding, and no expressed desire to include
or change the POLICY. The POLICY will only be updated by an 2/3 or more
positive vote from the board of directors. This vote will take place once
a quarter, unless a special session is called for an immediate vote.
III. Responsabilities:
The responsability of the CNS, is to maintain the over all operations of the
network, in conjunction with the other advisors. The CNS will be responsable
for making sure that the network is running smooth, there is little or no
down time, all rules are followed, and our mission statment is being
fullfilled, review all applications for admittance, and other duties as they
become necessary.
The responsability of the Assistant Coordinator will be to take over when the
CNS is unavailable, having the same authority when acting in his/her place.
The ACNS will advise and help in the day to day operation of the net.
The responsability of the International Coordinator, is to market the network
in all countries, and to act as a lieason for those countries. Setting up
RNS and FDC's if requested for the Internation callers. There may be several
people in these positions depending on how much activity we get.
The responsability of the Files Distribution Coordinator, will be to maintain
and update the FILES library for the network. To make available all files
that are requested, and to inform all users via the network of new additions,
and about those that will be in our archives. This job will take alot of
time to do updates, and will not be a message point, so they will have to get
mail on there own, or local HUB.
The responsabiltiy of the Marketing Director is to recruit as many BBS
and non-BBS operators as possible. Large and small BBS's, corporate and
small business. To get Software and Hardware vendors of all types to have
a support conference available and a staffer for it. To possibly recruit
financial backers, sponsors, or to get FREE advertising when available.
The responsability of the Public Relations Director will be to give our
network the recognition that it will need. Flyers, Newsletter, contests
advetising, budgeting, sponsorship, and the other accounting type needs.
The responsability of the Senior Moderator will be to recruit moderators
for all our conferences, to make sure that all current moderators are doing
the prescribed job, and that all complaints are investigated. The Senior
Moderator will be in charge of the Moderators and POLICY conferences.
This person will work closely with the CNS, to make sure things are running
smooth.
IV. Disciplinay Actions:
All disciplinary action will be handled in the Coordinators conference.
All grievences will be forwarded to the Coordinators conference via the
RNS's. After reviewing the complaints an action will be taken, and then
sent back down through the RNS. All complaintants will be allowed 1 (ONE)
appeal, which then the complaintant will be able to get as many supporters
for his cause, to give more insight as to making the descision on the appeal.
Once the descision on the appeal his made, no other action will be taken
on the matter. RNS's local users will be resonsible to their HUBS or RNS's,
and HUBS to their RNS's. The RNS's will be responsible to the CNS, and all
coordinators will be responsible to the CNS. We will update this section as
needed.
V. Mail Transfers:
The mail transfered on this system will be in either the FIDO or QWK style
mail formats. FIDO systems will have to have registerd version of all
software where applicable. All RNS's will have to have the FIDO and QWK
mail types on their systems, in order to handle all mail types. The HUBS
may choose the FIDO or the QWK type mail. The CNS will have both the FIDO
and the QWK mail available. We may add other mail transfer types in the
future. If your QWK mailer is not compatible with your HUBS or RNS, you will
have to transfer mail via the FIDO system, which is compatible on all
machine types. We will maintain our own nodelist, and it will be updated
every Thursday, unless no changes have been made. Every HUB, RNS and the CNS
will have assigned address, and these must appear in ever message so that we
know where traffic is comming from.
VI. Conferences:
You will find a file accompanying this one, that indicates all the available
conferences on the network. Conferences my be added or deleted, all users
will be notified in advance of the action. There will need to be at least 3
seperate individuales that request a conference in order for it to be
considered. We will update the conference listing each quarter along with the
POLICY statment, or sooner as may be needed. Companies that request a
support conference on the network need to provide a FAQ sheet about their
product or service, and that a staff member be assigned to assist with
the conference. All conferences that have 0-10 messages for a period of
6 months will be reviewed for deletion. This descision will be by the
coordinators, and no vote will be taken.
VII. Costs:
All costs incured by anyone associated with the net are of their own expence.
If at a later date, it is decided that a fee needs to be charged to maintain
the network operations, everyone will have the ability to express their
opinion. As of this writting, donations will be accepted to help maintain the
network, and keep our visibility high. In order to run a net of this
magnitude, donations will be the determining factor on the chances of
charging a fee. With everyones cooperation we can make tis net succeed.
VIII. Requirements For RNS/HUB Status:
In order for a BBS systems to be concidered for an Regional Network System,
the BBS must have been in operation for at least 1 year, file bases should
have technical or programming oriented files, and have a minimum 14,400 baud
modem. If an RNS has only one incomming line, and the traffic becomes more
than it can handle with one line, another RNS may be selected or the current
RNS may need to expand it's system. Must be a member of the FIDO network with
a valid address, and registered QWK mailer for their BBS software.
In order for a BBS system to be concidered for a local HUB, the BBS must have
been in operation for at least 6 months. BBS Theme should have something
to do with programming or technical aspects. Must have a minimum of 9600 baud
modem capabilities, must have a registered QWK mailer for their BBS software
or be a member of the FIDO network with a valid address.
There will be 1 (one) RNS for every 5 (five) HUBS in an area. There will be
only 1 (one) HUB per area code, or non-toll areas, unless it is physically
impossible to handle the local nodes that are participating, then there will
be one HUB per 10 local nodes. If the need arises to have what we will refere
to as a SUPER REGIONAL system, to help eleviate the message traffic for the
RNS's, there will be a MAX of 2 SUPER REGIONAL systems on this network.
For RNS's residing in the same area code as a HUB, the HUB may elect to call
anothe RNS for the purpose of keeping costs down. There will be no RNS in the
801 area code, a HUB will be assigned to retrieve mail directly from the HOST
system.
IX. Catch all:
This clause handles all problems that may arise on the network not coverd
by a previous statment. These problems will be handled by the CNS and the
coordinators.