cvs commit: LFS/FAQ netiquette.xml
sklein at linuxfromscratch.org
sklein at linuxfromscratch.org
Mon Mar 24 20:27:12 PST 2003
sklein 03/03/24 23:27:12
Modified: FAQ netiquette.xml
Merged the fixes from Bruce Dubbs <bdubbs at swbell.net> and other grooming
Revision Changes Path
1.4 +41 -33 LFS/FAQ/netiquette.xml
RCS file: /home/cvsroot/LFS/FAQ/netiquette.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- netiquette.xml 24 Mar 2003 17:53:39 -0000 1.3
+++ netiquette.xml 25 Mar 2003 04:27:12 -0000 1.4
@@ -1,60 +1,64 @@
<question><para>What about netiquette?</para></question>
-<answer><para>Here are some completely practical points of etiquette.
-They include only those items that someone would comment on you for missing.
-<para>For those who've been around project mailing lists awhile
-the first few items are an insult to the intellegence.
-There are better toward the end.
-<para>The reasons for these are omitted for brevity,
-but rest assured, there are reasons
-and those reasons are more than just an individual's personal preference.
+<answer><para>Here are some practical points of etiquette.
+They include only those items that will draw mention if missed.
+Those who've been around project mailing lists awhile
+will find the first few obvious.
+There are less obvious items toward the end.
+<para>The reasons for these points are omitted for brevity,
+but rest assured, these guidelines are more than just
+an individual's personal preference.
<para>While the text refers to "the lists" exclusively,
it doesn't intend to ignore the news groups
-to which the mailing lists are gatewayed.
+that mirror the mailing lists.
<para>With that out of the way,
here are a couple manners oriented items
-followed by more "mechanical" stuff.
+followed by more "mechanical" stuff:
<para>Please remember that it is rude to post questions
-that are answered in obviously available documentation
-such as the LFS and BLFS Books, this FAQ, the appropriate man pages,
-the list archives, and simple Google searches.
+that are answered in commonly available documentation
+such as the LFS and BLFS Books, this FAQ, the LFS Hints,
+the appropriate man pages, the list archives, and Google searches.
As long as you can demonstrate that you've made an effort to find the answer
and you're not offended by a pointer to documentation,
-no one should mind.
-Anyone who does mind can be ignored; they deserve it.
+no reasonable person will object to your question.
<para>Most of the bothersome flamewars start
-when a newbie with an overlarge ego posts an obvious question,
-is then laughed at (even in a kindly manner),
+when a newbie posts an obvious question,
+is then criticized (even in a kindly manner),
and becomes publically offended.
Please try to avoid this situation.
-Even the most unintellegent newbies (there are intellegent newbies)
-will usually realise their error,
-even if you don't mention that they're not being bright,
-if you point them at the exact documentation they should have read
-<para>As everywhere, things which are likely to become heated
-are best done off the lists, involving as few people as possible.
+"Wordlessly" pointing to the exact spot in the documentation is sufficient.
+If you feel you must criticize,
+please do it via private email, not on the lists.
+The same applies to anything else that may become heated.
+<para>The lists have an international membership so
+slang of all sorts and idiom are likely to be misunderstood.
+(Witness the recent discussion of "bootstrapping".)
+Any mention of profanity, politics, war, or religion (even in signatures)
+is likely to upset someone somewhere in the world so please avoid them as well.
+Finally, it is considered polite to post in English
+since many more people on the lists know it than any other language.
<para>Now for the more "mechanical" stuff.
-<para>Do not post in HTML.
+<para><emphasis role="bold">Do not post in HTML.</emphasis>
If you use Yahoo, Hotmail, or Outlook
and haven't turned HTML off, then it is on.
If you're using another mail client, please do check before posting.
If you don't know how to turn HTML off,
see <ulink url="http://www.expita.com/nomime.html"/>.
-<para>Wrap text at 72 characters.
+<para><emphasis role="bold">Wrap text at 72 characters.</emphasis>
If you do not wish to do this by hand,
set your mail client to do it automatically when sending.
-<para>Reply below quoted text.
+<para><emphasis role="bold">Reply <emphasis>below</emphasis>
<!-- XXX: A well formatted example is below. -->
Outlook makes this difficult.
There is a plugin to fix Outlook at
@@ -62,13 +66,17 @@
and one for Outlook Express at
-<para>Do not click reply unless you're actually replying to a post.
-Use new or compose or whatever your mail client calls it.
+<para><emphasis role="bold">Do not click reply
+unless you're actually replying to a post.</emphasis>
+Use new, or compose, or whatever your mail client calls it,
+to ask a new question or start a new thread.
Reply sets more than just the subject line
and will cause your post to appear in the wrong place
unless you're actually answering.
-<para>This isn't major, but is useful to know.
+<para><emphasis role="bold">Limit signatures to four lines.</emphasis>
+<para>The following isn't major, but is useful to know.
On the LFS lists, people usually clear the CC field
and just mail the list with replies.
This is probably not a good idea but is existing practice
@@ -131,7 +139,7 @@
If you actually want to be read and understood
in a high traffic place like the LFS lists,
-paragraph separation, use of lists, and general whitespace use
+paragraph separation, use of bulleted lists, and general whitespace use
are surprisingly critical.
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-book' in the subject header of the message
More information about the lfs-book