Back to top

Contributors to Drupal 7.x - End of Code Freeze Edition

Last week was the amazing Do It With Drupal conference and Angela Byron wanted some updated contributor statistics for her presentation. So, I analyzed the commit messages for Drupal core to find who has been helping out and once again the process and the data are getting better and better.

This time I'm using direct database information from the cvs commit log tables and using PHP to parse it which means that it's easier to create rules for fixing usernames or eliminating bad data. I also pulled in company information from to get a rough sense of which companies, as a group, are contributing the most to Drupal core. AND, thanks to Dreditor the commit messages are getting cleaner and include information about the person who has done reviews on patches.

Remember, none of this data is really perfectly accurate, but it gives us a tangible sense of what is going on.

Attached are a CSV file and an spreadsheet with the data. They show the uid of the user from, their name, their organization (if they specified one), the number of times they were mentioned as an author of a patch, the number of times they were mentioned as a reviewer of a patch, and the commit ID where they were mentioned. The commit ID is useful when chasing down bad data so that I can improve the parser. So, if you find a problem please let me know the CID value so I can improve the parser. There's a chance that this could eventually make it onto itself, but I'd like to improve the process first to understand whether or not that makes sense.

Enough with the process - it's time to name names!

Top 10 patch contributors to Drupal 7 core

Username Patches
catch 267
sun 238
damien tournoud 213
chx 159
yched 150
dave reid 145
pwolanin 141
boombatower 113
c960657 93
People Involved: 

Rocky Mountain Independent: Stillborn? Unprofitable in spite of reduced layers/management?

In January I was sad, but not surprised, to see the Rocky Mountain News shut down. They made a cool video did some nice retrospective posts, and shut down the operations. Since then the Denver Post (which was kind of a part owner of the Rocky) has picked up some of the more popular journalists and probably some of the other staff.

So, some of the staffers, photographers and journalists got together and decided they were going to do things right. They weren't going to be driven by corporate greed like the evil capitalists, they were just going to do the news and make enough money to keep the business rolling. They created a site I Want My Rocky as a rallying point for the former employees of the news and as a place to gather interest in a proposed online-only pay-for-content news source.

Old Media: Guess what, you're old and you're doing it wrong

I was most recently drawn to the site by a post from Cindy House - one of the main people in the post-RMNews project - about New models, new challenges. She talks about how they haven't been successful in getting a readership, so they can't afford good content, so they can't build the readership. So, they're going to start providing consulting services, specifically: "Web design, search engine optimization and editing/writing services to other businesses."

So, how good are their consulting services?
Often the homepage for a service provider is weak. This is the so-called "Cobbler’s Son Has No Shoes" effect. However, there are some painful mistakes on the IWantMyRocky site which are actively hurting their efforts. Let's look at the home page:

I want my rocky SEO weakness

People Involved: 

We maded a babby (well, we started one)

Taxonomy upgrade extras: 

How is babby formed? We needed to know.

We think we found out.

In all seriousness, little Henry Otto (as we call the baby in utero) is now 3 months along and due in the middle of March. Yay procreation!

(p.s. let's face it: it was only a matter of time before we became breeders)

Contributors to Drupal 7.x - Code Freeze Looming Update

The code freeze for Drupal 7.x is looming large on the horizon. From that point on we will be limited in what kinds of changes we can get into Drupal core. For some the code freeze is a time of relief: it means we are down to bug fixes and the final release should be coming soon. For others it is a hard time - bug fixing isn't always as fun as adding new features.

So, as we head into feature freeze it seemed like a good time to run some statistics on who has been contributing the most to Drupal 7.x so far.

Contributors to Drupal 7.x. Through August 10th

Following on from previous times that I've run these stats, I've published documentation of the process to get the data on This time I went straight to the commit messages stored in database tables on This has the benefit of counting new files as well as old files (the last times I did this it only counted changes to existing files).

So, who are the top 10 people based on the number of times their name is in a commit message?

Name Commit mentions
Damien Tournoud 192
catch 179
chx 123
pwolanin 113
Dave Reid 109
boombatower 95
yched 77
c960657 57
drewish 56
Berdir 56

The total number of mentions is 3133, so those top 10 are responsible for roughly 33% of the code. On the flip side, people with 3 or fewer mentions are responsible for roughly 15% of the code. We still have a long tail of 222 people who are mentioned in only one message. We see a fairly typical "long tail" distribution: the people who are most involved do a lot of the work, but the people who only get mentioned a few times each are still responsible for a large number of commits when aggregated together.

Commit mentions Count of people with that number
1 222
2 80
3 38
4 17
5 15
6 13
7 8
8 7
9 5
10 6
11 1
12 3
13 3
14 5
15 2
People Involved: 


Subscribe to RSS