Code of Conduct

[Tony Atkins]

Thanks, Colin:

This is looking good.  There's still an "INSERT EMAIL ADDRESS HERE" bit
late in the doc that I'm guessing should be replaced with the new
advocacy at lists.fluidproject.org address.

Cheers,


Tony

On Thu, Mar 16, 2017 at 9:01 PM, Clark, Colin <cclark at ocadu.ca> wrote:

> Hi all,
>
> Now that we've had a month or so to contemplate the many issues involved
> in adopting a code of conduct in our community, I've written up a wiki page
> that summarizes our discussion and the proposed Contributor Covenant CoC:
>
> https://wiki.fluidproject.org/display/fluid/Inclusion+in+
> the+Fluid+Community
>
> Are people comfortable going ahead with making a decision about adopting
> this code of conduct? In the wiki page, I've tried to reflect the values we
> all articulated in thread, so now seems like a good time to focus on
> concrete issues. If you have further ideas, please feel free to respond
> with specific suggestions and proposals.
>
> Colin
>
> ---
> Colin Clark
> Lead Software Architect,
> Inclusive Design Research Centre, OCAD University
> http://inclusivedesign.ca
>
> On Feb 13, 2017, at 6:05 PM, Gill, Avtar <agill at ocadu.ca> wrote:
>
> Hi all,
>
> Just finished going through this thread and really appreciate the
> feedback. The latest version of the CoC originally proposed seems to
> summarize values and acceptable behaviour that I would expect (hopefully)
> in other communities. It's also reassuring to see so many other projects
> listed as adopters. Are there any concerns regarding the language used in
> the document or other aspects of it? If so could those be discussed here or
> in a design crit/community meeting? If there aren't any concerns then are
> there any objections to adopting this CoC, working on the policy and
> procedures document, and augmenting the CoC as time goes on? It sounds live
> it's going to be a living document anyway and since it's versioned,
> potential changes could be contributed back as well.
>
> Thoughts?
>
> Avtar
>
>
> On Feb 10 2017, at 5:23 pm, Ayotte, Dana <dayotte at ocadu.ca> wrote:
>
>> Hi All,
>>
>> A really interesting discussion! For now I wanted to share a couple of
>> thoughts.
>>
>> I’d like to suggest that when we do create our code of conduct we include
>> something in our list of “expected behaviours” that encourages us to call
>> each other out on unacceptable behaviour. And by calling each other out I
>> specifically mean, those of us with relatively more privilege and power
>> calling out the behaviour of our peers with same. I imagine that in some
>> cases, a simple “hey, that’s not OK”, stated publicly, may be all that is
>> needed to “enforce” good conduct.
>>
>> Regarding how we define the boundaries of the “community space” within
>> which our code applies, I thought of a recent experience of mine in which
>> an #a11y-tagged tweet linked to a related blog post, which I found really
>> quite harmful in terms of being at odds with inclusive practice. It wasn’t
>> directed at me or at a particular group in any overt way, but its content
>> most certainly reinforced the male-dominated and often sexist culture of
>> tech. It really got me wondering about the scope of our responsibility,
>> especially as leaders in this field. Of course we have to draw some
>> boundaries to formally define the scope of our CoC; beyond that we can
>> choose to hold ourselves to a high standard of inclusion in everything we
>> do.
>>
>> And though it’s been touched on in this thread already, I want to add
>> that I think it’s really important to distinguish between something that is
>> personally offensive, and something that is in fact harmful because it
>> reinforces existing inequality. Too commonly, the the latter gets dismissed
>> as the former. Perhaps we can somehow address this in our CoC.
>>
>> Thanks!
>>
>> Dana
>>
>> On Feb 10, 2017, at 10:39 AM, Colin Clark <colinbdclark at gmail.com> wrote:
>>
>> 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
>>
>>
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
>> To unsubscribe, change settings or access archives,
>> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>>
>>
>> _______________________________________________________
> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>
>
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at lists.idrc.ocad.ca
> To unsubscribe, change settings or access archives,
> see http://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20170317/035679dd/attachment.html>