Code of Conduct

[Colin Clark]

Justin,

This is a perfect summary of the conversation so far, thank you! I also love this quote from earlier in your email:

"We don’t have to agree with it, we don’t have to accept it, but the process of understanding the alternate perspective will provide us greater insight into the basis for those perspectives as well as to test and strengthen our own."

To me, this is a crucial part of critique, and consistent with the inclusive critique strategies I've been thinking about—recognize, amplify, critique and transform.

The only other bullet point I might want to add to your list is this:

* Try to adopt a code of conduct, if possible, that people are already familiar with so that there is less need to explain, justify, reiterate, or bikeshed the expectations if possible. We might want to add a little addendum or addition if we feel it's necessary for our unique environment.

Thanks again,

Colin


> On Feb 10, 2017, at 11:03 AM, Justin Obara <obara.justin at gmail.com> wrote:
> 
> I’m going to attempt to summarize the values people have expressed in the thread, please feel free to clarify any parts and add anything that was missed. And of course, to continue this with ones that have yet to be covered.
> 
> a living document
> has a section that is clear about expected behaviour
> has a section that is clear about unacceptable behaviour
> examples give the reader a sense of what is considered positive behaviour and what is not
> deals with both digital and physical interactions
> inclusive of the many types of resources we collaborate on, including design artifacts and conversations, etc.
> ensure that our community is inviting to those who have experienced marginalization or inequality in other contexts or communities
> participate in a larger movement among open source communities to more clearly affirm inclusive values
> our community should be open to conversation and discussion
> inclusive spaces always need to include room for mistakes, cultural differences, perspective mismatches, rough patches, lots of listening, and different levels of familiarity with the issues at stake in community engagement
> a code of conduct shouldn't be used to short-circuit the "fertile muck" of diversity
> not a prescriptive set of rules
> a description of shared community responsibilities, a voicing of support, and a general outline of the kinds of behaviours that may put the community at risk
> a reminder that there is something real at stake when someone consistently behaves in an aggressive or harassing way

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20170210/bf18411a/attachment.html>