Going to be working on a project around stats for the contributor community, something at which we currently suck (even creating the list of people with props each release is still a fairly manual process). For the sake of this exercise, ignore the voice in your head that thinks, “There’s no way to gather that information,” or “We’d need a new API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. for that,” and just brainstorm. What stats would it be cool for us to have about the activity of core contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org.? Leave your ideas in the comments, and they’ll be cobbled together into a big list that I take to Otto to see what’s possible (at which point Nacin can start daydreaming about APIs, but not until then).
A few notes about these numbers. First, they are summary percentages for the previous day (where day is based on GMT). You’ll also notice that these numbers don’t really line up with each other, this is because the system normalizes the version numbers and throws out odd/invalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. versions (I was surprised by how many odd version strings there are out there). As a result each category The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. is best compared to itself, instead of trying to compare PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher with MySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. numbers.
The content type returned for this data is ‘application/json’, your browser may or may not display them correctly.
This is a start, there are more things to be added to this in the future. One obvious item is support for getting numbers for previous days and date ranges. Another would be to add some pretty graphs to WPORG to display this data.
Just ran some stats on where WordPress 3.0 development is compared to some of the previous larger releases:
- Closed 896 tickets so far compared to the previous peak of 786 for 2.8 and only 448 in 2.9
- Been coding for ~5months so far compared to 7 months for 2.5 and 9 months for 1.5 (Those were the days!)
Michael Adams ran some Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. stats last week for my keynote at WCSF, I only mentioned one of them but here are the rest:
We had 1,440 unique people particpate in tickets, attachments, comments, commit, or get props in the past year.
There were 3,506 new tickets from 1,093 people, and they had 3,979 attachments from 491 people.
TWENTY SEVEN THOUSAND comments. (And change.) From 1,032 people, or about 27 per person.
13 people committed 3,176 revisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision., about a third (1,387 of those) with “props.”
It was a very good year.