On 9/21/2018 6:55 AM, Christian Heimes wrote:
I don't understand why you are drawing the reverse conclusion here. Can
you give me one concrete example, in which a French, German, or any
other non-US American taboo was violated and not counteracted with swift
reaction?
Are you talking about
On Fri, Sep 21, 2018 at 7:07 AM Antoine Pitrou wrote:
>
> I don't know of specifically French linguistic taboos, so I'm unable to
> answer this. French culture generally doesn't ban words wholesale, even
> when used in quotes. The very idea that you can't *quote* something
> despicable is
On Thu, 20 Sep 2018 at 21:37, Antoine Pitrou wrote:
>
>
> Apparently it's this one:
> https://mail.python.org/pipermail/python-ideas/2018-September/053482.html
>
> By the way, regardless of this single case, I would like people to think
> of the broader issue we're having. It's more than a
Le 21/09/2018 à 13:06, Christian Heimes a écrit :
>
> In my opinion it's both wrong and unfair to compare the ban with
> Anatoly's ban. For one we didn't have a process and general consent for
> bans.
AFAIK we still don't. I don't know where such a procedure is written
out, and I don't
Le 21/09/2018 à 12:55, Christian Heimes a écrit :
> On 21/09/2018 12.46, Antoine Pitrou wrote:
>>
>> Le 21/09/2018 à 02:06, Nathaniel Smith a écrit :
>>> Now sure, that taboo is an American thing, and I wouldn't support
>>> automatically banning someone who used it in genuine ignorance, was
>>>
On 20/09/2018 22.25, Antoine Pitrou wrote:
>
> Hi,
>
> I'm choosing to forward this to python-committers because I don't think
> python-ideas is a reasonable place to discuss CoC decisions.
>
> I think the action taken by Brett (apparently decided with Titus and a
> mysterious "conduct working
> On Sep 21, 2018, at 6:55 AM, Christian Heimes wrote:
>
> I don't understand why you are drawing the reverse conclusion here. Can
> you give me one concrete example, in which a French, German, or any
> other non-US American taboo was violated and not counteracted with swift
> reaction?
On 21/09/2018 12.46, Antoine Pitrou wrote:
>
> Le 21/09/2018 à 02:06, Nathaniel Smith a écrit :
>> Now sure, that taboo is an American thing, and I wouldn't support
>> automatically banning someone who used it in genuine ignorance, was
>> repentant when they realized what they'd done, etc.
>
>
Le 21/09/2018 à 02:06, Nathaniel Smith a écrit :
> Now sure, that taboo is an American thing, and I wouldn't support
> automatically banning someone who used it in genuine ignorance, was
> repentant when they realized what they'd done, etc.
So why are American taboos specifically forbidden, and
On 09/20/2018 05:47 PM, Brett Cannon wrote:
Which is why I'm hoping we can eventually get a clear enforcement guide written
for all the mailing lists and then have
a specific group of people manage all of these incident reports and deciding
how to handle them for consistency.
Otherwise we
On Thu, 20 Sep 2018 at 15:35 Ethan Furman wrote:
> On 09/20/2018 02:17 PM, Brett Cannon wrote:
>
> > I will also say I didn't voice an opinion or participate in the
> discussion on the conduct WG when deciding how to handle
> > it (beyond outlining our levels of escalation when handling these
>
On 09/20/2018 05:06 PM, Nathaniel Smith wrote:
On Thu, Sep 20, 2018 at 3:35 PM, Ethan Furman wrote:
And I have to argue against his use of the n-word* as being part of the
reason -- he wasn't calling anybody that, he was using the word as an
example of a taboo in one culture that is not in
On Thu, Sep 20, 2018 at 3:35 PM, Ethan Furman wrote:
> And I have to argue against his use of the n-word* as being part of the
> reason -- he wasn't calling anybody that, he was using the word as an
> example of a taboo in one culture that is not in others. Using that as part
> of the reason to
FWIW, as an American I don't think it's appropriate to spell out the
n-word in a mailing list, even if it's not being directed at anybody
or even just being used as an example. There's no need, and it can
only cause discomfort or worse.
--Chris
On Thu, Sep 20, 2018 at 3:35 PM, Ethan Furman
On 09/20/2018 02:17 PM, Brett Cannon wrote:
I will also say I didn't voice an opinion or participate in the discussion on
the conduct WG when deciding how to handle
it (beyond outlining our levels of escalation when handling these situations).
One thing missing from the ban notification is
On Thu, 20 Sep 2018 at 13:57 Donald Stufft wrote:
>
>
> On Sep 20, 2018, at 4:25 PM, Antoine Pitrou wrote:
>
> I think the action taken by Brett (apparently decided with Titus and a
> mysterious "conduct working group") is not the right one:
>
>
>
> Just FTR, the conduct working group is the
On Thu, Sep 20, 2018 at 4:37 PM Antoine Pitrou wrote:
>
>
> Apparently it's this one:
> https://mail.python.org/pipermail/python-ideas/2018-September/053482.html
After reading the original email I, personally, am in support of the
WG & Brett's decision.
I also think that we need a neutral
> On Sep 20, 2018, at 4:25 PM, Antoine Pitrou wrote:
>
> I think the action taken by Brett (apparently decided with Titus and a
> mysterious "conduct working group") is not the right one:
Just FTR, the conduct working group is the PSFs CoC Working Group, which I
believe had an open call for
Apparently it's this one:
https://mail.python.org/pipermail/python-ideas/2018-September/053482.html
By the way, regardless of this single case, I would like people to think
of the broader issue we're having. It's more than a single contentious
decision.
Regards
Antoine.
Le 20/09/2018 à
Is there a copy of the original email? (I'm not a regular python-ideas
reader)
Based on Brett's description though, the content sounds very far over the
line, and I wouldn't want to interfere with the WG's decision.
Alex
On Thu, Sep 20, 2018 at 4:25 PM Antoine Pitrou wrote:
>
> Hi,
>
> I'm
Hi,
I'm choosing to forward this to python-committers because I don't think
python-ideas is a reasonable place to discuss CoC decisions.
I think the action taken by Brett (apparently decided with Titus and a
mysterious "conduct working group") is not the right one:
- a definitive ban is an
21 matches
Mail list logo