ADMIN: Elaboration on Posting Rules

["Eric J. Ray" <ejray -at- RAYCOMM -dot- COM>]

Gang,
Based on the messages so far this morning, I wasn't
adequately clear about the posting rules.

Read the rules before you post.

I've suspended one person's privileges so far this morning,
and am about to do the same to another. If you plan to
participate in this listserv list, you must follow the rules.
The key rule is that the messages must be about
technical communication.

Thus, a discussion about a technical writer and
the pros and cons of taking minutes on the job
is appropriate--it's about technical communication.
It matters not at all which side of the issue you
fall on--it's a potential occupational hazard or
benefit of this profession.
As soon as the discussion veers into gender issues,
sexism issues, or sarcastic diatribes about taking
phone messages, it's no longer about technical
communication and no longer appropriate.

If you're not sure, don't post.
If the connection isn't likely to be crystal clear to
all reading your post, explicitly state what the connection
to technical communication is.

If you don't understand part of the rules, ask me
and do not post until you understand.

Thanks!
Eric


POSTING RULES FOR TECHWR-L
     Revised 10/19/97

I strongly encourage everyone to read and understand these
rules before posting to TECHWR-L. Any list member may
be removed from the list, at the listowner's discretion,
for flagrant or repeated infractions. Additionally, if
you are abusive to the listowner or other list members,
you may be removed from the list.


     CHECK THE ARCHIVES BEFORE POSTING! Archives are available at
     http://www.documentation.com/techwrit/techwrit-l.htm
     and at http://listserv.okstate.edu/archives/techwr-l.html
     and at http://www.dejanews.com/ and at http://www.reference.com/.

     WHAT TO POST
     * If it is about technical communication and of general
       interest, post it.
     * If it is about technical communication and original and
       humorous, post it.

     WHAT NOT TO POST
     * If it doesn't clearly and directly relate to technical
       communication, don't post it.
     * If it relates to _language use_ but not technical
       communication, it probably isn't appropriate.
       Don't post it.
     * If it relates to _computer use_ but not technical
       communication, it probably isn't appropriate.
       Don't post it.
     * If it continues an irrelevant thread in any way
       (rebuttal, rebuke, rerun, revision, remark), don't
       post it.
     * If it is a personal message to a single subscriber,
       don't post it. Even if mail to that person bounces.
     * If you aren't sure, don't post it.
     * If it is something cute, interesting, or funny that
       you found on the Internet (e.g. Dr. Seuss on Tech
       Writing, origin of spam), don't post it. I assure
       you that most readers have seen it already.

     OTHER
     * Check your facts on anything you post. Do not under
       any circumstances post virus warnings or anything else
       designed to be "forwarded to everyone you know" to this
       list.
     * Do not directly attack anyone for anything on the list.
       Take issue with ideas, not personalities, and do
       NOT point out grammatical, spelling, or usage errors.
       This forum is not the place to exercise editorial
       frustration.
     * Please do post job ads -- they are welcome. Please
       put the location and general job description in the
       Subject line. E.g. something like
       JOB: Sr. Tech Writer, SF, California, USA.
     * Do not post job ad critiques. If you don't like the
       job, don't apply. If you have an issue with the
       terminology or phrasing, take it up off-line
       with the company.
     * Please do not post other ads in any form, for they are
       not welcome. The one exception is for ads that directly
       address a topic under discussion on the list. For example, if
       a reader posts a question about snazzling software and
       the company you work for makes Snazzler for Doors, posting
       information about the product would be fine.
     * Please make sure your E-mail address is included in
       the body of the message you post to the list.
     * If responses are sent to you--not to the whole list--please
       summarize and post the entire summary back to the list.
       A summary should include attributions so others can pick
       up conversations offline if necessary with original posters.
       When you send a summary back to the list, use the word
       "SUMMARY" as the first word of the "Subject" line."
     * Direct all commentary about this message to my
       address, not the list.





*********************************************************
* Eric J. Ray, ejray -at- raycomm -dot- com, http://www.raycomm.com/
* TECHWR-L Listowner, co-author _Mastering HTML 4.0_
*   _HTML 4 for Dummies Quick Reference_, and others.
* RayComm, Inc., currently accepting contract inquiries.