Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

[Raymond Hettinger]

> On Mar 31, 2017, at 2:40 PM, Brett Cannon  wrote:
> 
> In the (long) discussion of https://github.com/python/core-workflow/issues/6, 
> Wes Turner began to do his usual posting of lists. People pointed out he was 
> stepping out of line by being somewhat off-topic and seemingly lecturing 
> folks. He posted some of his lists again and then I warned him that if he did 
> it again I would block him for a CoC violation since he did not want to 
> respect anyone's time by taking the time to edit what amount to dumping his 
> personal notes on GitHub. (This is a long-standing issue, BTW, with Wes where 
> he has been warned in other settings like distutils-sig about his posting 
> behaviour.)

FWIW, this may just be his communication style that reflects his tooling 
(probably emacs org-mode or some such) and his way of thinking about problems.  
Even his personal web page looks like all of his posts:  
https://westurner.org/pages/resume  So I don't think he was trolling, it is 
possible that this is just who he is and may not be something he can easily 
switch-off.

I don't want to second guess the decision, but we've had a lot worse issues 
than "being somewhat off-topic and seemingly lecturing folks" or "not taking 
time to edit".  To me, blocking him seems a bit extreme especially for someone 
who has been a part of the Python community for a number of years.

I haven't followed many of his posts (which do seem somewhat odd and not 
entirely coherent), so I don't possess all the facts, so perhaps this was the 
right thing to do.

That said, I would like to remind everyone that when the diversity statement 
and code-of-conduct were approved, it was done with the understanding that the 
primary goal was to be an open and welcoming community that emphasized 
tolerance of just about everything from gender identity to neuro-diversity and 
Aspergers.  IIRC, both the diversity statement and CoC were toned down prior to 
approval, as a compromise with those who were concerned about them being turned 
into weapons of exclusion rather than tools for inclusion.

I did look at the referenced stream of posts, 
https://github.com/python/core-workflow/issues/6 . The contributions from Wes 
Turner did seem somewhat incoherent, disjointed, not useful, and perhaps a 
little annoying.  I didn't see anything overtly hateful or trolling that would 
rise to the level of a CoC issue (i.e. it hasn't created an environment that 
makes others feel unwelcome).

So, if Wes is to be blocked for a while, it should be on the basis of "adding 
too much noise to an important communication channel" rather than CoC which 
should be sparingly used for only egregious issues.  Also, if a real CoC issue 
does arise, I think any actions taken need to have multiple assents from a 
group of decision makers rather than having one person become a de-facto CoC 
czar with the power to banish people.

my-two-cents-ly yours,


Raymond Hettinger






___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] I have blocked Wes Turner from the Python org on GitHub

[Berker Peksağ]

On Sat, Apr 1, 2017 at 12:40 AM, Brett Cannon  wrote:
> In the (long) discussion of
> https://github.com/python/core-workflow/issues/6, Wes Turner began to do his
> usual posting of lists. People pointed out he was stepping out of line by
> being somewhat off-topic and seemingly lecturing folks. He posted some of
> his lists again and then I warned him that if he did it again I would block
> him for a CoC violation since he did not want to respect anyone's time by
> taking the time to edit what amount to dumping his personal notes on GitHub.
> (This is a long-standing issue, BTW, with Wes where he has been warned in
> other settings like distutils-sig about his posting behaviour.)
>
> Unfortunately he did it again for
> https://github.com/python/core-workflow/issues/66. Since GitHub only has
> organization-level blocks I have blocked him at that level (I've also
> already received some +1s from core devs while writing this email for my
> move, so I know others who have interacted with him also support this
> decision).

Thanks, Brett! I have set a filter to mark all of his emails as read
on several Python lists for a while.

--Berker
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Spurious bugs.p.o messages

[Terry Reedy]

On 3/31/2017 8:20 PM, Ezio Melotti wrote:

On Fri, Mar 31, 2017 at 3:59 PM, Terry Reedy  wrote:

On 3/31/2017 6:08 PM, Brett Cannon wrote:




On Fri, 31 Mar 2017 at 12:37 Victor Stinner > wrote:

2017-03-31 20:30 GMT+02:00 Antoine Pitrou >:
> Just a heads up that the following PR:
> https://github.com/python/cpython/pull/552/files
> has generated a lot of spurious PR additions on bugs.python.org
,
> probably because that PR references a lot of issues
> (example: https://bugs.python.org/issue23839).
>
> Perhaps it would be nice to have an upper limit on the number of
> notified issues when the PR mentions several of them?
>
> (I'm sure someone more active than me, such as Victor or Serhiy,
got *a
> lot* of notifications from that PR :-))

Hello, I got 110 emails, something goes wrong? :-)



Each link generated an email with a message like
"pull_requests: +994" but with a different number.



The range should be from pull_request826 to pull_request1113.
I tried to unlink a PR from the admin but it still generated an email.
I'm not aware of any method to unlink them without generating emails,
so If you don't mind another wave of emails, I can write a script to
go through them and unlink them from the issues, otherwise I'll just


I already unlinked for https://bugs.python.org/issue25464, and it did 
generate a message.  I would rather delete another 20 emails than leave 
the junk.


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Spurious bugs.p.o messages

[Ezio Melotti]

On Fri, Mar 31, 2017 at 3:59 PM, Terry Reedy  wrote:
> On 3/31/2017 6:08 PM, Brett Cannon wrote:
>>
>>
>>
>> On Fri, 31 Mar 2017 at 12:37 Victor Stinner > > wrote:
>>
>> 2017-03-31 20:30 GMT+02:00 Antoine Pitrou > >:
>> > Just a heads up that the following PR:
>> > https://github.com/python/cpython/pull/552/files
>> > has generated a lot of spurious PR additions on bugs.python.org
>> ,
>> > probably because that PR references a lot of issues
>> > (example: https://bugs.python.org/issue23839).
>> >
>> > Perhaps it would be nice to have an upper limit on the number of
>> > notified issues when the PR mentions several of them?
>> >
>> > (I'm sure someone more active than me, such as Victor or Serhiy,
>> got *a
>> > lot* of notifications from that PR :-))
>>
>> Hello, I got 110 emails, something goes wrong? :-)
>
>
> Each link generated an email with a message like
> "pull_requests: +994" but with a different number.
>

The range should be from pull_request826 to pull_request1113.
I tried to unlink a PR from the admin but it still generated an email.
I'm not aware of any method to unlink them without generating emails,
so If you don't mind another wave of emails, I can write a script to
go through them and unlink them from the issues, otherwise I'll just
leave them there. (It might be possible removing them from the db
directly using SQL without generating emails, but I'd rather avoid
touching the db).

>> No, it's a side-effect of having Misc/NEWS pasted as a comment into a PR
>> and the Roundup webhook thinking the issues were comments that warranted
>> connecting the PR with the issue.
>
>
> I consider this wrong ;-).
>
>>  Either we (a) don't worry about it as
>> people typically don't paste Misc/NEWS into a comment, (b) cap the
>> number of possible issues in a single webhook event, or (c) don't pick
>> up issue numbers from comments and only do it from PR titles.
>

I think adding a limit makes sense: 10 issues should probably be
enough, even for meta-issues.
I already started working on a patch, but I'm still thinking what's
the best way to implement it (e.g. limit it to the title only, to
individual messages, to all messages, etc.).

>
> (c), at least until we discover that there is something that needs to
> automated about numbers.
>
> What I would like is that the BPO issue # in the PR title be a link so it is
> easy to jump from PR to BPO.
>

There are some discussion about it, I think on the core-workflow issue tracker.
I'm not up to date, but last time I looked into it the title couldn't
be changed, but it should be possible to use a bot to convert the
issues to links in the message body.  Berker also made a browser
extension[0] that can be used in the meanwhile.

Best Regards,
Ezio Melotti

[0]: https://github.com/berkerpeksag/cpython-bpo-linkify

> --
> Terry Jan Reedy
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Spurious bugs.p.o messages

[Terry Reedy]

On 3/31/2017 6:08 PM, Brett Cannon wrote:



On Fri, 31 Mar 2017 at 12:37 Victor Stinner > wrote:

2017-03-31 20:30 GMT+02:00 Antoine Pitrou >:
> Just a heads up that the following PR:
> https://github.com/python/cpython/pull/552/files
> has generated a lot of spurious PR additions on bugs.python.org
,
> probably because that PR references a lot of issues
> (example: https://bugs.python.org/issue23839).
>
> Perhaps it would be nice to have an upper limit on the number of
> notified issues when the PR mentions several of them?
>
> (I'm sure someone more active than me, such as Victor or Serhiy,
got *a
> lot* of notifications from that PR :-))

Hello, I got 110 emails, something goes wrong? :-)


Each link generated an email with a message like
"pull_requests: +994" but with a different number.


No, it's a side-effect of having Misc/NEWS pasted as a comment into a PR
and the Roundup webhook thinking the issues were comments that warranted
connecting the PR with the issue.


I consider this wrong ;-).


 Either we (a) don't worry about it as
people typically don't paste Misc/NEWS into a comment, (b) cap the
number of possible issues in a single webhook event, or (c) don't pick
up issue numbers from comments and only do it from PR titles.


(c), at least until we discover that there is something that needs to 
automated about numbers.


What I would like is that the BPO issue # in the PR title be a link so 
it is easy to jump from PR to BPO.


--
Terry Jan Reedy


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Spurious bugs.p.o messages

[Brett Cannon]

On Fri, 31 Mar 2017 at 12:37 Victor Stinner 
wrote:

> 2017-03-31 20:30 GMT+02:00 Antoine Pitrou :
> > Just a heads up that the following PR:
> > https://github.com/python/cpython/pull/552/files
> > has generated a lot of spurious PR additions on bugs.python.org,
> > probably because that PR references a lot of issues
> > (example: https://bugs.python.org/issue23839).
> >
> > Perhaps it would be nice to have an upper limit on the number of
> > notified issues when the PR mentions several of them?
> >
> > (I'm sure someone more active than me, such as Victor or Serhiy, got *a
> > lot* of notifications from that PR :-))
>
> Hello, I got 110 emails, something goes wrong? :-)
>

No, it's a side-effect of having Misc/NEWS pasted as a comment into a PR
and the Roundup webhook thinking the issues were comments that warranted
connecting the PR with the issue.  Either we (a) don't worry about it as
people typically don't paste Misc/NEWS into a comment, (b) cap the number
of possible issues in a single webhook event, or (c) don't pick up issue
numbers from comments and only do it from PR titles.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] I have blocked Wes Turner from the Python org on GitHub

[Brett Cannon]

In the (long) discussion of https://github.com/python/core-workflow/issues/6,
Wes Turner began to do his usual posting of lists. People pointed out he
was stepping out of line by being somewhat off-topic and seemingly
lecturing folks. He posted some of his lists again and then I warned him
that if he did it again I would block him for a CoC violation since he did
not want to respect anyone's time by taking the time to edit what amount to
dumping his personal notes on GitHub. (This is a long-standing issue, BTW,
with Wes where he has been warned in other settings like distutils-sig
about his posting behaviour.)

Unfortunately he did it again for
https://github.com/python/core-workflow/issues/66. Since GitHub only has
organization-level blocks I have blocked him at that level (I've also
already received some +1s from core devs while writing this email for my
move, so I know others who have interacted with him also support this
decision).
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Spurious bugs.p.o messages

[Victor Stinner]

2017-03-31 20:30 GMT+02:00 Antoine Pitrou :
> Just a heads up that the following PR:
> https://github.com/python/cpython/pull/552/files
> has generated a lot of spurious PR additions on bugs.python.org,
> probably because that PR references a lot of issues
> (example: https://bugs.python.org/issue23839).
>
> Perhaps it would be nice to have an upper limit on the number of
> notified issues when the PR mentions several of them?
>
> (I'm sure someone more active than me, such as Victor or Serhiy, got *a
> lot* of notifications from that PR :-))

Hello, I got 110 emails, something goes wrong? :-)

Victor
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Spurious bugs.p.o messages

[Antoine Pitrou]

Hello,

Just a heads up that the following PR:
https://github.com/python/cpython/pull/552/files
has generated a lot of spurious PR additions on bugs.python.org,
probably because that PR references a lot of issues
(example: https://bugs.python.org/issue23839).

Perhaps it would be nice to have an upper limit on the number of
notified issues when the PR mentions several of them?

(I'm sure someone more active than me, such as Victor or Serhiy, got *a
lot* of notifications from that PR :-))

Regards

Antoine.
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/