Updated LM_NET Network Etiquette (fwd)

[Peter Milbury <pmilbur@EIS.CALSTATE.EDU>]

Dear LM_NET Colleagues,

Back again by popular request, the LM_NET Network Etiquette Guide.

>                    LM_NET NETWORK ETIQUETTE
>
>
>  When sending messages to a LM_NET, please keep the following
>  suggestions in mind.  They will help keep the group user-friendly
>  for everyone.
>
> 1.  Please include a subject line in each posting (it's a good
>     idea for ALL e-mail).
>
>     Note:  When sending commands to some listserv addresses, subject
>     lines should be left blank.  (i.e., listserv@some.site.edu)
>
> 2.  Keep each line in your message shorter than 70 characters.
>     Longer lines can cause problems with some e-mail systems. Check
>     your message for typos and other errors that make it hard to
>     read or understand.
>
>     Hot tip:  USING ALL CAPS IS CONSIDERED YELLING.  Save this style
>     for a special occasion.
>
> 3.  When replying to another message, try to refrain from
>     quoting entire messages.  Paraphrasing or quoting selectively
>     are both kinder to people's eyes and e-mail boxes and it is also
>     kinder to persons with CTS or tendonitis.
>
> 4.  At the end of your message, include your name and your
>     electronic mail address (this is your electronic "signature".)
>     Because it can be difficult to interpret e-mail addresses,
>     you are encouraged to include your institutional affiliation.
>
> 5.  Long signatures are discouraged. They may be humorous the
>     first time, but get old quickly (and take up valuable
>     net bandwidth and computer space). Some folks tire of
>     the time spent having to skim over them. 2-4 lines should
>     be sufficient to include any necessary information.
>
> 6.  Be _extremely_ careful when replying  to the author
>     of a list message.  Many e-mail systems will send your
>     reply to the entire list if you simply use a reply command.
>
>     NEVER post a reply message to the list which would not be
>     of interest to most members.  Just send it to the individual who
>     posted the original message to which you are responding
>
> 7.  Think before you post. Do I really want to say this to the
>     world (list)? Reread what you wrote. Did I really say what
>     I intended to? Once a message is sent, it can't be retrieved.
>
>     Should I send it to the individual, or to the entire group?
>
> 8.. Flames: a "flame" is an emotionally charged posting, and
>     is often directed at someone. Be sure you really want to
>     post it, and remember than some lists don't tolerate flames.
>
> 9.  To signal humorous intent, use some sort of "smiley",
>     such as :-).  Facetiousness and sarcasm can be misunderstood
>     easily in electronic communication.
>
> 10. Replies to requests for information. Some large lists have
>     a policy of sending information privately to the requester.
>     The requester then summarizes to the list. This can cut
>     down on traffic, but it tends to reduce the "give and take"
>     that some lists value.  See the LM_NET TARGET/HIT--> information
>     for the LM_NET policy.
>
> 11. Please be considerate of others.  Through inexperience or
>     limited local software, list members may inadvertently
>     violate the above suggestions.  A private message to the
>     offender from an experienced friend or from the list owners
>     is more appropriate than a public flame.
>
> 12. Please participate! Your ideas are important. Just because
>     you think everyone knows something doesn't mean they do.
>     If you're not sure, send the posting to an experienced friend
>     on the list (or the list owner) to see if the information
>     may be valuable.
>
> 13. LM_NET has its own character, just like any "real"
>     grouping of people (such as a party, or a meeting). The
>     list functions best when people respect the character
>     of the list. It's also good to respect the differences
>     among list members and have a certain tolerance for
>     our individual eccentricities.
>
> Especially for software producers and other vendors of products:
>
> 14. Producers should feel free to engage in general theoretical
>     discussions about the list topic, but should refrain
>     from turning their replies into commercials for their own
>     products.  Commercial messages are _not_ allowed unless first
>     approved by the list owners.
>
> 15. If a user posts the question "Does anyone have information
>     about program X?", the producer of program X should send
>     information directly to that person by e-mail rather than
>     posting the information to the list.  They may also post
>     a brief reply to the list saying that information has
>     been sent to the requester.
>
> 16. If a user posts the question "I'm looking for a program
>     that does X, Y, and Z", reply briefly to the list and
>     at greater length by e-mail directly to the individual.
>
> 17. Producers should avoid negative comments about their
>     competitors' products.
>
> If producers, or any list member, is unsure of the appropriateness
> of a message for the list, they are welcome to send it to one of the
> co-owners of the list first for review.
>
> The owner(s) will contact people who don't follow these guidelines.
> If people abuse the hospitality of this forum, they will be removed
> from the list.
>
>
> Mike Eisenberg and Peter Milbury
>