Re: [OFF-TOPIC] Mailing List Netiquette

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jan 09, 2007 at 11:37:30PM -0800, Justin Gallardo wrote:
Hey All,
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
about top-posting(not doing it), tips to help keep the flow of conversation,
and other various things. There was one thing that I wasn't quite sure what
everyone's opinion was though. When replying to an email, is it proper to leave
the original poster in the To: line of the email, and the CC the list? Or is it
better to just send your reply to the list, not specifically mentioning the
original poster. Possibly it is acceptable to just do whatever Reply All in
your client gives you(I would think the effect of this is configurable through
the mailing list). I was curious if I could get other's input on this matter.
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 :-).

Thanks a bunch.

--
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 |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFpJ16v8UcC1qRZVMRAuY3AJ42TwOykfGMd5MNHZrmR36fVMXMoACfaPiY
ynpZx8pg6mG73bC+YPTsLvA=
=vWMJ
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: [OFF-TOPIC] Mailing List Netiquette
    ... I am preparing a presentation to a group of students on mailing list ... original poster in the To: line of the email, ... The purpose of the talk is to help create better open source ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • RE: Something to come home to...
    ... please ask permission from original ... the original poster and it should be okay to use the ... To unsubscribe: ... in 45,000 destinations on Yahoo! ...
    (Fedora)
  • Re: edit the subject line of a thread?
    ... When replying to a mail/thread it is best not to modify the Subject ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: Teacher, Student Reach Compromise In Restraining Order Case
    ... > the original poster is make sure that the very first line of your reply is ... I noticed his request and was very careful to not delete ... *anything* before replying because I thought that was what I needed to do. ... I certainly didn't do it on purpose to ignore or discount his request. ...
    (alt.true-crime)
  • Re: What is Top-Post???
    ... clients (Outlook, Outlook Express) defaulting to that position, thereby ... Your reply should go below the material you're replying to, ... Your response to Topic 1 goes here. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
Loading