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 have
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
> s
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 oth
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 b
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 wrot
On 20Sep2018 1539, Antoine Pitrou wrote:
Is there a summary of the sprints somewhere or is it planned to post one
somewhere? It would be more to read a bit more about the discussions
that took place.
Currently debating the contents of the high-level blog post among those
who were there. Once
Le 21/09/2018 à 00:35, Ethan Furman a écrit :
> 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
>> si
Le 21/09/2018 à 00:35, Ethan Furman a écrit :
>
> 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 ba
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 th
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 PSF
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 third-
> 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 à 22:33
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 cho
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 extr
Zachary Ware wrote:
>
> Most of my effort this week has gone into improving the state of
> buildbot.python.org, which has largely gone into improving Buildbot
> itself. Here are the relevant highlights:
>
> [snip]
Those are important improvements! I'm really happy buildbot appears to
be receiving
Raymond Hettinger wrote:
>
> At the developer sprints this week, we collectively decided to grant core
> committer status to Emily and Lisa.
Welcome aboard! Glad to have you with us :)
___
python-committers mailing list
python-committers@python.org
http
Hi all
Just a heads-up that the Azure Pipelines build failures for Linux
machines are a known issue that should be fixed by the end of the week.
It seems the service has become so popular since last week's
announcements that many more builds are being run on machines that have
been freshly i
On Sat, 15 Sep 2018 at 05:28, Raymond Hettinger
wrote:
>
> At the developer sprints this week, we collectively decided to grant core
> committer status to Emily and Lisa.
Congratulations, and welcome!
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
___
On Sat, 15 Sep 2018 at 07:02, Zachary Ware wrote:
>
> Hi all,
>
> Most of my effort this week has gone into improving the state of
> buildbot.python.org, which has largely gone into improving Buildbot
> itself.
[snip]
Very nice!
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Bri
20 matches
Mail list logo
