CPython core team leaderboard

Activity covers all public repositories in the Python GitHub organization, including archived repositories and forks. The leaderboard still ranks the CPython core team, including triagers.

All adds closures, PRs opened, and reviews. Closures counts both closed issues and closed PRs, credited to GitHub’s closed_by actor. PRs counts PRs opened, credited to their author. Reviews awards one point per person per PR reviewed within the selected range, using the first qualifying submission in that range. Approvals, change requests, and submitted comment reviews count, including reviews later dismissed. Repeated reviews and alternate accounts on the same PR count once. Draft reviews, ordinary comments, reviews of your own PR, commits, and pushes do not earn review points. Reviewing and merging a PR earn one review point and one closure point. Each action is one point, so opening and closing the same PR counts as two actions, potentially for different people. Expanded lists show each item once, with its current status and the actions counted in this range.

Dates are inclusive. Closure counts use currently closed items whose latest closure falls in the range; reopened items are excluded. PR openings count regardless of their current state. Merged and unmerged PR closures and backports count. Ties share a rank.

Core developers come from the public CPython core-team log with a GitHub username and no departure date. Triagers come from the roster supplied for this sprint; overlapping members are counted once. Verified alternate accounts are combined into one person: jelle-openai counts toward JelleZijlstra. Bots and people outside these rosters are excluded; automated closures aren’t reassigned to a human. This is a fun sprint tally, and doesn’t measure collaboration, or the size of a contribution.