ADMIN: Posting Rules Reminder (was Re: Does anyone need this book on the C programming language?)

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

>I post this at the risk of being off-topic and having Eric ban me
>from TECHWR-L.  If it is off topic, please hold the
>flames, as I'm sure I'll be in enough hot water with the list
>administrator. 8-).

Just as an FYI for everyone, as I periodically get emails
wondering "why didn't you do something about ...",
I've revoked this subscriber's posting privileges.
Generally, I don't announce off-line warnings or administrative
sanctions, but this seems to call for a comment.

This subscriber's latest message testing the administrators will to
administrate comes on top of several off-line discussions
about appropriate postings AND complaints from this subscriber
about blatant commercial messages. I'm not inclined to play
games.

Had this been a one-time occurrence, it would have
gotten only an off-line warning. Had this been a repeat
offense but apparently done accidentally or by someone who
truly didn't understand the rules, it would have gotten a
very strong warning. As I have no doubt that this subscriber
understands the rules AND refuses to follow them
AND complains vehemently about messages like the one
quoted in part above, I've suspended his privileges.

As a reminder, here are the rules.
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.