Moving udd to django

[Martin Pool]

I think switching from batch html, handcoded sql and ssh access to
higher-level alternatives would be well worth while and Django seems
like a good choice. +1 from me, and also on the specific incremental
changes.

I agree with James, and disagree with Vincent, about bringing these
changes in to the running UDD importer.  It will benefit from eg
having a better web and admin ui, it will be less risky to deploy
changes gradually, and we are better off not forking if we can avoid
it.  Eventually we can split it into separate services/components.

Merging some of udd's failure tracking code with oopses would be good
but I think it's mostly complementary too this work, rather than an
alternative.

-- 
Martin