[Bug 1423756] Re: Ability to define user as domainowner or serverowner

Barry Warsaw 1423756 at bugs.launchpad.net
Sun Mar 15 21:02:05 CET 2015

This needs to be tackled at several layers.

Within the model, I think we add a flag to the user object to indicate
whether they are a server_owner or not.  It defaults to False.

Also at the model layer, Domains currently have a `contact_address`
field.  I think this should go away in favor of a set of user
references.  This will probably need to go in a separate table.  The
field would be called `owners` and it would iterate over user objects
for users who own the domain.  I wish we could use a roster but rosters
require mailing lists.

There will need to be a database migration for these changes.   Tests
and docs too.

After that, both features need to be plumbed through the REST API.  For
the server_owner flag, it's easy; just add the boolean to the user

For domains, we probably need a subresource which is a collection of
owners, i.e. users.  That might make the _DomainBase a little trickier
but I think it can be done.  Then that subresource probably needs the
usual GET, POST, PUT, PATCH, DELETE methods to add and remove domain

Docs and tests for these too.

Am I missing anything?  Would anyone like to take a crack at this?

** Changed in: mailman
     Assignee: Barry Warsaw (barry) => (unassigned)

You received this bug notification because you are a member of Mailman
Coders, which is subscribed to GNU Mailman.

  Ability to define user as domainowner or serverowner

To manage notifications about this bug go to:

More information about the Mailman-coders mailing list