Second table with extra (meta?) data

[m-aciek]

There is more data that we can track, but it really doesn't belong in the main table. That is:

• currently translated branch by the team (name of the branch, that we fetch the translations from)
• timestamp and hash of the latest commit in a language repo (Last Updated column #55)
• build warnings (sphinx-build)
• lint errors (sphinx-lint)

I'm thinking of a separate table, accessed in a second "tab" on the dashboard.

[m-aciek]

Idea: base CPython commit hash and/or number of source string not having a match in PO msgids.

[StanFromIreland]

Also it would be nice to give the option to sort by more than just completion which is not relevant on the page.