KDE PIM/Meetings/Osnabrueck 7: Difference between revisions
m →Agenda |
|||
| Line 12: | Line 12: | ||
Unscheduled topics and corresponding responsible persons (feel free to remove yourself there if you don't like what I assigned to you ;-) ): | Unscheduled topics and corresponding responsible persons (feel free to remove yourself there if you don't like what I assigned to you ;-) ): | ||
* Porting strategy for KABC/KCal based resources and applications (Kevin, Tobias) | * Porting strategy for KABC/KCal based resources and applications (Kevin, Tobias) | ||
** Designing an Akonadi-based replacement for KABC::StdAddressbook | ** Designing an Akonadi-based replacement for KABC::StdAddressbook | ||
| Line 49: | Line 48: | ||
* Presentation of the Akonadi on N810 project (Karim, Cédric, Romain, Audrey, Guillermo) | * Presentation of the Akonadi on N810 project (Karim, Cédric, Romain, Audrey, Guillermo) | ||
* KMail porting strategy (Thomas, Till, Ingo, Volker, Stephen) | * KMail porting strategy (Thomas, Till, Ingo, Volker, Stephen) | ||
* Static code analysis in KDE PIM (Bertjan) | |||
Revision as of 14:55, 9 January 2009
Annual KDE PIM meeting in Osnabrueck 2009.
Date: Jan 09th (friday) to Jan 11th (sunday).
Location/Travel
Location: NEW office of Intevation GmbH (Neuer Graben 17, 49074 Osnabrück, Germany), http://www.intevation.de/travel.en.html
Hotel: http://www.dom-hotel-osnabrueck.de/index_en.php (as usual)
Agenda
Unscheduled topics and corresponding responsible persons (feel free to remove yourself there if you don't like what I assigned to you ;-) ):
- Porting strategy for KABC/KCal based resources and applications (Kevin, Tobias)
- Designing an Akonadi-based replacement for KABC::StdAddressbook
- Needed Akonadi developments for 4.3 (Volker)
- Free/Busy support (Brad)
- Consideration of moving mail output (i.e. kdepim/mailtransport functionality) to Akonadi (Brad)
- Review Akonadi change notification (Stephen, Volker, Kevin, Tobias)
- Adding ItemMoved and CollectionMoved and adding parent collection to {Collection,Item}Removed in a BC way.
- Review Akonadi conflict detection (Stephen, Tobias, Volker)
- detecting backend induced conflicts on the resource side
- how to handle conflicts/GUI presentation
- Re-Redesigned KMime ContentStrategy stuff using KJobs (still to do) (Stephen)
- How to use Akonadi in your application/best practices/api dox review (Stephen)
- Review Akonadi extensions currently developed in playground/pim (Stephen, Volker)
- Discuss the fd.o situation (Cornelius)
- Review the distlist situation (Kevin, Tobias)
Put topics you would like to discuss here
Tentative schedule:
Friday
All day: arrival
- Forcing Ingo to finally commit his Akonadi work from the last meeting (Volker) ;-)
- Evaluating the Akonadi migration in 4.2 or: the very last chance to stop Akonadi in 4.2 (Kevin, Volker)
- KDE PIM runtime/apps split (Tom)
19:00 Dinner at "Chows Garten", Große Hamkenstr. 19
Saturday
08:00 Breakfast
- Presentation of the Akonadi on N810 project (Karim, Cédric, Romain, Audrey, Guillermo)
- KMail porting strategy (Thomas, Till, Ingo, Volker, Stephen)
- Static code analysis in KDE PIM (Bertjan)
19:00 Dinner at "Rampendahl", Hasestr. 35, http://www.rampendahl.de
Sunday
08:00 Breakfast
All afternoon: departure
Meeting Notes
- KResource -> Akonadi migration
- disable the creation of KRes client side bridges, but leave the migration enabled as such.
- Apps/Runtime split:
- we will create a runtime subdirectory in kdepim containing runtime dependencies (akoandi agents, plugins, etc) which should be buildable separately, cf. kdebase
Please complete by adding your notes!