Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
MIME-Version: 1.0
Sender: sa3ruby@gmail.com
In-Reply-To: <CADmm+Kf15K=DPf+qWd1VJ5h3vqXU5rsGVLYiUpxO5xa5CJc3QQ@mail.gmail.com>
References: <pony-31e1cbf2b23a01ea035ee3323fe2ab95950c8284-61e7eaf44e4b0408223fd75cb5f0d601014778f0@dev.community.apache.org>
 <CADmm+KcKYsy5ocSHfUZMCxG0Wm_3bNX=F=H4TAo-e+n9q8fSFg@mail.gmail.com>
 <ec483eb9-8d44-bf47-286d-9632e827eb4c@apache.org> <CAPaJBx7vW2K1Ltd4VL566VjD2MuP1wF8c58b+d4wa2HNnPTFbw@mail.gmail.com>
 <CADmm+Kc0cH6KRtC3r4FtabD30sxMs6X+c=wfpjhMwERtcehr4g@mail.gmail.com>
 <CAPaJBx5qEgeVjdzsrRyxGUTx_hME69X8s+bt46H+Rss70=fFsw@mail.gmail.com>
 <0903d96d-78f7-bbfd-82a2-f55ecaf48467@acm.org> <CAPaJBx57+0ce_Fb8tNJnDLT8b4D5EgRXpTpr-pj4Bps5u8c6Pw@mail.gmail.com>
 <0e743e4e-1421-c8f3-3967-6836e5e042f3@apache.org> <CADmm+Kf15K=DPf+qWd1VJ5h3vqXU5rsGVLYiUpxO5xa5CJc3QQ@mail.gmail.com>
From: Sam Ruby <rubys@intertwingly.net>
Date: Tue, 15 Nov 2016 19:42:20 -0500
Message-ID: <CAFG6u8E=D1gKnzv5a41Nc29M-qzDUf7R_1ExwpwUUZP7FsO9PQ@mail.gmail.com>
Subject: Re: Encouraging Diversity - Update 6
To: Apache Community Dev <dev@community.apache.org>
Content-Type: text/plain; charset=UTF-8
archived-at: Wed, 16 Nov 2016 00:42:48 -0000

On Tue, Nov 15, 2016 at 7:23 PM, Niclas Hedhman <niclas@hedhman.org> wrote:
>
> And FTR, yes, I am obviously incredulous and ignorant enough to not see how
> any mechanism in the ASF setup causes or encourages bad behavior from
> individuals.

I do *NOT* believe that anybody has stated that.  I certainly didn't.
Misstating others positions is counterproductive.

> Shane asked me to not stand in the way[1] of people who wants to improve
> diversity, but I am concerned about that _enforcement_ of a Code of Conduct
> will be overused. Yes, I realize that is also without usecases, but Noah
> stated that I am (by asking for some examples) an example of not "feeling
> safe" and I imply from that this _enforcement_ could (maybe should) be
> struck down on me over this very thread, rather than educate me of what is
> so "thoroughly horrible". The "assume the best intentions" attitude seems
> to be slowly replaced by a "assume the worst intentions", and I think that
> too is worrisome, especially with an "enforcement", rather than
> "education", "promotion" and "leading by example" language in Sharan's
> proposal.

You correctly state that your concern is without use cases.

Recapping: the ASF does not cause bad behavior.  However as bad
behavior has and will continue to occur despite this, and as that bad
behavior harms our mission, it is the ASF's best interest to not
tolerate that behavior.

No set of rules will capture every possible bad behavior that could
possibly occur.  The most that we can do is state that such behavior
will not be tolerated, and to follow through.

Just like you have asked of others, I ask that you judge those that do
so based on actual enforcement, not based on your own personal worst
fears and interpretations of their intent.  If a Code of Conduct is
overused, please speak up.  Until that occurs (and every evidence we
have is that we collectively have taken great pains NOT to do so),
please respect that there is a very real problem that needs to be
addressed.

> Cheers
> Niclas
>
> [1] A really terrible argument, since you (Shane) would not have that
> attitude for a proposal to allow for GPL'd projects in the ASF. "Don't
> stand in the way for people who wants to improve licensing diversity...
> enforce the right to release under multiple licenses...".

And that is a really terrible attempt to describe a situation that
isn't remotely parallel to the topic at hand.

- Sam Ruby

> On Wed, Nov 16, 2016 at 4:32 AM, Mark Thomas <markt@apache.org> wrote:
>
>> On 15/11/2016 17:28, Noah Slater wrote:
>> > What are you looking for, exactly? I'm not sure what a "use-case" is in
>> > this context.
>> >
>> > We have a concrete example of what not to do in this very thread
>> already. I
>> > was contacted off-list by Niclas making it clear he expected me to
>> provide
>> > proof that would "convince" him that I wasn't trying to "breed" a "a
>> > cry-baby and victimhood culture".
>> >
>> > Is this really the sort of thing we want to tolerate when a member of
>> > community mentions that they've had bad experiences before. Is this sort
>> of
>> > thing the "inclusivity" and "welcoming-ness" we aim for?
>> >
>> > As it happens, I wasn't bringing up my bad experiences to make any
>> concrete
>> > point about what we should or should not do re policy, only to refute
>> > Niclas's nonsense idea that "safety" is not a word we should be using.
>>
>> I received a similar off-list e-mail and while the impression I got was
>> of a general tone of incredulity, I'm prepared to give Niclas the
>> benefit of the doubt and assume it was a poorly worded email and he is
>> trying to better understand something he has never experienced.
>>
>> To summarise what happened in my case:
>>
>> - A list member launched an islamophobic attack on another list member
>> that was way, way over the line (no need to look for it in the archives,
>> it was removed within minutes).
>>
>> - I responded saying such behaviour was completely unacceptable and that
>> I was removing that person from the mailing list.
>>
>> - I then received a series of e-mails over about 24 hours (it might have
>> been less - it was a while ago) that threatened me and my family.
>>
>> - Because I am involved in infra, I was able to to remove the original
>> email from the archives and ensure that the person making the threats
>> was not subscribed to any other ASF lists.
>>
>> - I took the threats seriously enough that I considered cancelling my
>> trip to an upcoming ApacheCon.
>>
>> - I contacted the ASF President who advised I contact local law
>> enforcement and who contacted the ASF lawyers for advice.
>>
>> - I reported the threats to local law enforcement and also my employer
>> (for various reasons including that I might need to cancel the trip they
>> had already paid for).
>>
>> - Local law enforcement responded that - due to the cross-border nature
>> of the threats and the unknown identity of the person threatening me -
>> they weren't going to do anything. In short, they'd need to jump through
>> lots of legal hoops to make progress and the threshold for doing so was
>> somewhere around the level of terrorism and the threats to me and my
>> family fell short of that. I wasn't particularly surprised at this.
>>
>> - I did some digging of my own and while I couldn't track down an ID, I
>> had enough of an idea about location that I concluded that the
>> likelihood of the person turning up at ApacheCon was very low so I went
>> ahead with my trip. I did however, take care to ensure I was with a
>> group of people as much as possible.
>>
>> Generally, I felt it was handled well by the ASF. It helped that I could
>> do most things that required concrete action myself because of my
>> involvement with infra.
>>
>> In terms of where there is scope for improvement, I think we need to
>> make list moderators more aware of the CoC and their options when there
>> are posts that go against the CoC. I also think we need to make our
>> communities in general more aware of the CoC and what to do if they have
>> concerns.
>>
>> Whether we need to formally document how to respond when people report
>> CoC issues is TBD. They are rare enough (I'm one of the PoCs and I
>> haven't received a report yet) that I don't have enough data to
>> determine if there is sufficient commonality for any sort of documented
>> process or whether each needs a custom approach. Someone like Ross who
>> has dealt with more of these is probably in a better position to comment.
>>
>> Mark
>>
>>
>> >
>> > On Tue, 15 Nov 2016 at 16:58 Patricia Shanahan <pats@acm.org> wrote:
>> >
>> >> On 11/15/2016 6:48 AM, Noah Slater wrote:
>> >> ...
>> >>> You want some sort of "record" to consume. Is a person, on a mailing
>> >> list,
>> >>> saying "hey this place was so bad for me I had to take a break" not
>> >>> evidence enough for you that something might be wrong?
>> >>>
>> >>> As for the rest of it, this org keeps records of every email sent to
>> the
>> >>> lists. It would not be hard for you to go looking for context if you
>> >> wanted
>> >>> it.
>> >>>
>> >>> Asking me to go over all that stuff again (which I find upsetting to
>> even
>> >>> think about) days after returning here hoping things would be nicer for
>> >> me,
>> >>> is, well, ... it's not particularly considerate.
>> >> ...
>> >>
>> >> I don't think asking you to go over something you found upsetting is
>> >> necessary. On the other hand, I have started looking at the mail
>> >> archives for your 2015 participation, and I don't think I have found the
>> >> right context, or if I have I am not recognizing it.
>> >>
>> >> Could you perhaps save some time by giving a pointer in terms of e.g. a
>> >> mailing list and topic?
>> >>
>> >> Or, if you prefer we not discuss your particular situation, could you
>> >> give a pointer to any use-case, in terms of mailing list and topic?
>> >>
>> >> This very discussion is an illustration of why "feeling" based standards
>> >> are a problem. Some people are not comfortable setting policies without
>> >> solid use-cases they can discuss and analyze. Others may not be
>> >> comfortable with discussion and analysis of those use-cases. How does
>> >> one accommodate both sets of feelings?
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> >> For additional commands, e-mail: dev-help@community.apache.org
>> >>
>> >>
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>>
>
>
> --
> Niclas Hedhman, Software Developer
> http://zest.apache.org - New Energy for Java

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org