Meego Wiki
Views

Metrics/Dashboard

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Community Metrics Dashboard)
Line 6: Line 6:
* Drupal members
* Drupal members
* Mailing lists (members, posts, threads)
* Mailing lists (members, posts, threads)
-
* gitorious (commits, employer details for committers)
+
* gitorious (commits, employer details for committers) - should use Jon Corbet's scripts like are used in the LF yearly kernel data.
* Wiki (edits, new pages)
* Wiki (edits, new pages)
* Forums (members, posts)
* Forums (members, posts)
Line 12: Line 12:
* Transifex (Languages, translators, strings translated)
* Transifex (Languages, translators, strings translated)
* Community OBS (uploads, users)
* Community OBS (uploads, users)
-
* SDK downloads (potentially extrapolated from meego.com
+
* SDK downloads (potentially extrapolated from meego.com)
The data should also be available for custom reports for usage and analysis in the monthly MeeGo Metrics report published by [[User:DawnFoster]]
The data should also be available for custom reports for usage and analysis in the monthly MeeGo Metrics report published by [[User:DawnFoster]]

Revision as of 01:18, 19 January 2011

Community Metrics Dashboard

The goal is to provide a web page summarising metrics about various aspects of the MeeGo project. The data should update regularly - depending on the metric, that could be real time or updated automatically on a regular basis.

The dashboard will track the following community resources, ideally:

  • Drupal members
  • Mailing lists (members, posts, threads)
  • gitorious (commits, employer details for committers) - should use Jon Corbet's scripts like are used in the LF yearly kernel data.
  • Wiki (edits, new pages)
  • Forums (members, posts)
  • IRC (totql comments, people on channel)
  • Transifex (Languages, translators, strings translated)
  • Community OBS (uploads, users)
  • SDK downloads (potentially extrapolated from meego.com)

The data should also be available for custom reports for usage and analysis in the monthly MeeGo Metrics report published by User:DawnFoster

To fulfill these goals, the dashboard will gather data from the various resource into a centralised database, using an ESB or EAI of some sort. A web page will be a view into this database with predefined reports.

Candidate reporting/ESB/EAI solutions:

For each community resource, we need to figure out how to ETL the data into a usable form, and come up with appropriate queries for metrics reports, and finally present the results on a webpage.

Comparison of candidate ETL/reporting

Support for community infrastructure:

Personal tools