[Soc-coordination] debmetrics week 10 status update

[Joseph Bisch]

Hi,

This week:

As a reminder, this week I went on vacation Sunday-Wednesday, so I
didn't get as much done as I usually do.

I modified the index page so that it displayed the static interface.
The navbar now provides links to switch back and forth between the
static and dynamic interfaces. I moved the static interface metrics to
/m/<metric> instead of /<metric>.

I removed the tabbed interface from the static interface. The tabbed
interface didn't work well because it required setting a specific
height on the container. There is no easy way of knowing the height
the table will be before rendering it. So the static interface now
displays the graph with the table right below it.

I added the csv download link to the static interface. I put it right
above the table.

I set the SQLAlchemy timeout to 90 seconds, because the default of 30
seconds was too short for some of the metrics with more data

I added a dpkg_formats metric.

I added json and tab-delimited parsers.

I added python3 support. It just required changing print to a
function, ConfigParser to lowercase, and StringIO.StringIO() to
io.StringIO(). I think I also added unicode support just by changing
to python3 since python3 strs are unicode. I was able to remove the
encodes that I added to app.py and it works.

Next week:

I think I should add the ability to make the column names that get
displayed on the website different from the column names used by
SQLAlchemy and the database. For example, with dpkg_formats the column
names need to be something like v1dot0, but I would rather have it
display as 1.0 (but 1.0 is not a valid Python variable name).

I need to be careful about SQLAlchemy timing out. I can help mitigate
the issue by adding pagination to the table, so that not all the data
needs to be loaded at once. We can use JS to dynamically load the new
data for the dynamic interface and just a standard button link for the
static interface. Maybe if we add pagination we won't need the
stickyheaders plugin anymore. That would fix the issue we are having
with the interaction between stickyheaders and dragtable

Left over tasks for next week:

There is still an issue with the releases_count metric that I have not
debugged. I will do so next week. I also need to add a custom graph
for releases_count since it is too complex a metric for the default
graph. I won't be able to work on it until I debug the metric.

I am still not sure what to do about the interaction between
stickyheaders and dragtable causing the header to appear twice when
dragging a table column. I wasn't able to find anything online about
using those two plugins together. I guess if we must choose one, the
stickyheaders plugin is more important.

I still need to add more metrics. Zack asked me to add 2-3 more
metrics and I only added one so far.

I need to make the table columns deletable on the dynamic interface. I
need to make it possible to add multiple metrics to the table.

I still need to make it so that the common x-axis range is displayed
when graphing multiple metrics.

Joseph