Mozilla Forum Etiquette
Ground Rules
There are a few ground rules for participation in forums hosted by mozilla.org. Please respect these rules, and each other.
- Be civil.
-
No personal attacks. Do not feel compelled to defend your honor in public.
- Stay on topic.
-
Most of these groups are high-traffic and read by busy people, so please pay attention to the topic of your messages, and check that it still relates to the charter of the forum to which you are posting. Off-topic discussion not taken to private email, mozilla.general, or any place where it is not considered off-topic, by someone who knows they should be taking it elsewhere, is eligible for removal from the news server.
- Be kind to newcomers.
-
Newcomers may be annoying. They ask the wrong questions, including ones that seem obvious (or whose answers seem easy to find). But lots of valued contributors started out this way, and treating newcomers kindly makes them more likely to turn into the valuable community members we all know and love (and cut some slack when they mess up).
So while you don't have to humor them or suffer them gladly, and it's fine to point out when they make mistakes, point newcomers in the right direction in addition to turning them away from the wrong ones, and be kind to them in the process of correcting their transgressions.
- Let sleeping dogs lie.
-
It's tempting to revisit controversial decisions you disagree with, but it's rarely productive to do so, since it almost always results in the same heated, lengthy, and time/energy draining discussions leading to the same conclusion that was reached in the last round.
Therefore, for issues already raised, discussed, and decided upon, reopen the discussion only if you have significant new information that would reasonably prompt reconsideration of the original decision.
- No crossposting.
-
It is almost never appropriate to send the same message to two mailing lists or newsgroups. Please don't do it. Or, if you must, make sure you set the Followup-To and Reply-To fields to ensure that replies go only to one, not to both.
example: Newsgroup: mozilla.dev.apps.seamonkey Newsgroup: mozilla.dev.apps.firefox FollowUp-To: mozilla.dev.apps.firefox Reply-To: dev-apps-firefox@lists.mozilla.org Subject: XPFE browser? It is never appropriate to send the same message to two forums when one of those forums has
general
in its name. - No advocacy.
-
These groups are for discussions about the Mozilla source code. As such, discussions about which operating system is better, or whether one toolkit is better than another, or whether Microsoft is the root of all evil, are not relevant. There are many forums for discussing such issues on Usenet; please have such discussions there instead of on the Mozilla forums. Might we recommend:
- Ignore spammers.
-
Spam is a blight upon the face of the net. Nobody likes it. However, it is hard to avoid. Despite our best efforts, you will occasionally see spam on the Mozilla mailing lists and newsgroups. If you feel the need to flame the spammer, do not CC the list. Complaining about spam in public increases noise, but not signal. It may make you feel better, but it doesn't help. (For info on fighting spam effectively, check out spam.abuse.net.)
- No large attachments.
-
Do not send binary attachments, including screen shots, and especially including screen shots of textual dialog boxes. Many people read these messages through slow network connections; try to be respectful of them. If you have a large file that you would like to distribute, put it on a Web page and announce the URL instead of attaching it.
- Trim your follow-ups.
-
Do not quote the entire content of the message to which you are replying. Include only as much as is necessary for context. Remember that if someone wants to read the original message, they can; it is easily accessible. A good rule of thumb is, don't include more quoted text than new text.
There is always a need for some trimming - either a salutation, a signature, some blank lines or whatever. If you are doing no trimming whatsoever of the quoted text, then you aren't trimming enough.
- Top-posting vs bottom-posting.
-
Some people like to put reply after the quoted text, some like it the other way around, and still some prefer interspersed style. Debates about which posting style is better have led to many flame wars in the forums. To keep forum discussion friendly, please do interspersion with trimming (see above for trimming rules). For a simple reply, this is equivalent bottom-posting. So, remove extraneous material, and place your comments in logical order, after the text you are commenting upon. The only exceptions are the accessibility forums, which are top-posting.
- Post HTML at your own risk.
-
Keep in mind that not everyone uses mail or news readers that can easily display HTML messages. Consequently, you will reach a larger audience if you post in plain-text. Many people simply ignore HTML messages, because it takes a nontrivial amount of effort to read them.
- Report bugs in Bugzilla, not in the Mozilla forums.
-
If you encounter a bug with Mozilla, please take the time to file a report in Bugzilla about it. Mozilla developers do not all have time to follow all the Mozilla-related forums on a regular basis, and if you just post a bug report to a newsgroup or mailing list then it may not reach anyone who can actually do anything about the bug. By reporting the bug through Bugzilla you ensure that it will receive a higher level of attention, and will be tracked along with other bugs. Please also read the Bugzilla etiquette page.
- Identify your subject matter.
-
Not everyone has time reading all forum postings. To ensure that your message reach the right people at timely manner, identify your subject matter clearly in the subject line. Subjects like a
question
andMozilla problem
are not very helpful. - No
unsubscribe
messages. -
Unfortunately, this bears repeating. See How To Subscribe.
- No
test
messages. -
Please do not send test messages to the newsgroups except to mozilla.test.
Learn more about Usenet newsgroups and Usenet etiquette at the Usenet Info Center.