home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Crawly Crypt Collection 2
/
crawlyvol2.bin
/
apps
/
bbs
/
nest_kit
/
neststrc
/
neststrc.006
Wrap
Text File
|
1994-08-03
|
14KB
|
405 lines
__ ¯¯//\ //| // ////// ////// //////
// /\ // | // // // //tm
// \/\ // 9|0 // //// ////// //
\\ * / // | // // // //
\\ / _ // | // // // //
\\/__ // |// ////// ////// //
NeST Structure. (Issue 005 - 03/08/94)
---------------
Index.......... 1) Hierachy.
2) Tasks.
2) Voting.
3) Positions.
1) HIERACHY.
============
* Zone Coordinator
| ----------------
| (NeST Central Control - coordinates Zone 90)
|
* World Echo Coordinator
| ----------------------
| (Controls the EchoMail distribution and Moderators, appoints new
| Echo areas and issues the NeST EchoMail document)
|
* World File Echo Coordinator
| ---------------------------
| (Controls the FileEchos distribution, appoints new FileEcho areas
| and issues the NeST FileEcho document)
|
* Space Empire Coordinator
| ------------------------
| (Controls all aspects of the Space Empire Elite on-line game)
|
* Software Coordinator
| --------------------
| (Controls Software details and updates)
|
*
/ \
/ \
* Regional Coordinators (Coordinate a national Region)
|
*
/ \
/ \
* Host Coordinators (Coordinate a local Net)
|
*
/ \
/ \
* Hub Systems (Coordinate a local area Hub)
|
*
/ \
/ \
* Nodes (All public or private BBSs; each single SysOp)
|
*
/ \
/ \
* Points (Single-user Automated Mailing Systems)
If a system has a problem that is not covered by a designated person of
authority, the problem should be 'bounced' upwards through the network
structure.
ZONE COORDINATOR
================
The Zone Coordinator (ZC) is responsible for enforcing policy, and
moderating disagreements between Regional Coordinators (RC).
The ZCs tasks are to:
a) Create new Regional Coordinators.
b) Recommend the creation of new Host Coordinators.
c) Issue/update copies of the NeST documents, including the master
NeSTlist.
d) Issue NeST documents to Regional Coordinators.
e) Remove Regional Coordinators at the request of that Region's
Host systems, if the RC is found to be unsuitable.
f) Veto decisions taken by a lower level Coordinator, if found not
suitable for the Network's benefit.
WORLD ECHO COORDINATOR
======================
The World Echo Coordinator (WEC) is responsible for:
a) Keeping record of what NeST Echos are available within the Network,
from which Region/Host/Hub systems they are available, and advise
the best international links for the most efficient EchoMail
distribution.
b) Liasing with the ZC concerning matters of World NeST Echo Policy.
b) Updating the NeSTEcho List on a regular basis, incorporating all the
existing EchoMail conferences, and a list of new Echos that members
wish to propose.
c) The logging and storage of the rules for each individual NeST Echo,
written and updated by each Echo Moderator. The rules should be kept
in a special download area, and made available for F/Req'ing.
A default set of echo rules should be maintained for Echos which do
not need any special rules.
WORLD FILE ECHO COORDINATOR
===========================
The World FileEcho Coordinator (FEC) is responsible for:
a) Keeping record of what Tick FileEchos are available within the
Network, from which Region/Host/Hub systems they are available, and
advise the best international links for the most efficient FileEcho
distribution.
b) Liasing with the ZC concerning matters of NeST FileEcho
distribution.
c) Updating the NeSTFile List on a regular basis, incorporating all the
existing FileEcho areas, and a list of new areas that members wish
to propose.
SPACE EMPIRE COORDINATOR
========================
The Space Empire Coordinator (SEC) is responsible for:
a) Ensuring that all systems playing Space Empire Elite (SEE) are using
the same version of the program.
b) Ensuring all systems are active in the game.
c) Ensuring via SEE_FIDO.TOS that the SEE GALAXY.DAT files are updated.
d) Deciding when game resets should take place.
e) Moderating the N_SEE Echo.
f) Distributing SEE files via the 90_SEE File Echo.
SOFTWARE COORDINATOR
====================
The Software Coordinator (SC) is responsible for:
a) Keeping a log of what software is written within NeST, and keeping
track of version numbers.
b) Distributing the NESTSOFT.xxx document in the 90_NEST file echo,
which will detail the software information.
REGION COORDINATOR
==================
The Region Coordinator (RC) is responsible for insuring links, enforcing
policy, and moderating disagreements between Host Coordinators (HC).
The RC has the task to:
a) Insure the correct gatewaying of NetMail, EchoMail and FileEchos
to/form his/her Region and others, and inside of it.
b) Create new Host Coordinators, and ensure that the appointed Hosts
conform to policy.
c) Ensure that updated copies of NeST documents are circulated to Host
systems under his/her control.
d) Remove Host Coordinators at the request of that Host's Hub systems,
if the HC is found to be unsuitable.
e) Update the NeSTList with respect to his/her region. This information
must be forwarded regularly to the ZC.
f) Updating NeST Topology with respect to his/her region. This
information must be forwarded regularly to the TC.
HOST CONTROLLER
===============
The Host Coordinator (HC) is responsible for ensuring links, enforcing
policy, and moderating disagreements between Hub Systems (HS).
The HC has the responsibility to:
a) Insure the correct gatewaying of NetMail, EchoMail and FileEchs
to/form its net and others, and inside of it.
b) Create new Hub Systems, and ensure that the appointed Hubs conform
to the policies.
c) Ensure that updated copies of NeST documents are circulated to Hub
Systems under his/her control.
d) Remove Hub Coordinators at the request of that Hub's BBS systems, if
the HS is found to be unsuitable.
e) Updating the NeSTList with respect to his/her net.
This information must be forwarded regularly to the RC for that
Region.
f) Updating NeST Topology with respect to his/her net. This information
must be forwarded regularly to the RC.
HUB SYSTEM
==========
The Hub System (HS) is responsible for ensuring links, enforcing policy,
and should help out individual sysops with NeST problems.
The HS has the responsibility to:
a) Insure the correct gatewaying of NetMail, EchoMail and FileEchs
to/form its Hub and others, and inside of it.
b) Ensure updated copies of NeST documents are circulated to BBS
Systems under his/her control.
d) Updating the NeSTList with respect to his/her Hub.
This information must be given regularly to the HC for that Hub.
SYSOP
=====
The SysOp of course is responsible for his/her own bulletin board, and
should ensure that NeST Mail is kept distinct from other Fido Technology
mail. That duplications of messages, or problems with corrupted message
areas do not take place.
The SysOp should also try to ensure that no messages or files of an
illegal nature originate from his or her system.
POINT
=====
Points should ensure that there are no technical problems with messages
originating from them, and that no messages or files of an illegal nature
originate from his or her system.
2. OTHER NON HEIRACHIAL POSITIONS.
==================================
ECHO MODERATOR.
===============
The echo moderator is responsible for the following:
a) Naming his/her echo, in accordance with the echo naming
guidelines set out in the NeST Policy Document.
b) Posting a copy of the echo rules into the echo on a monthly, or
bi-monthly basis, depending on mail traffic.
c) Ensuring that messages sent witin the echo follow the echo rules
and do not contravene NeST Policy.
d) The echo moderator should also state in the rules any
restrictions concerning echo distribution. These restrictions
may include:
1) World Distribution (compulsary).
2) World Distribution.
3) Regional Distribution only.
3) Regional Distribution only (compulsary).
4) Net Distribution only.
5) Net Distribution only (compulsary).
5) Restricted Distribution - for beta testers.
- programing teams.
- closed user groups.
e) Ensuring an up to date copy of the echo rules are given to
the WEC.
3. VOTING.
==========
The 'vote' system of reaching decisions will be applied to:
a) Removing a NeST BBS from the network, if they are found to be acting
against NeST's interests.
b) Reprimanding a system for irresponsible behaviour.
c) Granting a BBS system Hub status. Voting would take place within
the local Host system only. It is a faculty of the Host/Region
Coordinator to call for SysOp votes in such an occurrnce.
d) Installing a new TC, WEC, WFC, SEC, RC, HC, HS, at the discretion
of the ZC, via votes taken from each system appearing in the
NeSTList (see below).
3. POSITIONS.
=============
Zone Coordinator = Position held for an undefined period.
The ultimate authority in NeST until the occasion
arises when other ZONES would become active.
If the ZC resigns, he will appoint a sucessor to
take up the position. The new ZC must be found
acceptable by the RCs before the appointment
commences.
Topology Coordinator = Position held for an undefined period.
The TC can be removed by the ZC. If the TC
resigns, a new TC will be appointed by the ZC via
a vote system.
World Echo Coordinator = Position held for an undefined period.
The WEC can be removed by the ZC. If the WEC
resigns, a new WEC will be appointed by the ZC
via a vote system.
World FileEcho Coord. = Position held for an undefined period.
The WFC can be removed by the ZC. If the WFC
resigns, a new WFC will be appointed by the ZC
via a vote system.
World Gateway Coord. = Position held for an undefined period.
The WGC can be removed by the ZC. If the WGC
resigns a new WGC will be appointed by the ZC
via a vote system.
Space Empire Coord. = Position held for an undefined period.
The SEC can be removed by the ZC. If the SEC
resigns, a new SEC will be appointed by the ZC
via a vote system.
Regional Coordinator = Position held for an undefined period.
An RC can be removed by the ZC. If an RC
resigns, a new RC will be appointed by the
Regional members concerned and the ZC, via a
vote system.
Host Coordinator = Position held for an undefined period.
A HC can be removed by the RC. If a HC resigns,
a new HC will be appointed by the RC and ZC
along with the members of that Net via a vote
system.
Hub System = Position held for an undefined period.
A HS can be removed by the HC. If a HS resigns,
a new HS will be appointed jointly by the HC
and RC, via a vote system.
Note that voting will be based on one vote per system appearing in the
NeSTList. Votes for each Net or Region will be held only by members of that
Net or Region, votes for any Coordinators position will be taken from all
Nets/Regions. The ZC reserves the right to over ride any vote for the
following reasons:
a) The person elected is not capable of carrying out the workload of the
position.
b) The person elected would not look after the best interests of NeST.
c) The person elected would not be suitable to the world members of NeST.
d) The person elected will not cooperate with other Coordinators.
e) The person elected would cause political problems within the
network itself.
(C)1993 Daron Brewood [NeST Zone Coordinator]