For every release, we share a thank you list of contributors. For example, see "Contributors to 1.14.0" here: Announcing Rust 1.14 | Rust Blog
To calculate this info, I have to run some git commands on my local checkout of Rust. That's kind of annoying, but there's something worse: this only tracks commits to rust-lang/rust. People who work on Cargo don't get credit. People who work on the nursery don't get credit. Etc. This is really unfair. We should be making sure to give thanks to everyone who works on the project as a whole.
I've wanted to rectify this for a long time; well over a year. I finally actually found some time and did it, though. That's thanks.rust-lang.org.
Now, there's a few things:
The code is kind of a mess. It's using raw hyper master, with tokio.
it uses nightly for now. with 1.15 it will be on stable; macros 1.1 is the only feature flag.
If you're interested in helping me whip this into shape, please jump on the issue tracker, I'd love to have some help! There's still a lot of easy issues to knock out.
EDIT: oh, and one more thing. If you see yourself listed twice, or not listed at all, please either open an issue or send me a PM in some form; we can take care of that. I've already found one or two things...
Technically, bors only adds one commit per PR. So if folks start sending PRs with thousands of commits, anyone could race to the top. Then perhaps bors will defend itself by squashing merges...
More seriously, is there anyway to track other github activity as a separate metric? Filing issues, opening PRs that get closed, and even just adding comments are all still valuable ways to contribute without adding to the commit count.