Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread Terry Reedy
On 5/3/2017 1:25 PM, Brett Cannon wrote: On Tue, 2 May 2017 at 11:29 Terry Reedy > wrote: It would easier to move discussion to bpo if there were a clickable link from PR to bpo, just as there is in the opposite direction. I believe that there is a workfl

Re: [python-committers] Proposal for procedures regarding CoC actions

2017-05-03 Thread Guido van Rossum
Two ex-board members disagree. I have to side with Brian; the PSF board should have minimal say in how the developers develop. Note, I'm fine with the board being the arbiter when someone disagrees with their ban though -- there's got to be a "higher authority" for appeals. But I don't agree that

Re: [python-committers] Proposal for procedures regarding CoC actions

2017-05-03 Thread M.-A. Lemburg
Since this is a matter outside the realm of committers, the PSF board will have to ultimately decide on any actions taken. The committers can report issues to the board and provide information useful for their decisions, the bad actor also has to be given a chance to respond to allegations and be

Re: [python-committers] Proposal for procedures regarding CoC actions

2017-05-03 Thread Brian Curtin
On Wed, May 3, 2017 at 3:28 PM, Mariatta Wijaya wrote: > Hi, > > First of all, sorry for bringing up an old thread. > I know this is an uncomfortable topic, and I also wish that we can just > avoid it, but ... I think we gotta do something about it. > > I understand why Brett did what he did, and

Re: [python-committers] Proposal for procedures regarding CoC actions

2017-05-03 Thread Mariatta Wijaya
Hi, First of all, sorry for bringing up an old thread. I know this is an uncomfortable topic, and I also wish that we can just avoid it, but ... I think we gotta do something about it. I understand why Brett did what he did, and I support his decision. I do agree with Raymond's point, that going

Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread Brett Cannon
On Tue, 2 May 2017 at 11:29 Terry Reedy wrote: > On 5/2/2017 10:07 AM, R. David Murray wrote: > > On Tue, 02 May 2017 09:36:02 +0200, "M.-A. Lemburg" > wrote: > > >> IMO, it's much easier for everyone to just always point people > >> to BPO for discussions and keep PRs reserved for code reviews.

Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread Christian Heimes
On 2017-05-03 19:54, Brett Cannon wrote: > I just touched > up https://github.com/python/cpython/blob/master/.github/CONTRIBUTING.rst to > explicitly mention that only code review issues should be discussed on > GitHub. Thanks Brett! I followed Donalds' advice and just pushed a modification to .m

Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread Brett Cannon
I just touched up https://github.com/python/cpython/blob/master/.github/CONTRIBUTING.rst to explicitly mention that only code review issues should be discussed on GitHub. On Mon, 1 May 2017 at 15:32 Christian Heimes wrote: > Hi all, > > since our move to Github I noticed a major increase in inco

Re: [python-committers] No Travis-CI on OS X?

2017-05-03 Thread Brett Cannon
So Donald is right that the reason we don't have macOS builds through Travis is due to the fact that back in February they had a horrible backlog and added too much time to the total build. But as Alex pointed out, Travis has subsequently increased their macOS fleet and given the Python organizati

Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread Stefan Krah
On Wed, May 03, 2017 at 06:06:59PM +1000, Nick Coghlan wrote: > 5. Easy reactions: no native +1 support to avoid "Usenet nod syndrome" > without spamming folks following the issue All platforms (except maybe Stackoverflow) who have voting use +1 more in a "high five" sense than for actual agreemen

Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread Paul Moore
On 3 May 2017 at 10:30, M.-A. Lemburg wrote: > I don't think we should open a discussion of whether to move away > from bpo or not. Agreed... > The thread topic only refers to how we deal with > discussions which should be had on bpo rather than Github PRs > and I think we mostly agree that havi

Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread M.-A. Lemburg
I've had another look at some of the PRs we do have on Github and must say, that it seems we're discussing a problem which doesn't really exist predominantly on our PR tracker: https://github.com/python/cpython/pulls?page=2&q=is%3Apr+is%3Aopen I haven't checked all PRs, but the ones which have a

Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread Paul Moore
On 3 May 2017 at 09:18, Antoine Pitrou wrote: > > As for "native" +1 mentions in Github, I tend to find them unhelpful, as > I don't know why people say "+1" at all. So I usually ignore them. The point is that it's easier to ignore +1s in github, because they don't trigger notification emails, a

Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread Antoine Pitrou
Le 03/05/2017 à 10:06, Nick Coghlan a écrit : > On 3 May 2017 at 05:09, M.-A. Lemburg wrote: >> This doesn't have much to do with UX/UI. It's mainly a questions >> of culture. > > It's about the UI/UX for me, as Roundup is missing a few modern > collaboration features: > > 1. Easy user mentions

Re: [python-committers] Github reviews are cannibalizing BPO

2017-05-03 Thread Nick Coghlan
On 3 May 2017 at 05:09, M.-A. Lemburg wrote: > This doesn't have much to do with UX/UI. It's mainly a questions > of culture. It's about the UI/UX for me, as Roundup is missing a few modern collaboration features: 1. Easy user mentions: I can't just mention someone inline based on autocompletion