Mailing list guidelines/zh-cn

From FedoraProject

< Mailing list guidelines(Difference between revisions)
Jump to: navigation, search
(Getting Help From Your System)
m (开启新话题)
 
(16 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{lang|en|es|zh-cn|page=Mailing list guidelines}}
 +
 
=== 向列表发邮件之前 ===
 
=== 向列表发邮件之前 ===
  
There are a number of ways you can [[#gettinghelp| find help within your system]].  If you don't find the answer there, try to look into the [[#archives| list archives]] before posting a question.  This is a high volume list and chances are that someone has already had the same problem you are now trying to fix.  See [[#resources| Useful Resources]] below for a list of places to try. Refer to this [http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf presentation] on mail etiquette that you should follow.
+
您可以通过许多种方法来 [[#从系统里获得帮助|从系统里获得帮助]]。如果您未能找到对您有帮助的信息,请在发布您的求助之前尝试来到 [[#列表归档|邮件归档 ]]找一找。这是一个高流量的列表,也许您会找到之前有人做出的解决方案。请参见下方 [[#resources|有用的资源]] 以获知一些尝试的地方。参阅这个 [http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf 展示文档] 以了解您应该遵循的邮件礼仪。
  
 
=== 如果您仍然找不到答案 ===
 
=== 如果您仍然找不到答案 ===
  
If you don't find a suitable answer for your question in the [[#resources| resources]] described below, then writing to the list is a good idea. These guidelines were written to make sure your message gets the attention it needs to be read and answered.  You may also find useful to look at [http://www.charlescurley.com/netiquette.html Charles Curley's netiquette guide] .
+
如果您在下文的 [[#有用资源|有用资源]] 中依然没有找到答案,那么写信到邮件列表是个好主意。These guidelines were written to make sure your message gets the attention it needs to be read and answered.  You may also find useful to look at [http://www.charlescurley.com/netiquette.html Charles Curley's netiquette guide] .
  
 
{{Anchor|postingguidelines}}
 
{{Anchor|postingguidelines}}
 +
 
== 发言指南 ==
 
== 发言指南 ==
  
Line 27: Line 30:
 
=== 不要添加附件 ===
 
=== 不要添加附件 ===
  
Attachments to the mails sent to mailing lists is not taken in good taste. Please avoid doing it.
+
向邮件列表发邮件时添加附件可不是好主意。请避免这么做。
  
 
{{Anchor|newsubject}}
 
{{Anchor|newsubject}}
 +
 
=== 开启新话题 ===
 
=== 开启新话题 ===
  
When you send in a new topic, do not start by replying to an existing message, but rather, start a new message to "users@lists.fedoraproject.org". This keeps messages organized by thread, for people who like to use threads (on high-volume mailing lists like this one, threads can be a great convenience).
+
当您展开新话题时,请不要在已有的其它邮件中提及。'''请单独发送一封新邮件'''。这将使得所有信息能按话题归类,通常在高流量的邮件列表,很多人喜欢按照话题查看相关信息。
  
Furthermore, please do not recycle messages. Recycling messages is replying to an existing thread by changing the thread name. this creates confusion & diverts the number of people repling to the topic.
+
还有,请不要打断话题线索,也就是千万不要用一个修改后的主题回复已有线索。这会导致一部分人人无法理解原话题的内容,并且会使得先前的一部分无法回复至原话题。
  
For details see http://mm.bbspals.org/message-recycling/  
+
详情请见 http://mm.bbspals.org/message-recycling/  
  
 
{{Anchor|goodsubject}}
 
{{Anchor|goodsubject}}
Line 124: Line 128:
 
=== 取消订阅 ===
 
=== 取消订阅 ===
  
To unsubscribe from the list you can visit the [https://admin.fedoraproject.org/mailman/listinfo/users Fedora Users List web page]
+
退订请访问 [https://admin.fedoraproject.org/mailman/listinfo/users Fedora邮件列表管理] 页面。
  
 
{{Anchor|signatures}}
 
{{Anchor|signatures}}
Line 150: Line 154:
 
=== 不要全部大写(英文字母) ===
 
=== 不要全部大写(英文字母) ===
  
Using capital letters in your sentences is considered shouting. It is considered as being rude. If you want to emphasize on something *use this* or _this_.
+
如果您全部使用大写,可能会被认为您正在大声呐喊您的内容,这被认为是不礼貌的。如果您想强调某些内容,请这样发布:*您要强调的内容*,或者这样发布:_您要强调的内容_.
  
 
{{Anchor|repeats}}
 
{{Anchor|repeats}}
 +
 
=== 不要重复发送 ===
 
=== 不要重复发送 ===
  
Line 165: Line 170:
  
 
{{Anchor|gettinghelp}}
 
{{Anchor|gettinghelp}}
=== 从你的系统里获得帮助 ===
+
=== 从系统里获得帮助 ===
  
有许多方法从你的系统里获取信息。右击桌面打开一个终端窗口。在窗口里输入以下中的一个(不包括 '$',并且把''application-name'' 替换为你的出问题的应用软件的名字)。
+
有许多方法从您的系统里获取信息。右击桌面打开一个终端窗口。在窗口里输入以下中的一个(不包括 '$')。
  
 
<pre>
 
<pre>
$ man application-name
+
$ man 出问题的应用软件的名字
$ info application-name name
+
$ info 出问题的应用软件的名字 name
 
$ locate stuff-you-want-to-know-about
 
$ locate stuff-you-want-to-know-about
$ rpm -qd packagename
+
$ rpm -qd 出问题的软件包的名字
 
</pre>
 
</pre>
  
Line 182: Line 187:
 
=== 文档 ===
 
=== 文档 ===
  
A lot of effort is currently being put into documentation for Fedora. Some of the results of this are:
+
Fedora项目已经把许多问题的解决方案放入文档,他们位于这里:
  
* [http://docs.fedoraproject.org/ Fedora Documentation Index]  
+
* [http://docs.fedoraproject.org/ Fedora 文档检索首页]  
* [http://docs.fedoraproject.org/release-notes/ Fedora Release Notes]  
+
* [http://docs.fedoraproject.org/release-notes/ Fedora 发行注记]  
* [http://docs.fedoraproject.org/fedora-install-guide-en/ Fedora Installation Guide]  
+
* [http://docs.fedoraproject.org/fedora-install-guide-en/ Fedora 安装指南]  
* [http://docs.fedoraproject.org/selinux-faq/ Fedora SELinux FAQ]
+
* [http://docs.fedoraproject.org/selinux-faq/ SELinux 常见问题解答]
* [http://docs.fedoraproject.org/jargon-buster/ Jargon Buster]  
+
  
Red Hat Enterprise Linux is based on the Fedora project. So, the RHEL documentation should be helpful for the Fedora user:
+
[[RHEL|Red Hat Enterprise Linux]] 基于Fedora项目而成。所以RHEL的文档对Fedora用户也会有帮助,它们位于:
  
* [http://www.redhat.com/docs/ Red Hat Documentation Index]  
+
* [http://www.redhat.com/docs/ Red Hat 文档检索首页]  
* [http://www.redhat.com/docs/manuals/enterprise/ Red Hat Enterprise Linux Manuals]  
+
* [http://www.redhat.com/docs/manuals/enterprise/ Red Hat Enterprise Linux 手册]  
  
Also, good help can be found here:
+
还有一些好的文档:
  
* [http://www.fedorafaq.org/ The Unofficial Fedora FAQ]  
+
* [http://www.fedorafaq.org/ 非官方的Fedora 常见问题解答]  
 
* [http://www.tldp.org/ The Linux Documentation Project]  
 
* [http://www.tldp.org/ The Linux Documentation Project]  
 
* [http://fedoratracker.org/ Fedora Tracker]  
 
* [http://fedoratracker.org/ Fedora Tracker]  
  
 
{{Anchor|archives}}
 
{{Anchor|archives}}
 +
 
=== 列表归档 ===
 
=== 列表归档 ===
  
Line 221: Line 226:
  
 
* http://www.google.com
 
* http://www.google.com
* http://www.google.com/linux
 
  
 
Search for Fedora issues almost invariably returns multiple hits.  Of course, if you are using google, its search criterion/criteria are important here and multiple attempts on keyword variations may be needed. One particularly helpful way to narrow the search is to include a mailing list name in the search criteria.  Some examples:
 
Search for Fedora issues almost invariably returns multiple hits.  Of course, if you are using google, its search criterion/criteria are important here and multiple attempts on keyword variations may be needed. One particularly helpful way to narrow the search is to include a mailing list name in the search criteria.  Some examples:

Latest revision as of 06:28, 8 February 2014

Contents

[edit] 向列表发邮件之前

您可以通过许多种方法来 从系统里获得帮助。如果您未能找到对您有帮助的信息,请在发布您的求助之前尝试来到 邮件归档 找一找。这是一个高流量的列表,也许您会找到之前有人做出的解决方案。请参见下方 有用的资源 以获知一些尝试的地方。参阅这个 展示文档 以了解您应该遵循的邮件礼仪。

[edit] 如果您仍然找不到答案

如果您在下文的 有用资源 中依然没有找到答案,那么写信到邮件列表是个好主意。These guidelines were written to make sure your message gets the attention it needs to be read and answered. You may also find useful to look at Charles Curley's netiquette guide .

[edit] 发言指南

[edit] 保持简短

The fedora-list maintains a maximum message length of 64 kilobytes; other Fedora lists may have similar length-limits. Remember that thousands of copies of your message will exist in mailboxes -- please keep your messages as short as possible. Avoid including log output (select only the most relevant lines, or place the log on a website or in a pastebin instead) or excessively quoting previous messages in the thread (trim the quoted text down to the most recent/relevant messages only).

[edit] 请不要使用HTML邮件

Set your mailer to send only plain text messages to the list (How? ). Why? HTML is designed for web pages, not emails, and uses a lot more bandwidth. Many list members actually block HTML because it is used for malicious code.

Not only does HTML mail be used to run malicious scripts, but when using handheld devices the time taken for the page to appear is also much higher.

(see "7 reasons why HTML e-mail is EVIL! ")

[edit] 不要添加附件

向邮件列表发邮件时添加附件可不是好主意。请避免这么做。

[edit] 开启新话题

当您展开新话题时,请不要在已有的其它邮件中提及。请单独发送一封新邮件。这将使得所有信息能按话题归类,通常在高流量的邮件列表,很多人喜欢按照话题查看相关信息。

还有,请不要打断话题线索,也就是千万不要用一个修改后的主题回复已有线索。这会导致一部分人人无法理解原话题的内容,并且会使得先前的一部分无法回复至原话题。

详情请见 http://mm.bbspals.org/message-recycling/

[edit] 写个好标题

Make a subject line that clearly tells us what you need. This is a point that can't be overemphasized. Try "Can't get past partitioning on F9" instead of "Argg - help me!!!" Why? So that people with certain skills, looking for someone to help, will notice your message. That helps you get help from the right people quickly.

On a high volume list like this, many people just skim through the subject lines and only read the messages that catch their interest. So, by creating a good subject line, you increase the chances that your message is actually going to be read and eventually answered.

Also refer to the subject for commercial messages below.

[edit] 如果要回复一个消息

Make sure we can tell what you are replying to. Place each part of your reply after the text it addresses (i.e., NO Top-Posting, please see "Wikipedia - Top Posting" and links therein for more on this). Most mail readers automatically put a '>' character in front of each replied-to line. It gives a conversational flow to the text, and people know what you're replying to. Trim irrelevant material. It makes it easier to read your reply and helps the reader to stay on subject. Using bottom, interleaved posting is recommened as it is more organised.

[edit] 回复摘要

In a high volume list like this, you may choose to receive mails in digested mode. However when replying to such messages, please avoid just hitting the reply button. This creates meaningless messages like "Re: Fedora-ambassadors-list Digest, Vol 44, Issue 10" which does not reflect what you are talking about. Please edit the subject to reflect what topic you are talking about.


[edit] 当您的问题得到答复后请告诉大家

When you get a solution to your question (or find it yourself after posting to the list), reply to your original e-mail describing what solved your problem, adding a [SOLVED] to the end of the subject line. This will let people know that you don't need help any more with this and can look for other posts to help. Also, it makes a search in the archives easier when someone has a related problem in the future.

[edit] 得体的发表格式

Top posting is replying to a message on "top" of the quoted text of the previous correspondence. This is highly unwanted in mailing lists because it increases the size of the daily digests to be sent out & is highly confusing and incoherent. By default, most email clients use this (includes gmail & hotmail). Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.

Do not over-qoute by the hierarchy level in the correspondence.

Bottom, interleaved posting is replying to the relevant parts of the previous correspondence just below the block(s) of sentences. For a comment to another block of sentenses of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irrelevant text.

Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested. Pasting whole articles may also amount to copyright violations, which is not something that this list encourages.

Read the above mentioned pdf file on mailing list guidelines by Shakthi Kannan : http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf. The illustrative document should claer all doubts.

[edit] 礼貌些

Be courteous and polite to fellow members in the list. Never swear or be rude to anyone.

[edit] 一些行为指南

If a mail has offended you personally, please send a private message to the person expressing how you feel, instead of sending it to the mailing list.

Please remember that we have members from all genders & nationalities. No gender abuse is allowed on the list, and do not include any gender specific slang in your posts. Also do not indulge in racial or regional criticism. This is a very serious violation.

Be careful when using sarcasm and humour. Without face to face communications your joke may be viewed as criticism. When being humourous, use emoticons (smileys) to express humour. (tilt your head to the left to see the emoticon smile) :-) = happy face for humour.

Behave in a professional manner in the mailing lists. Any mistake could put you under the scanner & at the receiving end of much rebuke.

[edit] 不要四处发布

Avoid posting to multiple lists simultaneously. Pick a mailing list that is most suitable for your post and just use that. CC'ing multiple lists should be avoided.

Post to the the mailing list that is most suited to your purpose & then just copy the link to that page or mailing list & paste to all the other mailing lists you want to post to. this will ruduce the amount of data duplicated - only one copy will be accessed by all who read it.

http://en.wikipedia.org/wiki/Crossposting

[edit] No chain letters

Never send chain letters to the mailing list. A mail simultaneously sent to more than 10 users will not reach the list. This is to eliminate possible spammers/bulk mailers to reach the list.


[edit] Don't make social network connections through the mailing list

Do not send invitations to social networking sites through the mailing list. The email addresses of people on the mailing list is visible to the members. To add mailing list contacts to your socail network, try searching them on the socail networking site or contact through email & not the mailing list.

[edit] 商业信息

When using the mailing list for commercial purpose, please prefix the subject line with "COMMERCIAL".

[edit] 取消订阅

退订请访问 Fedora邮件列表管理 页面。

[edit] 不要用长串签名和声明

We find value in your main content rather than signatures. One or two lines would be optimal to convey messages that must be included in your signature and avoid huge disclaimers describing how your mail is private and confidential while sending things to the mailing list. If your company/organization enforces that in the mail gateway, use a webmail with pop/imap access like gmail for instance. Such disclaimers aren't enforceable half of the time and are monumentally silly in a public mailing list.

[edit] Do not use a PGP Style Signature that is not published

Use of PGP or GnuPG signing is encouraged. However, if the corresponding key is not published on a public keyserver, then the message will cause some email client applications (MUAs) that are PGP/GPG aware to hang while they try all known keyservers. This can take a long time and cause frustration for other users. For more information on how to properly create and use GPG keys, read the Creating GPG Keys page.

[edit] 使用通用语言

Unless you are a Fedora mailing list that is dedicated to users speaking that particular language, communicate in English. Other languages might be ignored merely because the users in these lists might only know English or use it as their common language. Refer to the Communicating and getting help page for more information on other mailing lists.

Use standard language and not colloquial or regionally accepted abbreviations.Visit http://www.jargon.org for more such acronymns.

Use the universally accepted standard English. Always do a spell check before mailing to the list. Grammar doesn't matter as long as one is understood. Do not use SMS language. Do not use dots(".....") to conclude the sentences as is common across social networks.

[edit] 不要全部大写(英文字母)

如果您全部使用大写,可能会被认为您正在大声呐喊您的内容,这被认为是不礼貌的。如果您想强调某些内容,请这样发布:*您要强调的内容*,或者这样发布:_您要强调的内容_.

[edit] 不要重复发送

Often people helping on the mailing lists are volunteers who, just like you, have busy lives. If you do not get a response within a few minutes or hours, avoid re-posting the same question repeatedly. Give a minimum of 24-48 hours for an answer, and if you don't have one by then, give a "nudge" to the list by replying to (not re-posting) your original message.

Please *read all your mails before replying* to a mail. Someone may have already answered it.


[edit] 有用资源

[edit] 从系统里获得帮助

有许多方法从您的系统里获取信息。右击桌面打开一个终端窗口。在窗口里输入以下中的一个(不包括 '$')。

$ man 出问题的应用软件的名字
$ info 出问题的应用软件的名字 name
$ locate stuff-you-want-to-know-about
$ rpm -qd 出问题的软件包的名字

你也可以在 /usr/share/doc 目录下找到大量的文档。

[edit] 文档

Fedora项目已经把许多问题的解决方案放入文档,他们位于这里:

Red Hat Enterprise Linux 基于Fedora项目而成。所以RHEL的文档对Fedora用户也会有帮助,它们位于:

还有一些好的文档:

[edit] 列表归档

Sometimes difficult to use. Try the extended search or just entering your search query again after it returns the initial 0 found.

Good search engine, preserves threads. Also can display the answer in many different formats, to suit anyone's preferences.

Another favorite of the list users. However, it seems to use subjects instead of references to sort the messages, which means that the threads are sometimes broken.

[edit] 搜索!

Search for Fedora issues almost invariably returns multiple hits. Of course, if you are using google, its search criterion/criteria are important here and multiple attempts on keyword variations may be needed. One particularly helpful way to narrow the search is to include a mailing list name in the search criteria. Some examples:

fedora users + "boot hang"
fedora devel + pup

Another possibility is to include site:lists.fedoraproject.org instead of the list name. It will search all the main archives, which also include the test and devel lists (testers or developers are likely to come across problems before you do), the RHEL lists, and the old Red Hat lists.

[edit] 致谢

This document grew from the work of James McKenzie, Duncan Lithgow, Gustavo Seabra, David Curry, James Wilkinson, Perry Spiller, Christofer C. Bell and various people's useful comments and is in the spirit of the: RedHat Install List (RHIL) Unofficial User's Guide and How To Ask Questions The Smart Way .

Netiquette discussions are always ongoing and previously established conventions are continually revisited. Please read these guidelines in the spirit intended: to create a living document that reflects group consensus. Remember, you are more likely to receive answers to your questions if you adhere to these guidelines.