Path: intern1.nntp.aus1.giganews.com!internal1.nntp.ash.giganews.com!border2.nntp.ash.giganews.com!border1.nntp.ash.giganews.com!nntp.giganews.com!newsfeed.tpinternet.pl!news.atman.pl!news.intercom.pl!f124.n480!f127.n480!f112.n480!f200.n2432!f605.n774!f500.n123!f2000.n106!f1.n140!f6018.n106!not-for-mail
Newsgroups: fido.unix
Distribution: fido
From: Moderator
Date: Sun, 01 Feb 04 03:50:54 +0100
Subject: UNIX Echo Guidelines (rev. 5/1/01)
Message-ID:
Organization: The Enchanted Forest * Houston, Texas
200
2450/501
Lines: 84
Xref: intern1.nntp.aus1.giganews.com fido.unix:71
==========================================================================
I N T E R N A T I O N A L F I D O N E T U N I X C O N F E R E N C E
==========================================================================
G U I D E L I N E S
(1) All messages from me in my capacity as moderator will contain my
"Moderator" signature with date and time of creation or indicate
that status with a 'From: Moderator' heading.
(2) All discussions relating to the installation, operation, and support
of the Linux Operating System or applications of a Linux-specific
port should be directed to the LINUX echo or LINUX-USER echo.
Discussions pertaining to the comparision of Linux with various
flavors of Unix are permitted, provided the discussion does not
degenerate in to a 'How do I do this?' situation.
(3) We are all professionals, and as such, should behave accordingly.
Although I encourage debate on appropriate subjects, please refrain
from anything that remotely resembles a personal attack upon another
person's character. Stick to the facts/opinions.
(4) The official language of Fidonet is English. I recognize that we
do have a significant contingent of foreign participants; however
the non-English speaking participants should also recognize that
non-English posts are quite likely to result in a reduced response
rate, therefore the use of English is encouraged.
(5) Commercial advertising is prohibited, although informational postings
of product or service availability may be allowed, provided that the
announcement does not appear to result in commercial gain of the poster
or his/her associates, and the product or service is related to the
Unix Operating System. These type of postings must be limited to
one message and one posting.
(6) Posting of multi-part listings take up extra disk space and transfer
time, and may not be of interest to all readers. It is preferred that
'lists' be offered as a text file for File Request. If a user believes
that the echo would benefit from the posting of the list, the list
should be netmailed to the moderator for approval prior to posting.
(7) All notifications of rules violations and other rules discussions will
take place via netmail. Rules violations will be crash netmailed to the
participant and host sysop. Requests for cooperation posted in the echo
are not to be construed as "notifications" for purposes of Rule 8. All
participants must be capable of receiving crash netmail on the BBS that
they post from. Check with your sysop, if you are unsure of the availa-
bility. Sysops who do not provide an -inbound- netmail service to their
users, will have this echo restricted from their system.
(8) (a) The first notification of a rules violation will assume the
violator was unfamiliar with the rules, although -all- participants
are responsible for knowing and understanding the rules. As such,
the first notification is intended to be -informational- only.
(b) The second notification of violation of the -same- rule will be
considered a warning. Only one warning will be issued per specific
violation.
(c) A third violation will result in the participant's access and/or
sysop's feed being restricted.
(9) There are no restrictions in this echo on public key encrypted signature
blocks.
(10) There are no restrictions on 8-bit characters. This is an International
Echo, and as such has an obligation to support the necessary use of
international character sets. However, abuse of the International
Character Set for artistic purposes is not appropriate.
(11) There are no restrictions on signature blocks; however, in consideration
of those systems that do not receive their feeds on a fixed fee or
costsharing basis, please keep them to a minimum.
(12) Real names are required. If it is not contained within the header of
the message, then it should be included as a signature line.
==========================================================================
Last Revision: 5/1/2001
Summary of changes:
Removed references in (9) to BOFAQ.
Lawrence Garvin, lawrence@eforest.net
Moderator, International Fidonet Unix Conference
--- SendMsg/2
|