What should the new field on DestinationConfig be named?

[hmpf]

The email-plugin knows of and "imports" an email-address stored on the user-account. Such an email-address cannot be changed when altering a destination since it is outside the control of the notification system.

Whether an email address is fetched from the user is controlled by the "synced"-flag which is stored inside the JSON-blob settings-field.

Turns out, it is useful to "import" other types of destinations too, like phone numbers and email-addresses. allauth can allow log-ins with a code sent to a phone number, and can store and verify multiple email-addresses per user, so we're moving the functionality from just the existing "email"-plugin to be supported for all plugins.

This simplifies everything (except backwards compatibility with API v2...), but the field needs a name!

[lunkwill42]

Well, I would like to propose managed as an addition to the poll, but GitHub won't let me, claiming

There was an error posting your comment: Options is too long (maximum is 8 characters)

[hmpf]

I'll try replacing one of the existing, in case there is a hidden max of 8 options, not "characters".

[hmpf]

I replaced "fixed" with "managed", fixed is a bit too vague IMHO. Doing this reset the poll.