Mailing list etiquette - Revision history

Neteler: + Links to "Code of conduct"

2015-03-10T12:16:26Z

+ Links to "Code of conduct"

← Older revision		Revision as of 12:16, 10 March 2015
Line 60:		Line 60:

	* [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] by Eric Steven Raymond		* [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] by Eric Steven Raymond


			'''Code of conduct'''
			* https://getfedora.org/code-of-conduct
			* http://www.ubuntu.com/about/about-ubuntu/conduct
			* https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/CodeOfConflict

⚠️HamishBowman: /* Privacy police and misc */

2013-05-28T03:36:34Z

Privacy police and misc

← Older revision		Revision as of 03:36, 28 May 2013
Line 53:		Line 53:

	Note that		Note that
	* the emails are sent to a public mailing list (upon subscription you can write; the archives are accessible to anyone)		* the emails are sent to a public mailing list (upon subscription you can write; the archives are accessible to anyone), this is a one-way process
	* Anti-spammer measures: your email address be disguised (username [at] domain.com) to help thwart spam crawlers		* Anti-spammer measures: your email address is (maybe) disguised (username [at] domain.com) to help thwart spam crawlers
	* The mailing list archive is statically mirrored ~~but~~ several public webmail archives (Nabble, Gmane, etc).		* The mailing list archive is statically mirrored by several public webmail archives (Nabble, Gmane, etc).

	= See also =		= See also =

	* [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] by Eric Steven Raymond		* [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] by Eric Steven Raymond

Neteler: +see also

2011-04-23T09:08:02Z

+see also

← Older revision		Revision as of 09:08, 23 April 2011
Line 56:		Line 56:
	* Anti-spammer measures: your email address be disguised (username [at] domain.com) to help thwart spam crawlers		* Anti-spammer measures: your email address be disguised (username [at] domain.com) to help thwart spam crawlers
	* The mailing list archive is statically mirrored but several public webmail archives (Nabble, Gmane, etc).		* The mailing list archive is statically mirrored but several public webmail archives (Nabble, Gmane, etc).

			= See also =

			* [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] by Eric Steven Raymond

Neteler: +Non-English mailing list

2011-04-01T19:41:37Z

+Non-English mailing list

← Older revision		Revision as of 19:41, 1 April 2011
Line 16:		Line 16:

	* English difficult? There are a number of [http://grass.ibiblio.org/community/support.php#localized localized mailing lists] available in a range of languages if you prefer.		* English difficult? There are a number of [http://grass.ibiblio.org/community/support.php#localized localized mailing lists] available in a range of languages if you prefer.

			* Non-English mailing list? Be sure to write in the language of the list..

	* We don't accept spam, commercial ads and other rubbish on the list - just don't send it (otherwise we'll unsubscribe the spammer).		* We don't accept spam, commercial ads and other rubbish on the list - just don't send it (otherwise we'll unsubscribe the spammer).

Neteler: +Privacy police and misc

2010-07-13T20:24:16Z

+Privacy police and misc

← Older revision		Revision as of 20:24, 13 July 2010
Line 1:		Line 1:
	== Mailing list etiquette ==		= Mailing list etiquette =

	The [http://grass.ibiblio.org/community/support.php 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.		The [http://grass.ibiblio.org/community/support.php 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.
Line 5:		Line 5:
	In general traditional [http://www.dmoz.org/Computers/Usenet/Etiquette/ Usenet etiquette] covers most of it.		In general traditional [http://www.dmoz.org/Computers/Usenet/Etiquette/ Usenet etiquette] covers most of it.

			== Some requests ==
	Some requests:

	* "''Just the facts, ma'am''" - Smaller to the point posts means we can handle a higher rate of traffic with less overhead.		* "''Just the facts, ma'am''" - Smaller to the point posts means we can handle a higher rate of traffic with less overhead.
Line 23:		Line 22:
	* Please [http://grass.ibiblio.org/searchgrass.php search the archives] and [http://grass.ibiblio.org/bugtracking/index.php bug trackers] for an answer before posting a question. Feel free to add any answers you find to basic questions to the [[Faq\|Wiki FAQ]].		* Please [http://grass.ibiblio.org/searchgrass.php search the archives] and [http://grass.ibiblio.org/bugtracking/index.php bug trackers] for an answer before posting a question. Feel free to add any answers you find to basic questions to the [[Faq\|Wiki FAQ]].

	~~'''~~Responding to other posts~~:'''~~		== Responding to other posts ==

	* 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.		* 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.
Line 37:		Line 36:
	* 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 (or ask them first).		* 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 (or ask them first).

	~~'''~~Common posting mistakes~~:'''~~		== Common posting mistakes ==

	* Avoid posting in HTML. It makes it hard to read for some people and bloats the email size. Post in plain text instead.		* Avoid posting in HTML. It makes it hard to read for some people and bloats the email size. Post in plain text instead.
Line 48:		Line 47:

	* To get a better response try replacing any "I want this new feature ..." in your email with "This would be good for GRASS because ..." and see if it still makes sense.		* To get a better response try replacing any "I want this new feature ..." in your email with "This would be good for GRASS because ..." and see if it still makes sense.

			= Privacy police and misc =

			Note that
			* the emails are sent to a public mailing list (upon subscription you can write; the archives are accessible to anyone)
			* Anti-spammer measures: your email address be disguised (username [at] domain.com) to help thwart spam crawlers
			* The mailing list archive is statically mirrored but several public webmail archives (Nabble, Gmane, etc).

⚠️HamishBowman: /* Mailing list etiquette */ +pastebin

2010-02-28T23:14:49Z

Mailing list etiquette: +pastebin

← Older revision		Revision as of 23:14, 28 February 2010
Line 14:		Line 14:
	* Be nice! We don't get paid to provide help and if common contributers get annoyed they might go away, and we don't want that. It is well understood that language barriers and the lack of verbal cues may alter the intended tone, so please don't take offense if someone appears rude, just ignore it. A post demanding "''I need an answer now''" is likely to never receive one.		* Be nice! We don't get paid to provide help and if common contributers get annoyed they might go away, and we don't want that. It is well understood that language barriers and the lack of verbal cues may alter the intended tone, so please don't take offense if someone appears rude, just ignore it. A post demanding "''I need an answer now''" is likely to never receive one.

	* 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://sites.google.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://osgeo.pastebin.com/ PasteBin], [http://sites.google.com Google webspace], and Flickr are three places you might post code, data files, and screenshots.

	* English difficult? There are a number of [http://grass.ibiblio.org/community/support.php#localized localized mailing lists] available in a range of languages if you prefer.		* English difficult? There are a number of [http://grass.ibiblio.org/community/support.php#localized localized mailing lists] available in a range of languages if you prefer.

⚠️HamishBowman: /* Mailing list etiquette */ clairfy

2010-02-18T02:01:42Z

Mailing list etiquette: clairfy

← Older revision		Revision as of 02:01, 18 February 2010
Line 47:		Line 47:
	* Cross-posting: There's no need to start a new message thread on both the -user and -dev mailing lists. Almost all people on the -dev list also read the -user list, so your question will not be lost. If the topic strays too far away from its starting list it may migrate to the other list. The danger of attempting a split discussion is that the relevant information does not get back to all parties and it is hard to follow in the archives.		* Cross-posting: There's no need to start a new message thread on both the -user and -dev mailing lists. Almost all people on the -dev list also read the -user list, so your question will not be lost. If the topic strays too far away from its starting list it may migrate to the other list. The danger of attempting a split discussion is that the relevant information does not get back to all parties and it is hard to follow in the archives.

	* To get a better response try replacing any "I want ..." in your email with "This would be good for GRASS because ..." and see if it still makes sense.		* To get a better response try replacing any "I want this new feature ..." in your email with "This would be good for GRASS because ..." and see if it still makes sense.

⚠️HamishBowman: /* Mailing list etiquette */ update url

2010-02-17T02:07:14Z

Mailing list etiquette: update url

← Older revision		Revision as of 02:07, 17 February 2010
Line 14:		Line 14:
	* Be nice! We don't get paid to provide help and if common contributers get annoyed they might go away, and we don't want that. It is well understood that language barriers and the lack of verbal cues may alter the intended tone, so please don't take offense if someone appears rude, just ignore it. A post demanding "''I need an answer now''" is likely to never receive one.		* Be nice! We don't get paid to provide help and if common contributers get annoyed they might go away, and we don't want that. It is well understood that language barriers and the lack of verbal cues may alter the intended tone, so please don't take offense if someone appears rude, just ignore it. A post demanding "''I need an answer now''" is likely to never receive one.

	* 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://sites.google.com Gmail webspace] and Flickr are two places you might post data files and screenshots.

	* English difficult? There are a number of [http://grass.ibiblio.org/community/support.php#localized localized mailing lists] available in a range of languages if you prefer.		* English difficult? There are a number of [http://grass.ibiblio.org/community/support.php#localized localized mailing lists] available in a range of languages if you prefer.

⚠️HamishBowman: /* Mailing list etiquette */ !me me me

2010-02-17T02:01:30Z

Mailing list etiquette: !me me me

← Older revision		Revision as of 02:01, 17 February 2010
Line 46:		Line 46:

	* Cross-posting: There's no need to start a new message thread on both the -user and -dev mailing lists. Almost all people on the -dev list also read the -user list, so your question will not be lost. If the topic strays too far away from its starting list it may migrate to the other list. The danger of attempting a split discussion is that the relevant information does not get back to all parties and it is hard to follow in the archives.		* Cross-posting: There's no need to start a new message thread on both the -user and -dev mailing lists. Almost all people on the -dev list also read the -user list, so your question will not be lost. If the topic strays too far away from its starting list it may migrate to the other list. The danger of attempting a split discussion is that the relevant information does not get back to all parties and it is hard to follow in the archives.

			* To get a better response try replacing any "I want ..." in your email with "This would be good for GRASS because ..." and see if it still makes sense.

⚠️HamishBowman: /* Mailing list etiquette */ thanks you notes

2008-12-01T02:54:01Z

Mailing list etiquette: thanks you notes

← Older revision		Revision as of 02:54, 1 December 2008
Line 32:		Line 32:

	* 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.		* 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.

			* While it is very useful to have confirmation that a suggested solution works lodged in the mailing list archives, and you should do that, you really don't need to cc a thank-you note to all 1000 readers of the list. Sending a private note to the helper is fine :)

	* 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 (or ask them first).		* 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 (or ask them first).