Just as a reminder to everyone interested in it that it's there.

When logging a QSO we do a check if we already have a matching other QSO
for the QSO check. In the past this was only saved on the QSO being
logged, not on the other side (though we tried). The problem with this
was, that we queried for the other QSO and then tried to set the cfmdQSO
directly inside the QuerySet we get from filter(). Apparently each time
we access q[0] we get a new object, meaning we set the qso with
q[0].cfmdQSO = self and then saved a completely different pristine other
QSO with q[0].save(). When we put q[0] into a variable this does not
happen anymore.

Also, for this to work we need to move the checking after the initial
save(), as we need to make sure the QSO is in the DB and has an id to be
referenced with.

--max-line-length 120

 * move script to its own bin dir
 * update django setup style
 * clarify what the script is deleting and what not
 * drop python2 support

Add install instructions to readme that worked at least for me to set
this interface up again.

Previously we had a lot of hardcoded contest information in the
templates. Name, ruleset and number of contest are now all taken from
the currently active contest and rendered into the templates. Instead of
an URL containing the current contest name, we just use a generic
/contest/. The API will no longer use "the contest with id=1", but the
currently active contest as well.

The currently active contest is - for now - the contest with the latest
deadline.

Now that we're somewhat Django4 compatible it's time to advertise our
newfound skill! Not all functionality has been tested, but it is
starting again.

Apparently this is now a property, so we don't need to call it. We can
just use it.

url() is no longer available, has to be replaced with path() or
re_path(). For proper include() we also need an app_name specified in
the urls.py we're including.

Can't believe this has not been done yet.

Remove some __future__ imports and the six compability layer (which was
not mentioned in the requirements.txt anyway).

Reformat codebase a bit so it is easier to work with.

The check disallowed having a QSO with any callsign that is also a
reference. Obviously the user should also be able to log this kind
of QSO, even if it might not make sense. We don't judge.

Without regTime being blank a user with regTime NULL cannot be edited
via the admin interface

Required for python3 transition

Apparently it was still unclear to people what call they should use on
registration. Added extra message to explain this further.

Before this commit when a newRef was entered on user registration and
that ref already existed we errored out. Now we use exactly that
reference when it already exists.

Script clears calls, users, references and shadow calls from the
database to clean up after the last contest.

When a user enters a call beginning with DN on the registration page we
now disable the DN-call and rig question fields, so we don't confuse
our SWLs.