home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-386-Vol-2of3.iso
/
b
/
bbsnet2.zip
/
CONFRULE.ZIP
/
RIMECONF.RUL
< prev
Wrap
Text File
|
1992-04-02
|
14KB
|
289 lines
RIME Conferences
I. GENERAL RIME CONFERENCE RULES
*1. No illegal activities. Illegal activities, including promotion of
illegal acts and promotion of software copyright infringement, will
not be allowed in RIME.
*2. No offensive or abusive language. The use of any word, group of
words, expression, comment, suggestion, or proposal which is profane,
obscene, lewd, lascivious, filthy, indecent, or is ethnically,
sexually, or racially demeaning is strictly prohibited within RIME.
3. No abuse of other users. Do not abuse the other users of
this/these conference(s) by sending abusive, foul, or insulting
messages. No abuse of other users on the basis of character, physical
characteristics, religion, gender, sexual orientation, intelligence
quotient, or ethnicity is allowed. Messages meant to harass or bully
another user are not allowed.
4. Conference topics. Messages shall remain to the topic of the
conference.
5. Do not "over quote" messages. Quoting should be limited to only
enough to remind the original user of what was said or to provide for
an adequate response. Quoting should not need to be more than 20% of
the total message. Never quote tagline areas unless you are
discussing taglines.
BBS Ads are ONLY permitted in the BBS AD Conference. ForSale ads are
permitted only in the FORSALE conference, or where specifically
permitted by the Conference Host.
Messages containing ANSI codes are to be ONLY posted in the ANSI
Conference. No ANSI graphics may be used in any conference on the
network except the ANSI conference. Signatures may not exceed two
lines and may not contain any ANSI or other characters which interfere
with readers and BBS software. Quote symbols and quote boxes should
also not contain any characters which might interfere with readers and
BBS software.
6. Copying messages to other conferences and/or other users. No one
may copy, quote verbatim, or extensively quote from a message from one
issue-oriented conference to another without permission of the
originator of the message. In addition, retransmission of
public/private messages dealing with administrative matters to or by
anyone other than the user(s), Sysop, CH or SC member(s) involved is
considered grounds for disciplinary action and potential removal from
the network.
No copying messages from other networks without the specific
permission of the author of the message and/or the orginating network
whichever is appropriate.
7. Bombing the Net. Bombing the Network, or the practice of a user
generating multiple non-related messages for the purpose of disrupting
a conference or the Network is prohibited.
8. Misleading information. Messages that are specifically intended
to mislead and deceive are considered to be disruptive to a
conference.
9. Harassment. Messages meant to harass or bully another user are
not allowed.
10. Any and all of the rules that are part of the RIME Bylaws are
hereby incorporated here.
11. Differences of opinion. Differences of opinion that are over
these rules in a conference are to be discussed in the NETADMIN or the
USERS Conferences only. These differences may be discussed with the
Conference Host in the conference by R/O and/or Routed message only,
or with STEERCOM in the COMMON Conference by R/O message only
12. Any user or sysop threatening to involve Relaynet in a law suit
or legal battle, at the discretion of the CC or SC, may be removed
from the network.
13. No soliciting on the network without specific permission of the
Steering Committee
*Denotes direct quote from bylaws.
II. CONFERENCE MANAGEMENT
1. Establishing conferences.
a. Fifteen nodes--5 of which must be hubs--must agree to carry a
proposed conference. An individual who is acceptable to the CC must
be willing to act as Conference Host before the conference can be
activated. If all conditions are met, the CC will announce the
conference within 10 days. The SC reserves the right to review all
issues arising out of conference requests. Nodes which carry all RIME
Network conferences cannot be included in this node count.
b. RULES, PROCEDURES FOR PROPOSING A NEW CONFERENCE ON RIME
1) Send a message to the Conference Coordinator (James Wall Nodeid=
DREAM) in Common or Network Administration, stating that you would
like to start a conference. The following must be listed in this
initial message. A) NAME OF CONFERENCE. B) WHAT THE CONFERENCE WILL
EMCOMPASS. C) THE NAME OF THE PROPOSED CONFERENCE HOST.
2) Upon receipt of the message the Conference Coordinator will discuss
with the Steering Committee the feasibility of the conference and
will inform you if you may scout for participation in this
conference.
3) If permission is given to scout for participation, the Conference
Coordinator will so inform you.
A. The Conference Coordinator will assign to you a "Scout Number".
This number MUST be used on all messages from you requesting
participation in your proposed conference. Any message
requesting participation that does not contain this scout number
should not be answered. If an incorrect scout number is used
the Conference Coordinator or a Member of the Steering
Committee, will inform everyone that this is not an authorized
scout.
B. You are allowed to send out scout messages in 5 conferences of
your choice. You will inform the Conference Coordinator the 5
conferences in which you will be scouting.
C. You will then have the responsibility of acquiring the required
number of nodes and hubs that will guarantee that they will
carry this conference. At present the required number is 15
Nodes, 5 of which must be Hubs, with No node that carries all of
the conferences. PLEASE BE AWARE THAT EACH HUB HAS A NODE
DIRECTLY UNDER IT THAT IS THE SYSOPS BOARD. YOU "CANNOT" USE
BOTH THE HUB AND THE NODE IN YOUR COUNT! YOU MUST SELECT ONE OF
THESE WHICH WILL BE USED. (For example: HUBDC is a hub which has
as its node DREAM, which is the sysops board). You may use one
of these but not both. YOU "CANNOT" USE IN YOUR COUNT ANY NODE
THAT TAKES ALL OF THE PUBLIC CONFERENCES ON RIME. You should
make sure the sysop knows this when he guarantees his node. You
should save all confirmation messages sent to you, so that you
can later send them to the Conference Coordinator.
4) Once the required number of nodes and hubs has been obtained, you
should send a Private, Routed message to the Conference
Coordinator, listing the nodes and the hubs that have guaranteed
they will take the conference and the names of the sysops if each
node and hub. You must also at this time send to the Conference
Coordinator copies of all confirmation messages that have been sent
to you stating that the node or hub guarantees they will carry the
conference.
5) Once the Conference Coordinator has this information, the list will
be checked for accuracy and will be also checked to make sure all
requirements have been met. Another brief discussion between the
Conference Coordinator and the Steering Committee will ensue and
normally the conference will be entered on the next release of the
conference list. The Conference Coordinator will inform you as to
exactly when the conference will go up.
SUMMARY:RULES FOR SCOUTING FOR PARTICIPANTS
(A) Obtain Scout Number from James Wall of DREAM
(B) Pick 5 Conferences, you may only advertise your new conference
proposal in these 5 conferences.
(C) You may post (1) advertisement message per week for (4) weeks in
your (5) conferences.
(D) You may always feel free to answer questions or requests concerning
your conference proposal, but this must be a dialog, not another
advertisement.
(E) If you do not have the required number of Nodes and Hubs in the
(4) weeks allocated, you may not post again. You may request this
conference again in (4) months.
THE CONFERENCE COORDINATOR IS JAMES WALL
HIS NODEID (IDCODE) IS DREAM
b.The SC reserves the right to establish specialized conferences,
such as vendor support conferences, announced through the CC.
2. Removal of conferences. The CC will monitor on a monthly basis
conference activity using reports generated by the NETHUB. Conferences
that do not meet established activity criteria will be subject to
discontinuation the CC.
3. Conference Hosts are designated by the CC. Conference Co-hosts
can only be assigned with the advanced consent of the CC; Conference
Hosts can only recommend and cannot appoint Co-hosts directly.
4. RIME Conference Host Responsibilities:
a. Check the contents of your conference frequently. If you
must be out of town or unable to access your conference for more than
three days, notify the Conference Coordinator so that arrangements can
be made in advance to cover the conference during your absence.
b. Make every effort to see that users of the conference will
keep to the topics that are the goal of your conference. Help to
stimulate conversation to benefit all users of the conference.
c. If users are introducing topics that do not relate to the
conference topic, note to them in a cordial fashion that their post is
not appropriate to the conference topic and suggest another conference
where they might continue their discussion and/or query.
d. Be able to answer general questions about the network and how
to make the most of it. Answer questions regarding the privacy of
messages on the network, how to route messages, and how to set up
private mailboxes.
e. Inform the conference users of whom they should contact in
the event of a problem in the conference. This includes making
yourself visible as the first person to contact in such an event.
III. CONFERENCE PROBLEM SOLVING
1. Steps in Handling Problems in RIME Conference
a. If a problem exists, the Conference Host shall approach the
user in his/her most courteous fashion and ask the user to review the
rules of the conference and/or network and to please abide by them.
This initial message should be R/O and routed if possible, however,
the Conference Host may elect to address the problem in a general
public message in the conference. Depending on the severity of the
matter and how quickly the problem develops, it may be appropriate to
notify the Conference Coordinator of RIME of the impending problem so
that he/she may be abreast of the situation and follow the contents of
your conference.
b. The second step is to contact the SysOp of the board from
where the user's messages are originating and respectfully ask for
their cooperation/aid in handling the problem. If the Conference Host
does not know the name of the Sysop, he or she should send a Routed
NETWORK SYSOP message to the ID CODE of the board. COMMON is the best
place to handle any administrative issues you are bringing to a sysops
attention. Please send this message routed.
c. The third step (if the first two have not been successful) is
to ask for direct intervention by the Conference Coordinator/SC to
bring the problem situation to a close.
d. The fourth (and final) step is to consult the Steering
Committee for final guidance in addressing the matter. In most
instances, step 1 is sufficient to handle most user problems.
e. Conference Hosts serve at the discretion of the CC and SC and
are subject to the same rules of decorum and conduct as all other
users.
f. All node SysOps are expected to adhere to the highest
standards of decorum and courtesy in their conference usage and
participation. Of course, all node Sysops are subject to SC
accountability.
2. Disciplinary Action. Any suspensions or removals from the network
may only be performed by the SC.
a. First offense. The user may be warned. Warnings should be
brought to the attention of the CC.
b. Second offense. The user is subject to removal from the
conference(s) for a minimum of ten days.
c. Third offense. The user is subject to removal from the
conference(s), or the network if appropriate, for a minimum of thirty
days.
d. Fourth offense. The user is subject to removal from the
conference(s), or the network if appropriate, permanently or until the
SC declares otherwise.
e. Appeals can be made R/O to STEERCOM in the COMMON Conference,
by public or R/O message in the Users Conference, or by voice.
f. Sysops always have the discretion to remove their own users
at any time.
2. Emergency measures:
a. A CH in a conference where there has been flagrant disregard
of all rules of common sense to the point of conference disruption,
may suspend a participant in the conference immediately for a period
of 10 days.
b. Upon suspension the CH must immediately notify at least two of
the following persons:
Paul Hileman - Conference Coordinator (NODE ID BAYOU)
Bonnie Anthony - CEO (NODE ID RUNNINGA)
Sysop of the board that the user messages from.
c. Immediate suspension is considered a grave event and should
not be undertaken lightly.