summaryrefslogtreecommitdiff
path: root/code-of-conduct.txt
Commit message (Collapse)AuthorAge
* Incorporate new preamble from doveGravatar Jonathan Reed2014-02-25
|
* Wordsmith apology paragraphGravatar Jonathan Reed2014-02-14
| | | | | | Add suggestion from dwilson to change wording to "...qualify your apology" to clarify that it's not the literal phrasing that's important, but rather avoiding "#sorry #notsorry"
* Add closing paragraph about learning from mistakes.Gravatar Jonathan Reed2014-02-14
| | | | Incorporate suggestions from dwilson. "The more you know..."
* Clarify that "well actually" is about nitpickingGravatar Jonathan Reed2014-02-14
| | | | Incorporate suggestions from dwilson
* Add sentence to pre-ambleGravatar Jonathan Reed2014-02-14
| | | | | Incorporate suggestion from dwilson that the one of the document's goals is to identify off-putting behavior
* Clean up apologies sectionGravatar Jonathan Reed2014-02-11
| | | | | | | Rephrase in more positive manner. Incorporate suggestions from jhawk so as to clarify exactly what type of apologies we're talking about and why.
* Re-phrase rule in a more positive mannerGravatar Jonathan Reed2014-02-11
|
* Clean up "well-actually" section.Gravatar Jonathan Reed2014-02-11
| | | | | | | Move footnote about the origins of the term to be a footnote. (inline note breaks up the flow). Incorporate suggestions from jhawk and zhangc to clarify this point.
* Wordsmith "feigning surprise" sectionGravatar Jonathan Reed2014-02-11
| | | | | | Incorporate suggestions from jhawk to clarify that we're talking about deliberate overreactions, and not genuine surprise, but the latter can still make people feel bad
* Move "perfection not required" paragraph to the beginningGravatar Jonathan Reed2014-02-11
| | | | | I feel this sets a good tone for the document, which is that we're all imperfect. It also no longer begins the document with a "No...." principle
* Clarify part on -ismsGravatar Jonathan Reed2014-02-11
| | | | | | Note that issues of sexism may not be directed at specific individuals (e.g. a group of people in the office rating women on okcupid), and that in these situations, it's important for anyone to speak up
* Rewrite the end section; clarify enforcementGravatar Jonathan Reed2014-02-11
| | | | | | | | | | | | | | | | | | | | | Incorporate suggestions from dove and others to clarify how enforcement will work. Hopefully this section now communicates that this will be largely community enforced, but will not preclude anyone who has been hurt by a "violation" of these rules from coming to the EC for assistance. The goal is to make it clear that there are not specific punishments for each instance of "well-actually" or "Sorry but not sorry", but simultaneously not in any way deny the EC the power to take action against any SIPB member or propsective who is making the office an unwelcoming (or even hostile) environment. Third parties are encouraged to talk to the recipient first, but should still feel empowered to speak up if necessary. (e.g. If $X says something sexist to $Y, and $Y doesn't react, but $Z also was upset by the sexist comment, $Z should feel free to speak out.) The last sentence in the penultimate paragraph is deliberately the same as in the paragraph above it.
* Add quote in well-actually sectionGravatar Jonathan Reed2014-02-10
| | | | | Incorporate quote from iannucci to better illustrate why a well-actually may not have the intended effect.
* Change title to 'principles', update preambleGravatar Jonathan Reed2014-02-10
| | | | | | | | | Incorporate suggestions from tboning and others to change the title to something other than rules, but which still emphasizes that these are important shared beliefs. Incorporate suggestions form achernya and others to remove any negative phrasing from the preamble.
* Initial version of code of conductGravatar Adam Glasgall2014-02-10