Confirm, emeritus
998
edits
Changes
no edit summary
* How will these changes affect the inline contact editor?
* What should happen to Collected Addresses? Should we keep the current behaviour, or should they expire based on some heuristic?
* How do we deal with syncing conflicts?
|Feature overview=From a surface perspective, Thunderbird's address book has not changed much since it's very beginnings. Even today, by default, it is impossible to create a contact with more than 2 e-mail addresses in Thunderbird. It has also failed to adapt to the social web as it exists today, where the identity of contacts can be spread across multiple services (Facebook, Google Contacts, LinkedIn, Twitter, LDAP, desktop address books, etc). It also has no notion that contacts may belong to one or more groups.
# Strict user control over what data contact providers have access to
# Allow for easy importing and exporting of contacts to common formats (vCard, LDIF, CSV, etc)
|Feature users and use cases=Our target is current users of the Thunderbird address book, as well as users who are inconvenienced or frustrated by having their contacts scattered all over the web.
Use cases:
# A user adds a contact provider to their address book. Among the various settings for this contact provider are options for setting whether or not this contact provider should be able to push changes to other contact providers. The user can also choose which fields can be pushed to this contact provider, and pushed to other contact providers from this provider.
# A user adds a contact provider to their empty address book. Contacts are copied locally. Changes made locally are automatically pushed to the contact provider.
# A user adds a contact provider to an address book that already has some contacts in it. Contacts are merged where applicable. Changes made locally are automatically pushed to the contact provider. The local contacts not already existing in the contact provider are pushed, assuming that we have write capabilities to that provider, and the user has specified that this is a provider that we want to push new data to.
# A user adds a contact provider to an address book that already communicates with one or more other contact providers. Contacts are merged where applicable. The user can view the contacts that were merged, and make any corrections or resolve any ambiguities that may have arisen from the merge.
# A user is offline and opens their address book. They are able to view and edit their contacts, but changes are not pushed until they come back online. Once back online, any ambiguities or conflicts from pushing will be brought to the users attention for resolution.
# A user adds a contact provider that provides some sensitive or private information about each contact. During the setup process, the user makes sure to set the provider so that this information is not pushed to any other contact providers.
# A user with several contact providers in their address book decides to compose an email. While filling out the "To:" field, potential contacts are displayed for auto-completion.
# A user adds a new contact to their address book. Contact providers that Thunderbird has permission / ability to write to are automatically updated with this new contact.
# A user deletes a contact in their address book. Contact providers that Thunderbird has permissions to push to have this contact removed. For providers that do not allow us to delete contacts, Thunderbird instead hides that contact from view.
# A user wants to remove a contact from one contact provider, but not from others. The user disconnects that contact from the contact provider, and the contact is deleted from that provider (if possible - if not, it's simply made hidden). Changes to that contact are no long pushed or pulled from that provider.
}}
{{FeatureInfo
