Since the Debtags consolidation announcement there are some more news:
No more anonymous submissions
- I have disabled anonymous tagging. Anyone is still able to tag via Debian Single Sign-On. SSO-enabling the site was as simple as this.
- Tags need no review anymore to be sent to ftp-master. I have removed all the distinction in the code between reviwed and unreviewed tags, and all the code for the tag review interface.
- The site now has an audit log for each user, that any person logged in via SSO can access via the "history" link in the top right of the tag editor page.
Official recognition as Debian Contributors
- Tag contributions are sent to contributors.debian.org. There is no historical data for them because all submissions until now have been anonymous, but from now on if you tag packages you are finally recognised as a Debian Contributor!
Mailing lists closed
- I closed the
debtags-develanddebtags-commitsmailing lists; the archives are still online. - I have updated the workflow for suggesting new tags
in the FAQ to "submit a bug to debtags and Cc
debian-devel"
We can just use debian-devel instead of debtags-devel.
Autotagging of trivial packages
- I have introduced the concept of "trivial" packages to currently be any
package in the
libs,oldlibsanddebugsections. They are tagged automatically by the site maintenance and are excluded from the site todo lists and tag editor. We do not need to bother about trivial packages anymore, all 13239 of them.
Miscellaneous other changes
- I have moved the debtags vocabulary from subversion to git
- I have renamed the tag used to mark packages not yet reviewed by humans from
special::not-yet-taggedtospecial::unreviewed - At the end of every nightly maintenance, some statistics are saved into a database table. I have collected 10 years of historical data by crunching big tarballs of site backups, and fed them to the historical stats table.
- The workflow for getting tags from the site to ftp-master is now far, far simpler. It is almost simple enough that I should manage to explain it without needing to dig through code to see what it is actually doing.