Mailing List Netiquette
It should go without saying, but say we will:
- Be respectful of the time and feelings of others. Reply to posts
with courtesy and tolerance—everyone was once a newbie. Clarity
of expression, concise and on-point postings, and correct spelling and
grammar are always appreciated.
- Please use plain-text English. Avoid using attachments, as e-mail
filters can remove them.
- When asking for help or coding advice, remember to include enough
information for meaningful responses. List members are valuable
resources that should be consulted with care. They are not Google or
free programmers! Do your homework first (sometimes literally), then
by all means ask.
- When following up a post, please think before you quote. Since
everybody else on the list also received the original post, don't
quote it entirely. Quote only the points that are really needed to
understand your follow up. Make sure the quoted part is recognizable
as such, by ensuring each quoted line starts with a > (or more, in
cases of multi-level quoting). Please don't quote signatures, entire
code examples, or entire posts. Be considerate of the time and disk
storage of others.
- Also, please reply after the quoted
text, not before it (as per RFC
1855). It's confusing to see a reply before the quoted context.
Stick to the subject of the original post or change the subject line
to match the new focus.
- Please don't have long, inflammatory, cute, controversial, or
offensive signatures in your postings (see RFC
1855). The best bet is to avoid using a signature altogether. If
you feel you must include a signature, the rule of thumb is no more
than 4 lines of 80 characters each.
Many thanks for participating in the GBBopen mailing lists!
|