This was around from the time when we handled timezones sanely and
Django did not; now that we are on 1.4 we no longer need our own code to
handle this.
Signed-off-by: Dan McGee <dan@archlinux.org>
We can then show little flag icons later on in relevant places based off
of this, such as on the developer profile, clocks page, etc.
Signed-off-by: Dan McGee <dan@archlinux.org>
Move this model into the devel/ application, and move the PGPKeyField
which is used only by these models into the application as well. This
involves updating some old migrations along the way to ensure we don't
reference a field class that no longer exists.
Signed-off-by: Dan McGee <dan@archlinux.org>
This will be used to track cross-developer and master key signatures to
build a visualization in the web interface of key signatures, as well as
be able to provide info on who is verified, who is not, etc.
Signed-off-by: Dan McGee <dan@archlinux.org>
* Add models.py required file to app
* Use user_passes_test instead of custom superuser checking in
new_user_form as it implements the same "next" redirection as
login_required
Signed-off-by: Ismael Carnales <icarnales@gmail.com>
