home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Crawly Crypt Collection 2
/
crawlyvol2.bin
/
apps
/
bbs
/
nest_kit
/
nesteply
/
echopoly.003
next >
Wrap
Text File
|
1994-08-01
|
8KB
|
244 lines
--=//\ //| // ////// ////// //////
// /\ // | // /
// \/\ // 9|0 // //// ////// //
\\ * / // | // // // //
\\ / _ // | // // // //
\\/ _ // |// ////// ////// //
Network ST - NeST Echomail Rules - Issue 03 (Mon Aug 1st 1994)
==============================================================
by NeST WEC Flemming Nielsen (90:90/900)
###########################################################################
[1.0] NeST Echomail definition
[1.1] - Echomail discussions
[2.0] General NeST Echomail rules
[3.0] Proposing a new echo.
[3.1] - Who can propose an echo.
[3.2] - PROPOSAL.003 (Proposal form)
[3.3] - Echo naming
[4.0] Voting for a new echo.
[4.1] - Who can vote.
[4.2] - Possible votes
[4.3] - Voting periode
[4.4] - How to vote.
[5.0] Result of the vote
[5.1] - RESULT.003 (Result form)
[5.2] - Requirement for opening the echo.
[5.3] - Exceptions
[5.4] - Backboned echoes
[6.0] Echo details (Moderator/Rules/ect.)
[6.1] - Moderator
[6.2] - Echo rules
[6.3] - Echo info
[6.4] - Moderator resignation
[7.0] Deletion of echos
[7.1] - Lack of trafic
[7.2] - Lack of Author support (N.SUP.*)
[7.3] - N.ADM.* & N.NET.*
[8.0] Regional echoes
[8.1] - Voting
[8.2] - Rules
[8.3] - Backboned
[1.0] NeST Echomail definition
All echomail transfered with a 90:* address are concidered NeST echos
and must comply with this document and the current NEST-POLICY
(NESTPOLY.???) document.
For specifics concerning regional echoes, see [8]
[1.1] - Echomail discussions
All discussions concerning echomail should be directed to N.ADM.ECHO.
These discussions include: creating new echoes, removing echoes,
echo moderation, echo gating, echo rules and echo policy decisions.
This echo is moderated by the NeST World Echo Coordinator (WEC) 90:90/900
[2.0] General NeST Echomail rules
(see NESTPOLY.???)
[3.0] Proposing a new echo.
[3.1] - Who can propose an echo.
All members of NeST having an entry in the current NeSTList can
propose a new echo.
[3.2] - PROPOSAL.003 (Proposal form)
This form is used to propose a new echo and to call for votes on the
creation of this echo. The form must be posted in N.ADM.ECHO.
Post this form at the start of the voting period and then once a week
adding all valid votes until the vote ends.
The subject line should be: Vote for ECHONAME
where ECHONAME is the name of the proposed echo.
[3.3] - Echo naming
It would be a good idea to check the name with the WEC to ensure that
the NeST echo structure is maintained. The WEC reserves the right to
override any name not fitting in the structure or that in any way
contrevenes NESTPOLY.???.
Current structure:
N.ADM.* Administrational echos
N.NET.* Network business echos
N.NET.NOTICE.* Network Notice subdivision
N.MISC.* Miscellaneous topic echos
N.ST.* Atari ST(e)/TT/Falcon echos
N.ST.GAMES.* Atari Games subdivision
N.ST.PROG.* Atari Programming subdivision
N.FALCON.* Atari Falcon echos
N.SUP.* Support echos
N.SUP.BETA.* Beta support echos
Regional structure:
N.UK.* UK specific
N.GER.* Germany specific
N.ITA.* Italian specific
N.SCA.* Scandinavian specific
N.GR.* Greek specific
[4.0] Voting for a new echo.
[4.1] - Who can vote.
The members of NeST at the time of the motion are each entitled
to one vote per member. Nobody is required to vote. For the vote
to be considered the SysOp must have an entry in the NeSTList given
in the proposal. If a SysOp has more than one NeSTList entry they
will still only be allowed one vote.
[4.2] - Possible votes
Possible votes are "YES" (install area), "NO" or "ABSTAIN".
[4.3] - Voting periode
The voting period is one month.
The given final date means, all votes arriving at the vote-takers system
before or on final date 11:59pm local time are valid. All votes that
arrive later are invalid and will not be counted.
[4.4] - How to vote.
The vote will be taken via the N.ADM.ECHO echo. (see the proposal form)
[5.0] Result of the vote
[5.1] - RESULT.003 (Result form)
This form is used to post a vote result in N.ADM.ECHO.
The results must be posted one day after the vote is finished with all
votes publicly listed.
The subject line should be: Result of vote for ECHONAME
where ECHONAME is the name of the proposed echo.
[5.2] - Requirement for opening the echo.
A majority of at least ten (10) votes and 2/3 of all given votes must
be FOR the proposal for the motion to be granted and the echo opened.
[5.3] - Exceptions
All NeST Coordinators 90:90/* can setup administrational echos, without
any voting.
In urgent cases, you can crash mail the WEC to get permission to install
a specific echo without the normal procedure.
All other requirements still apply. Specificaly [6].
[5.4] - Backboned echoes
If the echo is opened and backboned, the echo must be made available
from all 90:*/0 systems.
Note: If a backboned echo is _not_ compulsory and neither the 90:*/0
system nor any node under it wants the echo, then that 90:*/0 system
is _not_ required to take it. If one or more nodes want it, the 90:*/0
system _must_ take it.
[6.0] Echo details (Moderator/Rules/ect.)
All NeST echos (and echos gated to NeST) should have a NeST moderator.
[6.1] - Moderator
The echo proposor will automaticaly become the echo moderator,
unless the proposer elects someone else.
[6.2] - Echo rules
The moderator must maintain and post the echo rules in the echo once
every month. (see NESTPOLY.???)
A copy of the rules must be sent to the WEC by netmail when the echo
is created & whenever the rules change.
[6.3] - Echo info
The following info must also be netmailed to WEC when a new echo is
created or any of the info is changed:
--+-----
Echoname :
Moderator Name :
Moderator Addr :
Backboned (Available at 90:*/0) :
Regional echo (Available region):
Gated with (echo, addr of gate) :
Handles allowed :
Access level (All,nodes,coord,.):
Short Description (max 40 chars):
Long Description (max 5 lines) :
--+-----
[6.4] - Moderator resignation
A moderator wishing to resign should normaly try and find a replacment.
[7.0] Deletion of echos
[7.1] - Lack of trafic
Echos can be deleted due to lack of trafic.
The echos are divided into two catagories for minimum trafic definitions:
N.SUP.* : 4 messages/month.
The rest: 15 messages/month.
A message will be posted to an area if the minimum is not reached in
the past month, stating that the area is under the minimum trafic limit.
(This message is _not_ counted)
If an echo has less than the minimum for 3 consecutive months, the echo
will be removed from the backbone.
[7.2] - Lack of Author support (N.SUP.*)
Software support echoes should normaly have the software author as
participant, and the software should be under continued development.
[7.3] - N.ADM.* & N.NET.*
These echos are fundamental to the network and can only be deleted if
agreed upon by NeST coordinators.
[8.0] Regional echoes
Exceptions from the above for regional echoes.
Note, that all above rules apply, unless explicitly excepted here.
Regional rules must comply with NESTPOLY.???.
[8.1] - Voting
Regional echos are only to be voted on in the region the echo is to be
made available. Voting for and discussions about regional echos should
not normaly be done in the international N.ADM.ECHO.
[8.2] - Rules
The exact voting rules and requirements for regional echoes are decided
upon in the region. These rules should normaly follow the international
rules if possable.
Valid exceptions are the minimum 10 node majority in a 5 node region,
and simular.
These rules (in english) should be forwarded to the WEC.
The WEC can overrule these rules, should it be deemed nessesary.
[8.3] - Backboned
Backboned regional echoes must be made available from all hosts and
above in the region.