Yes, we should decide what is worth to automate and what is not worth to keep tracking. You should be using your time in better tasks.

Currently we are generating automatically

http://korma.wmflabs.org/browser/its.html

The data is not reliable because many repos are missing, see Bug 54469. But apart of that, we must decide which reports are you updating manually that would be useful to have automated.

Note that our priority in reference of Bugzilla stats is this key progress indicator:

https://www.mediawiki.org/wiki/Community_metrics#Bugzilla_response_time

I think this would be a good Google Code-in task.

Maybe splitting a bit? But yes.

Álvaro, I wonder whether we could integrate this reports with Korma?

Korma is just static HTML+JSON files so it is just a matter to create the HTML for the reports and upload it to korma website and then, integrate it in the menus system (pretty easy).

As we're planning to replace Bugzilla by Phabricator this is nothing to recommend to newcomers - removing easy keyword.

Should this bug be then resolved as wontfix?