(Initial rough ideas for dashboard project. Needs some more detail on how to do it.) |
|||
| Line 25: | Line 25: | ||
* [http://petals.ow2.org/ Petals] | * [http://petals.ow2.org/ Petals] | ||
* [http://www.mulesoft.com/ MuleSoft] | * [http://www.mulesoft.com/ MuleSoft] | ||
| + | |||
| + | 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: | ||
| + | |||
| + | * JasperReports: | ||
| + | ** Bugzilla: http://jasperforge.org/projects/bugzillareportswitholap | ||
| + | |||
| + | * Pentaho | ||
| + | ** Bugzilla: http://sourceforge.net/projects/qareports/ | ||
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:
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.
Support for community infrastructure: