Code of Conduct

Thu Feb 9 19:45:45 UTC 2017

Thanks for sharing this.

I think in general I like the contributor-covenant. However, my initial gut
reaction is that it seemed code focused, despite using words like community
and contributor. I’m not 100% sure it addresses the breadth of work,
outreach, and etc that we do in our community. Maybe this is just a matter
of tone / presentation style.

I’m also not sure of our intended scope. Does it just cover fluid and fluid
related tasks? Will it be a requirement for all of our partners in the work
that we do? Is it meant to govern over every aspect of work at the IDRC
whether involving workshops, guests, visitors, etc? This may have an impact
on the enforcement and how that is structured, developed and etc. Perhaps
the enforcement model outlined in the contributor-covenant itself doesn’t
necessarily reflect how we can best address issues that arise in our
community.

In doing some quick googling for codes of conduct I came across "Why the
Open Code of Conduct Isn’t for Me
<http://dancerscode.com/blog/why-the-open-code-of-conduct-isnt-for-me/>"
that was posted as a response to a code of conduct adopted by GitHub. I
probably don’t completely agree with everything said there, and some of it
is specific to language used in a specific code of conduct, but it does
have some good points and things to think about.

Perhaps we need to take a step back and define what it is exactly that we
want for our community. Is it a set of rules to be strictly enforced, is it
a set of expectations and core values that we strive for, etc?

Thanks
Justin

On February 9, 2017 at 4:10:20 AM, Tony Atkins (tony at raisingthefloor.org)
wrote:

Hi, All:

This looks really promising, and I absolutely agree that our community
should champion these ideals as an important part of working in open
source.  To save everyone a couple of clicks, here's a direct link to the
latest version in HTML format:

http://contributor-covenant.org/version/1/4/

Before we can add this to our projects, we need at least some basic
agreement around this section of the document:

Instances of abusive, harassing, or otherwise unacceptable behavior may be
> reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
> complaints will be reviewed and investigated and will result in a response
> that is deemed necessary and appropriate to the circumstances. The project
> team is obligated to maintain confidentiality with regard to the reporter
> of an incident. Further details of specific enforcement policies may be
> posted separately.

The rest of our communication errs on the side of openness, in this case we
need to give incident reporters a safe space to raise concerns.  This means
that the group of incident responders needs to be small enough that it is
effectively confidential.  The incident responders group also needs to be
large enough that incidents are responded to in a timely fashion, and large
enough that the handling of an incident itself reflects some kind of
consensus.  We also need to have a clear process of managing that group
over time, perhaps similar to how committers are nominated, but with an
implicit term limit, rotation, voluntary retirement, or other means of
keeping the group small.

All of that is my opinion, feedback is encouraged and appreciated.
However, before we can post the covenant in our projects, we do at least
need an initial group and an email address.  As there is no core group at
the moment to start the nomination process (as we do with committers), I
propose an initial open nomination process within the community (i.e. on
this mailing list).

I'd also propose setting up the email as a private mailing list to which
anyone can post, but which only distributes to the responders.

Your thoughts welcome, very excited to see where this goes.

Cheers,

Tony

On Wed, Feb 8, 2017 at 11:23 PM, Michelle D'Souza <michelled33 at gmail.com>
wrote:

> Hey everyone,
>
> Codes of conduct have started to show up in a lot of open source
> communities as a very unfortunately result of discriminatory behaviour. As
> they have become more common, people often use the existence (or lack of) a
> code of conduct to decide whether or not they will participate in a
> community.
>
> Given that our community has always been open and welcoming and has
> inclusion at its core, it just makes sense to add a code of conduct to flag
> ourselves as such.
>
> This seems like it will suit our community very well (thanks Colin):
>
> http://contributor-covenant.org/
>
> If you know of one that you think would be a better fit - please let us
> know! Otherwise, let’s aim to add this next week.
>
> Thanks,
>
> Michelle
>
>
>
> _______________________________________________________
> 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/20170209/a3dfda87/attachment.html>