The project is to create a Debian Metrics Portal, a portal, which will be a central place for various metrics and stats. The portal will:

  1. Perform measurements by itself, from various sources and by different ways;
  2. Collect ready-made stats from various places;
  3. Display collected data in various ways (in text, in plots)

What is required to describe when creating a new metric

The author of the script decides by himself how and where to store the data.

For remote measurements

Why give so much freedom

There can be many use cases of how statistics is displayed. Examples:

And they all belong to Debian Metrics Portal.

Though not all metrics are complex and require so much freedom. An access to so many possibilities could be given by portal administrator only.

Why JSON

Django templates

Graph creating

One of the main features of the portal will be an easy way to plot data. The metric author should not care how to graph, only what can be graphed.

It means:

A template tag should handle it all. It will:


The metrics can be pretty simple. For example, a dependency of number of bugs from the date can be represented as a simple list of dicts. For these cases a more generic approach can be used.

A simple metric

This data will be saved in an inner table; the script author does not need to care, where to save his measurements.


Some other notes