Drupal core open issues

• Features on the bottom, bugs and tasks on the top.
• Critical issues within the black lines.
• Colored as usual: grey open, red needs work, tan/yellow-ish needs review, green reviewed and tested by community.
• We used to track the development version as x.y.z.

I think we should have better tools, user interfaces, and visualizations for developers. This is one way to steer Drupal’s large developer community. For example, query cost is now more accessible; I think that will lead to less slow queries on Drupal 7 sites. Regressions are tested with SimpleTest; so there will be relatively less bugs.

This graph shows how many issues are open. I wanted to show something we haven’t seen before and maximize the amount of data on the screen. Project*’s database isn’t designed for this, it is good at saying where we are right now and how a single issue has progressed.

1. Query in SQL via Drush.
2. Translate results to JSON, including PHP unserializing.
3. Process to usable data in JS.
4. Graph with Protoviz.

This process is non-ideal, but was good for rapid iteration. Now that there is an algorithm, it can be written into a module to store the usable data in SQL. The data & code are available to hack on. This should make its way to project pages on Drupal.org; we need more ways to quickly evaluate modules.

I am working on API.drupal.org, but have been bogged down with parser rewriting. There is now a solid parser backed by Grammar Parser and the beginning of real project support. What UI improvements will increase developer efficiency and understanding?

Too often I’m stuck with ugly, circuitous tools on an underpowered development server. We can do better.