Atom: http://mail-archives.apache.org/mod_mbox/www-community/?format=atom
Title: Tips for email contributors
Notice:    Licensed to the Apache Software Foundation (ASF) under one
           or more contributor license agreements.  See the NOTICE file
           distributed with this work for additional information
           regarding copyright ownership.  The ASF licenses this file
           to you under the Apache License, Version 2.0 (the
           "License"); you may not use this file except in compliance
           with the License.  You may obtain a copy of the License at
           .
             http://www.apache.org/licenses/LICENSE-2.0
           .
           Unless required by applicable law or agreed to in writing,
           software distributed under the License is distributed on an
           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
           KIND, either express or implied.  See the License for the
           specific language governing permissions and limitations
           under the License.

[TOC]

# Tips for email contributors # {#overview}

This is a collection of tips for assisting people to contribute to all ASF
mail lists.

- <a name="respectful" ></a>Respectful and considerate communities are one of the pillars of the
Apache way. Please aim to provide constructive comments and do not
denigrate others.

- <a name="appropriate-mailing-list" ></a>Send your comments to the appropriate mailing list. Well-directed
conversations are more productive and easier to find later. See [ASF
mailing lists](../foundation/mailinglists.html) and the [Contact Apache
FAQ](../foundation/preFAQ.html).

- <a name="volunteer-basis" ></a>Remember that most people are participating in development on a volunteer
basis and in their "spare time". These enthusiasts will attempt to respond
to issues. It may take a little while to get your answers.

- <a name="participants-busy" ></a>Most list participants are very busy. Their replies might appear to be
curt when they direct you to a document, or give a short answer without
niceties. If they spent too long preparing each reply, then they would
become exhausted.

- <a name="no-private-emails" ></a>Please do not send private emails about development or usage questions.
Rather keep the discussion on the mailing list, where we can all assist.
This also enables other people to learn from such common questions. The
time spent answering these questions is far more effective, and it helps
the community to grow.

- <a name="become-familiar" ></a>Become familiar with the mailing lists. As you browse and search, you
will see the way other people do things. Follow the leading examples.

- <a name="do-not-engage" ></a>Do not engage in personal attacks. That is not our way. If ever you see
one happening, then either help to defuse it or don't comment and let the
conversation die.

- <a name="do-not-use-you"></a>Try not to use the word "you". People get defensive when they think that
comments are directed at them personally. Consider using "one" or "we" or
even "me". Also stay away from "you said" then paraphrasing - too easy to
misinterpret their words.

- <a name="use-general-list"></a>It is also better to direct your comments to the list in general, rather
than to any specific person.

- <a name="avoid-gender"></a>Avoid the use of gender-specific terms like "he" or "she" simply by
writing better sentences: "Rene agreed to fix issue 542".

- <a name="research-topic"></a>Research your topic before beginning to discuss a new issue. Search and
browse through the email archives - your issue may have been discussed
before. Do not just perceive a problem and then rush out with a question -
instead, delve.

- <a name="clearly-explain"></a>Take the time to clearly explain your issue and write a concise email
message. Less confusion facilitates fast and complete resolution. Everyone
will benefit from the extra time on your part. The less unnecessary
discussion, the better.

- <a name="contribution-worthwhile"></a>Every contribution is worthwhile. Even if the ensuing discussion proves
it to be off-beam, then it may jog ideas for other people.

- <a name="use-sensible"></a>Use sensible and concise email subject headings. Search engines, and
humans trying to browse a voluminous list, will respond favourably to a
descriptive title.

- <a name="topic-focused"></a>Keep each topic focused. If some new topic arises then start a new
discussion. This leaves the original topic to continue un-cluttered.

- <a name="no-cross-posting"></a>Do not cross-post message. In other words, pick a mailing list and send
your messages to that mailing list only. Do not send your messages to
multiple mailing lists. The reason is that people may be subscribed to one
list and not to the other. Therefore, some people will only see part of the
conversation.

- <a name="do-not-send-html-mail"></a>Do not send HTML; send plain text (Content-type: text/plain) instead.
Sending HTML decreases the number of people who will read your email and is
the single most common cause of mail being rejected by the apache.org inbound
spam filtering.  If your mail bounced and the error message said the spam
hits include `HTML_MESSAGE`, re-send the message as plain text.

# Other email guidelines # {#other}

-  [ASF Mailing Lists](../foundation/mailinglists.html) 

-  [Apache Jakarta - Mailing Lists -
Guidelines](http://jakarta.apache.org/site/mail.html) 

-  [Apache Cocoon - Contribution Notes and
Tips](http://cocoon.apache.org/2.1/1177.html#Contribution+Notes+and+Tips) 

-  [How To Ask Questions The Smart
Way](http://www.catb.org/~esr/faqs/smart-questions.html) 

-  [RFC 1855: Netiquette Guidelines](http://www.ietf.org/rfc/rfc1855.txt) (text document)