Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

2017-01-22 Thread Barry Warsaw
On Jan 22, 2017, at 10:26 PM, Paul Moore wrote: >Will we be moving to the github issue tracker No. I think a lot of us still prefer Roundup and a significant amount of work is being done to integrate our Roundup instance with GH. >(Or at least have some means of scanning issue emails to quickly

Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

2017-01-22 Thread Paul Moore
On 22 January 2017 at 21:59, Barry Warsaw wrote: > On Jan 22, 2017, at 12:22 PM, Brian Curtin wrote: > >>I've been on the sidelines for a while myself for a number of reasons, >>but the shift to GitHub will pull me back in for sure, at least in >>terms of code review. I look forward to actually co

Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

2017-01-22 Thread Barry Warsaw
On Jan 22, 2017, at 12:22 PM, Brian Curtin wrote: >I've been on the sidelines for a while myself for a number of reasons, >but the shift to GitHub will pull me back in for sure, at least in >terms of code review. I look forward to actually contributing code >again soon, but easier tooling on revie

Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

2017-01-22 Thread Brian Curtin
I've been on the sidelines for a while myself for a number of reasons, but the shift to GitHub will pull me back in for sure, at least in terms of code review. I look forward to actually contributing code again soon, but easier tooling on reviews—rather, a shiny new one, as I'm aware of Reitveld—is

Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

2017-01-22 Thread Tal Einat
Dormant core dev here. Not contributing at all due to severe lack of time in the past year and a half, not likely to have more time in the near future. Also no longer working with Python at all except as a hobby :( I could pull off a review once a month if it would actually help! On Sat, Jan 21,

Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

2017-01-22 Thread Brett Cannon
What I'm picking up from this is (as a gross oversimplification): * Victor _wants_ code reviews * Raymond thinks we _need_ code reviews So the common theme here regardless of whether you agree with Raymond or Victor's approach to development is that we are not getting enough code reviews to go ar

Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

2017-01-22 Thread INADA Naoki
I read this whole thread. Here is my opinion. 1. Lack of reviewers It's really problem. If well written patch is not reviewed and committed for long time, patch writer (core developer, or potential core developer) may lost their motivation. Motivated contributor will be lower and lower. I wro