Attack Things not People

Simple rule for our community: 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.

For instance, acceptable forms of communication would include:

"I think this is a bad idea for the following reasons..."
"This change needs to be removed for the following reasons..."
"This change fails to account for some important use cases..."
"I don't understand the logic behind favoring A over B..."
"The data used to make decision N is flawed because..."
"The principal used to make decision N is flawed because..."

Unacceptable forms of communication include:

"I think developer/designer/director N should be fired"
"People who think A is better than B are idiots"
"The only thing [group of people N] are good at is [disparaging thing]"
"If _YOU_ don't [thing], then _I_ am going to [action to be taken by angry
commenter]"
"Why are we just catering to the users who are stupid?"
"The only way to solve that problem is to reduce the number of stupid users"

Overall it's a pretty simply rule, it isn't about the veracity of the
critique but rather the sentience of the target.

Don't be a jerk.

-Alex