[python-committers] Re: Making it easier to track who is currently considered "active" for voting

2020-10-23 Thread M.-A. Lemburg
FYI: There's a ticket open to address the remaining missing parts of the process that is defined in PEP 13 vs. the what the voting script implements: https://github.com/python/voters/issues/16 I've implemented some extra logic to enable tracking the inactivity status as per PER 13 and creating a

[python-committers] Re: Making it easier to track who is currently considered "active" for voting

2020-10-20 Thread Brett Cannon
On Tue, Oct 20, 2020 at 3:07 PM Brett Cannon wrote: > > > On Tue, Oct 20, 2020 at 2:58 PM Nathaniel Smith wrote: > >> How are you measuring "activity"? Just commits? >> > > Same as it has always been since the voters repo has existed and we > automated any of this: you either committed or author

[python-committers] Re: Making it easier to track who is currently considered "active" for voting

2020-10-20 Thread Brett Cannon
On Tue, Oct 20, 2020 at 2:58 PM Nathaniel Smith wrote: > How are you measuring "activity"? Just commits? > Same as it has always been since the voters repo has existed and we automated any of this: you either committed or authored a change in the CPython repo. So you can either author a PR that

[python-committers] Re: Making it easier to track who is currently considered "active" for voting

2020-10-20 Thread Nathaniel Smith
How are you measuring "activity"? Just commits? On Tue, Oct 20, 2020 at 12:16 PM Brett Cannon wrote: > With the next SC election fast approaching, I did the final tweaks I > wanted to make to the voters repo to address visibility issues we had in > the last election. > > First, there is now a mo