Mailing list etiquette: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(→‎Mailing list etiquette: public replies, specisivity)
Line 16: Line 16:
* If someone does reply to you in private (aka ''off-list''), please respect their wishes and do not quote their email back to the public list.
* If someone does reply to you in private (aka ''off-list''), please respect their wishes and do not quote their email back to the public list.


* Please be specific in your questions. Exact command line usage and exact error messages are much more useful and more likely to get a positive answer than simply "''g.module didn't work. Help!''"
* Please be specific in your questions. Exact command line usage and exact error messages are much more useful and more likely to get a positive answer than simply "''g.module didn't work. Help!''" Posting the version of GRASS and operating system you are using is helpful too.
 
* Please search the archives for an answer before posting a question. Feel free to add any answers you find to basic questions to the [[Faq|Wiki FAQ]].


* Avoid posting large attachments. The mailing list blocks very large attachments, and although smaller attachments are allowed through it is nicer to find some web space somewhere and post a URL to it rather than spam 1000 mailing list readers' long suffering inboxes with a largish file. [http://www.googlepages.com Gmail webspace] and Flickr are two places you might post data files and screenshots.
* Avoid posting large attachments. The mailing list blocks very large attachments, and although smaller attachments are allowed through it is nicer to find some web space somewhere and post a URL to it rather than spam 1000 mailing list readers' long suffering inboxes with a largish file. [http://www.googlepages.com Gmail webspace] and Flickr are two places you might post data files and screenshots.

Revision as of 05:49, 2 December 2007

Mailing list etiquette

The mailing lists tend to be high traffic and quickly suck away the time and mailbox space of those volunteering their time to help. Therefore we ask that a few simple rules be followed to make the experience nicer for everyone. These are not hard and fast rules and we don't mean to be controlling; the lists are not moderated. You must be subscribed to post to the list.

In general traditional Usenet etiquette covers most of it.


Some requests:

  • "Just the facts, ma'am" - Smaller to the point posts means we can handle a higher rate of traffic with less overhead.
  • Avoid posting in HTML. It makes it hard to read for some people and bloats the email size.
  • Please reply ongoing questions to the entire list, not just to the person who supplied some help. In this way other experts on the list can provide additional ideas and any solutions will be saved in the archives for future travelers.
  • If someone does reply to you in private (aka off-list), please respect their wishes and do not quote their email back to the public list.
  • Please be specific in your questions. Exact command line usage and exact error messages are much more useful and more likely to get a positive answer than simply "g.module didn't work. Help!" Posting the version of GRASS and operating system you are using is helpful too.
  • Please search the archives for an answer before posting a question. Feel free to add any answers you find to basic questions to the Wiki FAQ.
  • Avoid posting large attachments. The mailing list blocks very large attachments, and although smaller attachments are allowed through it is nicer to find some web space somewhere and post a URL to it rather than spam 1000 mailing list readers' long suffering inboxes with a largish file. Gmail webspace and Flickr are two places you might post data files and screenshots.
  • "This email is intended for you and you alone" footer notes have no place on a public list and may be considered rude. They are probably legally useless anyway.
  • A: Topposting.
  • Q: What's the most annoying thing on Usenet?
  • When replying to a message please crop away any useless quoted text, for example office phone numbers, mailing list details, irrelevant parts of the conversation, etc. Please do keep "So and so wrote:" tags so that someone reading an email can follow the quoted conversation without having to hunt back through the thread to see who said what.