On 22 Jan 2017 11:26 pm, "Paul Moore" wrote:
One question (and apologies if this has been discussed on another list
somewhere) - my biggest bottleneck is the sheer number of python-bugs
emails, and the difficulty of identifying ones I can contribute. Will
we be moving to the github issue tracker
On Sat, Jan 21, 2017 at 9:51 PM, Brett Cannon wrote:
> 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 d
On Mon, 23 Jan 2017 at 11:50 Paul Moore wrote:
> On 23 January 2017 at 19:31, Brett Cannon wrote:
> > Do you want this to search issues or PRs by? Since the migration has not
> > happened yet there isn't any emerged practice yet of what will be
> labeled on
> > PRs and what will be kept on bpo (
On 23 January 2017 at 19:31, Brett Cannon wrote:
> Do you want this to search issues or PRs by? Since the migration has not
> happened yet there isn't any emerged practice yet of what will be labeled on
> PRs and what will be kept on bpo (e.g. we will more than likely label what
> versions of Pyth
On Sun, 22 Jan 2017 at 14:26 Paul Moore wrote:
> 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 lea
Excerpts from Brett Cannon's message of 2017-01-21 19:51:48 +:
> 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'
