On Wed, Jan 10, 2007 at 03:02:02AM -0500, Kevin Mark wrote:
> On Tue, Jan 09, 2007 at 11:37:30PM -0800, Justin Gallardo wrote:
> > I am preparing a presentation to a group of students on mailing list 
> > netiquette
> > (as you may have guessed by the subject), and thought that maybe I could use
> > the busiest mailing list I followed as a good source of information. I have
> > thought of numerous things to bring up in the presentation including rules
> > ...
> > Also, if you can think of any other good points to bring up during this 
> > talk, I
> > would love to hear them. The purpose of the talk is to help create better 
> > open
> > source community members for the future. So any help now could possibly save
> > you some heartache later :-).
> > --
> Hi Justin,
> heres a few:
> -remove chunks of the post if possible as its better to not send 50 line
> posts each time if you are only replying to 2 lines.
> -if the person is responding to a mailing list, reply to the list only
> -unless the person does not read the list or the person asks you too. On
> debian-user, we read the list -- no need to get 2 replys.
> -dont flame
> -always provide error message verbatum and other info that give the folks 
> hints
> to help you solve the problem otherwise they will ask you for it later
> -dont paraphrase error message -- it only wastes time (see above)
> -dont use html 
> -keep signatures less than 15 lines
> -make example data anonymous/remove personal data in examples
> cheers,
> Kev
> -- 
> |  .''`.  == Debian GNU/Linux == |       my web site:       |
> | : :' :      The  Universal     |   'under construction'   |
> | `. `'      Operating System    | go to counter.li.org and |
> |   `-    http://www.debian.org/ |    be counted! #238656   |
> |   my keysever: subkeys.pgp.net |     my NPO: cfsg.org     |


(Leaving the previous message as a case in point... ;-)

I'd have to add:

  - whitespace,

  - whitespace,

  - whitespace.

Blank lines cost little, just 8 bits, but help considerably to make
posts easier to read.

Code segments, command line examples, bulletted lists, all benefit
from indenting to clearly separate them from ordinary message text,
in addition to having blank lines before and after.  Such indentation
should survive quoting by decent mailers.

Ken

-- 
Ken Irving, [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to