On Tue, 23 Apr 2019 at 17:19, Richard Yao <[email protected]> wrote:
> On 4/22/19 4:13 PM, Matthew Ahrens wrote:
> > The proposed code of conduct is available here:
> > http://www.open-zfs.org/wiki/Code_of_Conduct_Summary
> The following sentence is overly broad:
>
> "In addition, conduct outside these spaces may affect a person's ability
> to participate within them."
>
> It would be better if it said:
>
> "In addition, conduct in professional settings outside these spaces may
> affect a person's ability to participate within them."
>
> The way that it is presently worded risks creating different
> interpretations of what the scope of the CoC is. That could cause the
> project to be asked to police situations where the CoC is out of scope.
> Saying that a situation is out of scope in such situations would invite
> accusations of selective enforcement, which we don't need.

I think it's tempting to try and treat a document like this as an
algorithm, but it's really not.  Inserting "professional settings" in
this sentence merely invites people to quibble about what constitutes
a professional setting. My home is not a professional setting, and nor
is a public library or a bar; if I was being harassed in any of those
places by a member of the community it would be no comfort that it had
occurred outside of a workplace.

People should feel confident that issues they report will be heard,
not dismissed on a technicality.

> If we later find that this change made the CoC too narrow, then we can
> always revise it to address the situation in an environment that is
> amicable. Wording the CoC in a way that we later find that it was too
> broad might not give us quite as amicable an environment for revision.

I think the document is quite good as it is.  The team of people
responsible for fielding reports are responsible folk, and they've
outlined a process for amending the language later if needed.

Reports under a code of conduct are always delicate matters.  I think
keeping the language broad -- and uncomplicated! -- allows the team to
exercise their discretion as they seek to treat people fairly, while
preserving the safety and privacy of community members.


Cheers.

-- 
Joshua M. Clulow
Engineer @ Joyent
http://blog.sysmgr.org

------------------------------------------
openzfs: openzfs-developer
Permalink: 
https://openzfs.topicbox.com/groups/developer/T5dc11696c7b4bddb-Mc2796e4de761a7c5e9ae871a
Delivery options: https://openzfs.topicbox.com/groups/developer/subscription

Reply via email to