Confirm, emeritus
998
edits
Changes
no edit summary
* In the schema design for the new database, each field should be typed so that Thunderbird can make intelligent decisions on what actions (if any) to take if a user selects that field. For example, Thunderbird should understand that when a user clicks on an e-mail address, we should open up a compose window. If we click on a Twitter username, the users Twitter client opens up. If we click on a Skype username, a Skype client should open, etc. This should be extendible mechanism.
<b>4) Move from Mailing Lists / Address Books to more generic "groups" of contacts.([https://TODO:FEATUREPAGE feature page]):</b>
* The current implementation of mailing lists in Thunderbird is unacceptable.
* Moving from folders to tags/groups means greater flexibility in contact organization for our users.
<b>5) Build an API for address book "contact providers", which allow read and write to various online contact services.([https://TODO:FEATUREPAGE feature page]):</b>
* Design a contact editor that is flexible enough to deal with the variety of fields that a contact provider could require / support.
* Provide a way to display contact groups / mailing lists from contact providers as an address book group.
