Follow along at delocalizedham.com/dcsf-core-summit, j/k are next/previous
I recommend reading this if you are not viewing the presentation.
The database is optimized for viewing issues, which is a good thing; makes this a bit roundabout.
This was rendered using SQL via Drush, PHP converting to JSON, and JavaScript with Protovis.
This draft does not include the initial issue node, making the left side inaccurate. Issues leaving project 3060 do not disappear, making the right side inaccurate.
The parser is better, we are getting classes. There is now basic support for projects, we can parse all of contrib.
Now that those are out of the way
What UI improvements will increase developer efficiency and understanding?
What interesting data can be found?
Put test results on patches to encourage testing and save time.
Put documentation coverage on project pages to encourage documentation.
Make query cost more accessible to improve queries.
Make insecure configuration harder or impossible for users.
Improve core by looking at how APIs are used.
Spot trends in development.
How I did the j/k paging