On Thu, 4 Jul 2019 at 18:53, Brett Cannon brett@python.org wrote:
Did not commit/author beyond a 3 month time span from first commit/authorship to last commit/authorship and their last commit was more than two years ago (helps cover people we don't have good records for in terms of sprints or GSoC who never got involved)
Hmm... I may be a bit dense, but I don't understand that sentence :-S
Let's say someone made all of their commits from 2015-07-04 to 2015-10-04 (and when I say "commits" I mean committing or authoring in git terms). That means they committed over a span of less than 3 months over the entire history of the cpython repo and that the last commit was more than 2 years ago. In that instance I'm suggesting we drop the person as chances are they were probably a GSoC student or a sprinter who tried things out but quickly walked away.
Or put another way, I'm arguing that if you spent less than 3 months making commits to cpython over two years ago you were probably not someone who got promoted to being a core developer through the normal promotion process.
I may fall under this category, as I don't actually commit much to the cpython repo. But I would very much like to continue being considered as a "core developer". As I understand it, my saying so here should be sufficient for that to happen (I will say so again when the actual lists come out, if it turns out I'm right). If there's anything else that I'd need to do in order to stay on the list, can it be clarified what that is?
Paul