[Soc-coordination] debmetrics week 5 status update

[Joseph Bisch]

Hello,

This week, based on Piotr's suggestion, I used astring.title() in
table2class function. I added python-croniter to the requirements.
Python-croniter is required by python-crontab for schedule.get_next()
and schedule.get_prev(). Based on Stuart's suggestion, I added
docstrings to pull_runner_test and used self.assertEqual instead of
assert. I added additional pull_runner tests. I finished the switch to
SQLAlchemy in pull_runner. I renamed the filename used by the table. I
displayed the tables on the website. Based on Piotr's suggestion, I
imported the models variable in create_all.py instead of importing
each model individually.

During the call we talked about possibly using importlib to generalize
the flask code. He sent me links to some code from debsources that
shows how importlib is used. Zack suggested trying to deploy the
manifest and script files in a separate location on the filesystem
from the code itself. I will record any issues I encounter while doing
so. Zack also suggested I work on the interface for push scripts. We
talked about the tables. Right now they are generated by matplotlib as
an image. The images are hard to read when you have a lot of rows,
plus Zack brought up that it is bad for accessibility. So he suggested
using jinja2 to generated HTML tables. Depending on the directory from
which they are run, my tests are sometimes not running correctly, so I
will work on them so that they don't need to run from a specific
directory.

For next week, I will use HTML for the tables instead of matplotlib. I
will fix the tests. I will make the flask code generate, so that it
doesn't need to be changed when a new metric is added. I will deploy
the code with the manifest and script files in a different location
from the code and will record any issues I experience with it.

Joseph