[Mailman-Developers] Small change to REST API for held subscription requests

[Barry Warsaw]

On Mar 22, 2015, at 09:55 PM, Florian Fuchs wrote:

>As for the `password` key: It's recognized by mailman.client and
>exposed within the mlist instance's `requests` property. But it's used
>nowhere in postorius and I would be surprised if it's used anywhere in
>hyperkitty (Aurélien...?). I guess it can go away.

TBH, I desperately want to purge user passwords from core too!  I think
they're almost completely unused; the only reason to keep them would be to
help Postorious or other REST clients.

>As for the email/address keys: We can also just keep the `address` key
>in mailman.client and let it use the same value as `email`. That way
>we would still have a fallback but the REST API would stay clean and
>wouldn't send any redundant information over the wire.

Cool.

>Can you notify me when your API changes are pushed to LP, so I can
>update mailman.client accordingly? Just to keep the window as small as
>possible where we have non-compatible states in the
>mailman/mailman.client trunks. Especially during GSoC application
>week...

Will do.  I'm working on the subscription policy branch again, and this is a
useful refactoring I'm committing before other work.  I'm trying to decide
whether to commit this to trunk now or when subpolicy lands.  Stay tuned!

Cheers,
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20150322/ffe01a5d/attachment.sig>