[%# The contents of this file are subject to the Mozilla Public # License Version 1.1 (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.mozilla.org/MPL/ # # Software distributed under the License is distributed on an "AS # IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or # implied. See the License for the specific language governing # rights and limitations under the License. # # The Original Code is the Bugzilla Bug Tracking System. # # The Initial Developer of the Original Code is Netscape Communications # Corporation. Portions created by Netscape are # Copyright (C) 1998 Netscape Communications Corporation. All # Rights Reserved. # # Contributor(s): Stefan Seifert # Gervase Markham # Emma Humphries #%] [% PROCESS global/header.html.tmpl title = "Bugzilla Etiquette" style = "li { margin: 5px } .heading { font-weight: bold }" %]

Bugzilla Etiquette

It is our intention that [% terms.Bugzilla %] remains a useful tool for reporting and commenting on [% terms.bugs %], feature-requests, and tasks for the Mozilla community. In order to keep [%+ terms.Bugzilla %] a useful, inclusive place for this work, we have guidelines for using this site which, by using this site, you agree to follow. In addition, your participation on this site is also subject to Mozilla's participation guidelines. Violations of [% terms.Bugzilla %] etiquette or Mozilla's participation guidelines will be considered as grounds for suspending your privileges on this site, or suspend your account altogether.

Commenting

  1. No abusing people. Constant and intense critique is one of the reasons we build great products. It's harder to fall into group-think if there is always a healthy amount of dissent. We want to encourage vibrant debate inside of the Mozilla community, we want you to disagree with us, and we want you to effectively argue your case. However, we require that in the process, you criticize things, not people. Examples of things include: interfaces, algorithms, and schedules. Examples of people include: developers, designers and users. Attacking or encouraging attacks on a person may result in you being banned from [% terms.Bugzilla %].
  2. No obligation. "Open Source" is not the same as "the developers must do my bidding." Everyone here wants to help, but no one else has any obligation to fix the [% terms.bugs %] you want fixed. Therefore, you should not act as if you expect someone to fix a [% terms.bug %] by a particular date or release. Aggressive or repeated demands will not be received well and will almost certainly diminish the impact and interest in your suggestions.
  3. No spam. Posting comment spam will lead to the supsension of your account.
  4. No pointless comments. Limit comments on a [% terms.bug %] to information which will help with resolving it. Unless requested, additional "I see this too" or "It works for me" comments are unnecessary unless they are on a different platform or a significantly different build.
  5. No private email. Do not send comments to [% terms.bugs %] by private email; no-one else can read them if you do that, and they'll be missed and/or ignored. If an attachment is too big for [% terms.Bugzilla %], add a comment giving the file size and contents and ask what to do.

Changing Fields

  1. No messing with other people's [% terms.bugs %]. Unless you are the [% terms.bug %] assignee, or have some say over the use of their time, never change the Priority or Target Milestone fields. If in doubt, do not change the fields of [% terms.bugs %] you do not own - add a comment instead, suggesting the change.
  2. No whining about decisions. If another project contributor has marked a [% terms.bug %] as INVALID, then it is invalid. Filing another duplicate of it does not change this. Unless you have further evidence to support this, do not post a comment arguing that an INVALID or WONTFIX [% terms.bug %] should be reopened.

If you observe, or are the subject of behavior in violation of these guidelines, please tag the [% terms.bug %] or comment following our anti-abuse policy.

Other useful documents: The [% terms.Bug %] Writing Guidelines.

[% INCLUDE global/footer.html.tmpl %]