Closes no issue.
Previously foreign keys pointed at Member objects. This created some issues as
autocomplete_fields (in Django 2.0) and
raw_id_fields require an
Admin for the models that a foreign key points to. As
Member has no
Admin this meant that we could not use
This MR fixes this issue by replacing all foreign keys to
Member with foreign keys to
In particular this MR does the following things:
mailinglistapps now use the
Usermodel for foreign keys.
Membermodel has been renamed to
Profileto reflect that it is (mostly) used for storage of extra information.
- A proxy to
Memberhas been added. This allows us to override
User. Most methods that did not make sense in
Profilehave been moved to the new