Update the Bugzilla Etiquette document to reduce confusion on why someone was banned

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
General
RESOLVED FIXED
8 years ago
7 years ago

People

(Reporter: faaborg, Unassigned)

Tracking

Details

The current Bugzilla Etiquette document is comprehensive, but it may not be clear enough to communicate with people who are landing on it when they are extremely angry (which is usually correlated with them just being warned, or just being banned).

For the most extreme cases, users are usually breaking section 1.3:

>No personal abuse. Bugzilla is a window into the world of Mozilla development.
>The fact that we permit anyone with an account to add a comment does not mean you
>may harass, harangue or otherwise hassle contributors. Do not make weak threats
>like "I won't use Mozilla until this bug is fixed!" If a respected project
>contributor complains about your Bugzilla attitude, then you may have your
>account disabled. If you don't like this possibility, become a respected project
>contributor.

This is what the user may be thinking:

"I'm just getting banned because I disagreed with them in public, Mozilla is a special club and they don't like dissent.  They even say that I'm out because I called them on being stupid, and I'm not a "respected project contributor" (i.e. in their special club)."

The other downside to this section is that it indirectly implies (inaccurately, I hope) that respected project contributors may engage in personal abuse.

Here's some text that could clear up both misconceptions:

1.1 Attack Things not 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.  It’s harder to make mistakes when every facet of every decision is being ruthlessly analyzed by a large and diverse group of people.  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, while engaging in these debates, it’s critical that people follow one simple rule: Attack Things not People.  Examples of things include: interfaces, algorithms, processes, schedules, etc. Examples of people include: developers, designers, users, etc.  **Attacking a person instead of a thing may result in you being banned from Bugzilla**.

Comment 1

8 years ago
I propose we have two documents. The "rules" document that Alex has drafted here, and a second "how to be effective" document that includes etiquette and best practices.
(Reporter)

Comment 2

8 years ago
Gerv: in the last few weeks the tone of comments in Bugzilla has pretty significantly declined.  Could we get this landed to try to reverse the trend?
I think trying to implement Asa's suggestion will result in delay. We can always do that later. I've checked Alex's text, slightly copyedited, into the bmo-3.6 and bmo-4.0 repositories. I'll get picked up next time bmo updates (which is quite frequently these days).

Gerv
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(In reply to comment #3)
> I think trying to implement Asa's suggestion will result in delay. We can
> always do that later. I've checked Alex's text, slightly copyedited, into the
> bmo-3.6 and bmo-4.0 repositories. I'll get picked up next time bmo updates
> (which is quite frequently these days).
Thanks a ton!
(Assignee)

Updated

7 years ago
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.