Difference between revisions of "KDE PIM/Akonadi"

Jump to: navigation, search
(KMail Zerstückelungsplan: change title)
(Add todo items from the Osnabrueck meeting.)
Line 7: Line 7:
 
|- style="background: #ececec; white-space:nowrap;"
 
|- style="background: #ececec; white-space:nowrap;"
 
! Status !! Item !! Description !! Contact
 
! Status !! Item !! Description !! Contact
 +
{{FeatureDone|Cache policies|As discussed in Osnabrueck|[email protected]|Volker}}
 +
{{FeatureInProgress|Agent configuration|As discussed in Osnabrueck|[email protected]|Volker}}
 +
{{FeatureTodo|Item size|Needed by Mailody|}}
 +
{{FeatureTodo|Item streaming in ItemSync/ResourceBase|As discussed in Osnabrueck|}}
 +
{{FeatureTodo|API for additional item parts|As discussed in Osnabruck|}}
 +
{{FeatureTodo|Infrastructure for showing additional dialogs from agents/resources|As discussed in Osnabrueck|}}
 +
{{FeatureTodo|Allow to limit ItemFetchJob to current cache content|Prevents search index feeder agents from downloading all remote data|}}
 +
{{FeatureTodo|Conflict detection in resources|See Osnabrueck meeting notes for details|}}
 +
{{FeatureTodo|Fix API for item/collection modifications|See Osnabrueck meeting notes for details|}}
 
{{FeatureTodo|Extend model/view stuff for mails||}}
 
{{FeatureTodo|Extend model/view stuff for mails||}}
 
{{FeatureTodo|Undo framework||}}
 
{{FeatureTodo|Undo framework||}}

Revision as of 23:04, 7 February 2008

Akonadi TODO

The following list contains the things which need to be done for Akonadi.

Core

Status Item Description Contact
DONE Cache policies As discussed in Osnabrueck Volker <[email protected]>
IN PROGRESS Agent configuration As discussed in Osnabrueck Volker <[email protected]>
TO DO Item size Needed by Mailody [mailto: <>]
TO DO Item streaming in ItemSync/ResourceBase As discussed in Osnabrueck [mailto: <>]
TO DO API for additional item parts As discussed in Osnabruck [mailto: <>]
TO DO Infrastructure for showing additional dialogs from agents/resources As discussed in Osnabrueck [mailto: <>]
TO DO Allow to limit ItemFetchJob to current cache content Prevents search index feeder agents from downloading all remote data [mailto: <>]
TO DO Conflict detection in resources See Osnabrueck meeting notes for details [mailto: <>]
TO DO Fix API for item/collection modifications See Osnabrueck meeting notes for details [mailto: <>]
TO DO Extend model/view stuff for mails [mailto: <>]
TO DO Undo framework [mailto: <>]
TO DO Action framework <Volker?>

Resources, Agents and others

Status Item Description Contact
TO DO Expire Agent [mailto: <>]
TO DO MBOX Resource <Thomas>
TO DO Extend IMAP Resource [mailto: <>]
TO DO POP3 Resource <Thomas>
TO DO Filter Agent [mailto: <>]
TO DO Search [mailto: <>]
TO DO Filter Rule GUI Used by filters and searches [mailto: <>]

KMail Breakdown Plan

The current plan is to put some parts of KMail into a stand-alone library, independent of KMail. This increases code reuse (for example, the message composer could be shared with Mailody) and makes the code a lot easier to maintain and to port to Akonadi.

Status Item Description Contact
TO DO Bodypart formatters [mailto: <>]
TO DO Reader Window [mailto: <>]
TO DO Composer: Editor [mailto: <>]
TO DO Composer: Message Composer [mailto: <>]
TO DO Composer: GUI Window [mailto: <>]
TO DO Queue Manager for mailtransport [mailto: <>]
TO DO Templates: Core [mailto: <>]
TO DO Templates: GUI [mailto: <>]
TO DO Port KMCommands [mailto: <>]
TO DO Port away from KMMessage and KMFolder* everywhere it is left [mailto: <>]
TO DO Migration application for index and other config [mailto: <>]
TO DO Port MDNs [mailto: <>]

Content is available under Creative Commons License SA 4.0 unless otherwise noted.