Sam,
you are conflating the concerns. This is not ON/OFF logic, with a possibly
more than one dimension of shading and positioning one (relatively extreme)
case as the norm for how to interact, is not the way to deal with this.
(analogy; "Person killed in traffic. Ban all cars.")
Niclas
On Thu,
On Nov 17, 2016 04:03, "Noah Slater" wrote:
>
> He offered to copy the email to the list in the reply I was responding to.
Not directed toward you, but I had thought to bring this up a week or so
earlier when I first read their article and other hostile email traffic,
and the welcome plenary at A
He offered to copy the email to the list in the reply I was responding to.
:)
I can't resist pointing out the irony of you flagging my conduct on a
public list, in an email thread you started to criticise me for flagging
someones conduct on the same list. ;)
Also, I want to challenge your charact
I think you misinterpreted a couple things...
On Nov 17, 2016 02:18, "Noah Slater" wrote:.
>
> I quoted a chunk of an email that was sent to me privately because the
> person who sent it had already offered to copy it to the list. I saved him
> the trouble by excerpting the bit I wanted to remark
Agreed with Sam.
Saying "ignore it" ensures our communities will only be made up of people
who are hardy enough or privileged enough to be able to ignore such things.
We're not enforcing people's feelings of safety. Nor are we enforcing
people's happiness. Of course, we could never do that. They
On Wed, Nov 16, 2016 at 8:38 PM, Niclas Hedhman wrote:
>
> 3. IGNORE IT
>
> You don't have to read what other people write, you don't have to
> internalize it and you may convince others to do the same. For 20 years,
> this was the number one defense against trolls and poisonous people.
Strongly
On Thu, Nov 17, 2016 at 6:54 AM, Noah Slater wrote:
> Okay, back to the topic.
>
Ok, good.
> Perhaps we should update the code of conduct. It seems that a lot of the
> unease here relates to the nature of our planned responses to conduct
> infractions.
>
That is one part, the second is someth
The thread you're referencing contains a number of actionable, productive
suggestions. Indeed, mine and other's participation on that thread was an
attempt to counteract derailment.
I quoted a chunk of an email that was sent to me privately because the
person who sent it had already offered to cop
So I just sort of boggled at an post that seemed to quote private
correspondence while making a CoC accusation, or at least that's
what I think I read. Many of us know the holidays for the airing of
grievances arrives in 2 months, but public archived email lists
really are simply not the place. We
Okay, back to the topic.
Perhaps we should update the code of conduct. It seems that a lot of the
unease here relates to the nature of our planned responses to conduct
infractions.
I can tell you how I see it, as one of the people behind the work that went
into our code of conduct.
There are two
This is the last email I am going to send on the specifics of me not liking
the response I got on this thread. I have a follow-up email that will
hopefully get us back on topic.
Here's an excerpt of what you chose to email me privately:
> Now, you have claimed that you have been suffering from pr
On Wed, 16 Nov 2016, Rich Bowen wrote:
It would be great to have some kind of statistics on how GSoC helps
projects longer term. Do students stick around? Does the code written
actually get incorporated into releases? Does it in fact contribute to
the mission of Community Development, or is it
It would be great to have some kind of statistics on how GSoC helps
projects longer term. Do students stick around? Does the code written
actually get incorporated into releases? Does it in fact contribute to
the mission of Community Development, or is it just a nice summer job
for these students?
13 matches
Mail list logo
