TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
>----------
>From: Eric J. Ray[SMTP:ejray -at- RAYCOMM -dot- COM]
>Reply To: Eric J. Ray
>Sent: Wednesday, October 14, 1998 3:04 PM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject: ADMIN: Posting Rules Reminder
>
>Gang,
>
>Please review the posting rules. Specifically:
>
> * If it is about technical communication and ORIGINAL and
> humorous, 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.
>
>Thanks!
>Eric
>
>
>POSTING RULES FOR TECHWR-L
> Revised 31 July 1998
>
>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.
> * If it is a job offer for technical communicators, 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 a test message, do not post it. Ever. Contact
> the listowner if you have problems posting or with your
> subscription.
> * 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.
> * Edit all unnecessary quoted messages and TECHWR-L footers
> out of your postings, and make sure that you send only
> plain text messages and no attachments to the list.
> * 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 RayComm, Inc.
>http://www.raycomm.com/ ejray -at- raycomm -dot- com
>
>*Award-winning author of several popular computer books
>*Syndicated columnist: Rays on Computing
>*Technology Department Editor, _Technical Communication_
>
>From ??? -at- ??? Sun Jan 00 00:00:00 0000==
>
>
>
>