gregglind · April 3, 2012 21:23
diff --git a/code_of_conduct.txt b/code_of_conduct.txt
 (this is a bit fragmentary.  My goals:  
 * some mix of aspiration and operational
 * I don't care what people believe, only how they act in the rooms
 * I want acknowledgement of impact, and feelings.  
 * we might lose people over this.  That doesn't make this not worthwhile
 * The person impacted has agency to decide the impact on them.  
 )


 Big principles:

 * mutual accountability
 * respectful discourse
 * welcoming openness and encouragement of contributions from everywhere (phrasing?)
 * separation of personal speech from mozilla speech

 We want Mozilla spaces to be splendid, respectful, and productive.

 In Mozilla spaces we agree:

 * there is no normal brain, or right country of birth, language, correct gender, sexuality, or religion.  These are all parts of normal human variation.
 * no one starts as an expert, and no one was born with a keyboard in their hand.  We help build the inexperienced up with skills and encouragement.
 * all contributors are welcome, and their work is welcome.
 * the value of a contribution is completely independent of the race, gender, sexuality, physical ability, (etc.)
 citizenship status, etc. of the contributor, and should be evaluated accordingly.
 * to hold each other accountable for violations of these code.
 * power comes in many forms.
 * great ideas can come from anywhere, and we want Mozilla to benefit from that.


 We hold each other accountable:

 * we intervene when we see violations
 * we help to deescalate situations, or escalate them up as warranted.
 * we help protect persons of reduced power and privilege, and actively encourage their contributions
 * we are all custodians of the space.


 When we talk, we:

 * assume positive intent
 * remember that the internet can amplify the effects of harsh speech, and cause communication problems, due to language barriers, cultural differences, internet hiccoughs and other reasons.  
 * remember that everyone has feelings
 * argue about technical problems without personal insult
 * understand that decisions get made that we don't agree with.  Sometimes these decisions are wrong.  
 * (more stuff from the Ubuntu CoC? or maybe irc guidelines?)

 Escalation:

 There are several processes for resolving conflicts, but ultimately the final stop is with 
 Mitchell.  

 *  governance
 *  channel maintainers
 *  (etc?)
 *  if there is a problem with any of this, email [email protected] .   


 Notes:
 ------------

 Mozilla spaces include but are not limited to: online activity in all sites in *.mozilla.com|org, all mozilla corporate office locations,
 and events funded or staffed primarily by Mozilla employees or contributors acting on behalf
 of the Mozilla project.

 These same code applies to people acting in official capacities on behalf of Mozilla.


 Suggested readings (in English):

 * knapsack?
 * irc guidelines?
 * nt statements?


 Alternatives to this:
	(this is a bit fragmentary. My goals:
	* some mix of aspiration and operational
	* I don't care what people believe, only how they act in the rooms
	* I want acknowledgement of impact, and feelings.
	* we might lose people over this. That doesn't make this not worthwhile
	* The person impacted has agency to decide the impact on them.
	)


	Big principles:

	* mutual accountability
	* respectful discourse
	* welcoming openness and encouragement of contributions from everywhere (phrasing?)
	* separation of personal speech from mozilla speech

	We want Mozilla spaces to be splendid, respectful, and productive.

	In Mozilla spaces we agree:

	* there is no normal brain, or right country of birth, language, correct gender, sexuality, or religion. These are all parts of normal human variation.
	* no one starts as an expert, and no one was born with a keyboard in their hand. We help build the inexperienced up with skills and encouragement.
	* all contributors are welcome, and their work is welcome.
	* the value of a contribution is completely independent of the race, gender, sexuality, physical ability, (etc.)
	citizenship status, etc. of the contributor, and should be evaluated accordingly.
	* to hold each other accountable for violations of these code.
	* power comes in many forms.
	* great ideas can come from anywhere, and we want Mozilla to benefit from that.


	We hold each other accountable:

	* we intervene when we see violations
	* we help to deescalate situations, or escalate them up as warranted.
	* we help protect persons of reduced power and privilege, and actively encourage their contributions
	* we are all custodians of the space.


	When we talk, we:

	* assume positive intent
	* remember that the internet can amplify the effects of harsh speech, and cause communication problems, due to language barriers, cultural differences, internet hiccoughs and other reasons.
	* remember that everyone has feelings
	* argue about technical problems without personal insult
	* understand that decisions get made that we don't agree with. Sometimes these decisions are wrong.
	* (more stuff from the Ubuntu CoC? or maybe irc guidelines?)

	Escalation:

	There are several processes for resolving conflicts, but ultimately the final stop is with
	Mitchell.

	* governance
	* channel maintainers
	* (etc?)
	* if there is a problem with any of this, email [email protected] .


	Notes:
	------------

	Mozilla spaces include but are not limited to: online activity in all sites in *.mozilla.com\|org, all mozilla corporate office locations,
	and events funded or staffed primarily by Mozilla employees or contributors acting on behalf
	of the Mozilla project.

	These same code applies to people acting in official capacities on behalf of Mozilla.


	Suggested readings (in English):

	* knapsack?
	* irc guidelines?
	* nt statements?


	Alternatives to this: