Re: [python-committers] number of active core devs [was: Comments on moving issues to GitHub]

2018-06-02 Thread Nick Coghlan
On 3 June 2018 at 11:07, Guido van Rossum wrote: > Sounds to me like these are probably just past committers who are no > longer active for whatever personal reasons, and took no action when we > moved to GitHub. We basically never remove the commit bit from anyone > except by request, and I

Re: [python-committers] Comments on moving issues to GitHub

2018-06-02 Thread Brett Cannon
On Sat, 2 Jun 2018 at 14:58 Ezio Melotti wrote: > Hi, > > On Sat, Jun 2, 2018 at 10:26 PM, Brett Cannon wrote: > > > > > > On Sat, 2 Jun 2018 at 12:47 Mariatta Wijaya > > wrote: > >> > >> [SNIP] > >> > >>> 2. Better support for core developers in the tracker. > >> > >> > >> Not sure what you

Re: [python-committers] number of active core devs [was: Comments on moving issues to GitHub]

2018-06-02 Thread Guido van Rossum
Sounds to me like these are probably just past committers who are no longer active for whatever personal reasons, and took no action when we moved to GitHub. We basically never remove the commit bit from anyone except by request, and I only recall seeing one such request, ever. Some of them

Re: [python-committers] number of active core devs [was: Comments on moving issues to GitHub]

2018-06-02 Thread Donald Stufft
Is that a 50% reduction or is that just 50% of the people who could be active are? Sent from my iPhone > On Jun 2, 2018, at 8:33 PM, Ethan Furman wrote: > >> On 06/02/2018 12:46 PM, Mariatta Wijaya wrote: >> >> And perhaps this is to be discussed in a separate thread: even though in the >>

[python-committers] number of active core devs [was: Comments on moving issues to GitHub]

2018-06-02 Thread Ethan Furman
On 06/02/2018 12:46 PM, Mariatta Wijaya wrote: And perhaps this is to be discussed in a separate thread: even though in the b.p.o we appear to have 170 committers, really there are 90 core devs (people who has commit right to CPython on GitHub). and out of those 90, I think only about half

[python-committers] Comments on moving issues to GitHub

2018-06-02 Thread M.-A. Lemburg
Reading the comments in the thread and having used Github issues myself for a few years now, I find the idea of moving from a dedicated issue tracker we can easily customize to our needs (or hire someone to do so via the PSF) to a simplistic tracker add-on, which Github issues is, not a very

Re: [python-committers] Comments on moving issues to GitHub

2018-06-02 Thread Ezio Melotti
Hi, On Sat, Jun 2, 2018 at 10:26 PM, Brett Cannon wrote: > > > On Sat, 2 Jun 2018 at 12:47 Mariatta Wijaya > wrote: >> >> [SNIP] >> >>> 2. Better support for core developers in the tracker. >> >> >> Not sure what you mean by "support"? There are only two maintainers of the >> bug tracker, they

Re: [python-committers] Comments on moving issues to GitHub

2018-06-02 Thread Brett Cannon
On Sat, 2 Jun 2018 at 12:47 Mariatta Wijaya wrote: > [SNIP] > > 2. Better support for core developers in the tracker. > > > Not sure what you mean by "support"? There are only two maintainers of the > bug tracker, they both are also Python core developers: Brett and Ezio. My > personal opinion

Re: [python-committers] Comments on moving issues to GitHub

2018-06-02 Thread Mariatta Wijaya
> > "Old and languishing issues should just be closed / ignored" > I disagree with doing this blindly, and I would be mightily annoyed if > someone did so with IDLE issues and hide valuable ideas and code. Since you are IDLE's maintainer, I'll also be annoyed if other people except yourself (or

Re: [python-committers] Comments on moving issues to GitHub

2018-06-02 Thread Steve Dower
I think boards have improved since I last used them, but when I tried they added nothing but overhead. Possibly useful for planning, if we had someone who was responsible for that (maybe individual planning? But then you can’t really expect contributors to keep it up to date for you).