Mailing list guidelines

Revision as of 13:59, 30 September 2010

Before You Start

Please remember that when you are posting to a community mailing list, you are in effect asking a large group of people to give you some of their time and attention - to download your message, read it, and potentially reply to it. It is simply polite to ensure that your message is relevant to as many of the people receiving the message as possible. All of these guidelines stem from this basic principle.

• Read the Community_communication document: Do not post without reviewing this document.
• Search for existing answers: Believe it or not, your question might not be new - do a thorough search to see if it has been answered before.
• Post in the right place: Review the Community_communication document and make sure that you are posting in the right place for your topic.

Posting Guidelines

Be Nice

Be courteous and polite to fellow members in the list:

• Keep the language clean (no swearing)
• Respect other people: No regional, racial, gender or other abuse will be tolerated.

Keep it Legal

Make sure that you have the legal right to post your content and are not violating copyright or other laws.

Keep It Short

Remember that thousands of copies of your message will exist in mailboxes:

• 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)
• Don't excessively quote previous messages in the thread (trim the quoted text down to the most recent/relevant messages only).

Use Proper Posting Style

• No HTML or Rich Text: Set your mailer to send only plain text messages to avoid getting caught in our spam filters.
• Do not top post: 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 top post. Please, remove the irrelevant part of the previous communication(in case of more than a single correspondence) and use bottom, interleaved posting.
• Using interleaved posting: 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 sentences 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.
• Use links: Please provide URLs to articles wherever possible. Avoid cutting and pasting whole articles especially considering the fact that all may not be interested.
• Don't include attached files: Instead of including attached files, please upload your file to the MeeGo wiki and post a link to the file from your email message.

Do Not Cross Post

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.

Subscribers Only

Only subscribers can post to our mailing lists. If you would like to contribute to our mailing lists, we think it is only fair that you be a subscriber. Please note that if you want to participate only occasionally, you can subscribe to a list and set your email options to digest or no mail and read the web archives when you want to catch up.

Guideline Violations

See our process for dealing with violations for more details.

Requesting a New Mailing List

Keep in mind that we already have many mailing lists, so new lists need to be justified. Sending a request that has nothing more that "create mailing list x for me" will not be approved without additional justification.

Before you request a new list

• Review all of our existing mailing lists. Is there any way that you can use one of our existing lists to collaborate on your project.
• Think about the upstream lists. Most of the MeeGo components are based on upstream projects. Can you use the upstream infrastructure?

How to make the request

• Send an email to Dawn Foster to request the list.
• Include answers to the following questions in your email.

Answer the following questions in the request

• Why do you need this list?
• Who will be using this list?
• Who can I name as a co-owner of the list (this should be someone technical who is involved in the day to day working of the project)?
• Why are all of the the existing lists unsuitable for your project?
• If it relates to an upstream project:
  • Is there a reason you need a meego list and aren't using the upstream infrastructure?
  • How do you you plan to use this list to contribute back to the upstream project and how will the 2 activities relate to each other?

Additional Resources

• Mailing list guidelines by Shakthi Kannan (PDF): Great guideline summary and examples of posting styles.

Acknowledgements

Credit to the Fedora Mailing List Guidelines as a starting point under the Creative Commons Attribution-ShareAlike 3.0 Unported license.