KDE PIM/Meetings/Osnabrueck 10: Difference between revisions
| Line 82: | Line 82: | ||
==== Resource scheduler ==== | ==== Resource scheduler ==== | ||
'''Audience:''' Akonadi developers, '''Desired results:''' Design for resource scheduler | |||
Discussing design of resource scheduler | Discussing design of resource scheduler | ||
Revision as of 21:42, 8 February 2012
The annual KDE PIM Meeting Osnabrück 10 is currently in a planning state. It will take place on 10.2.2012 - 12.2.2012 at the Intevation offices in Osnabrück. Participation is open please enter yourself to: https://sprints.kde.org/sprint/68
Accomodation and Travel will be organized on the Sprint page
Topics
Projects
Projects we'll work on in small groups, mostly coding or creating other concrete results.
- Nepomuk integration in KMail (and possibly other PIM applications) in respect to the feeder rewrite.
- Groupwise calendar resource for Akonadi
- Akonadi importer for Polka
- Zanshin
- Porting KTimetracker to Akonadi
- KMail migration
- Wiki
- KAlarm Akonadi resource
- Stabilizing Akonadi IMAP resource
- Writing: Explaining Akonadi
- Writing: Report on status of Akonadi
- Document Kolab's use of Akonadi
- Java library to access Kolab IMAP
Discussions
Discussions about topics, which are relevant to all or a sub group of people. Please state audience and desired result of the discussion.
Marketing
Audience: all, Desired Results: List of real problems, list of myths, plan how to address both
Akonadi and as a consequence KMail and the other PIM applications still have a pretty bad reputation. People perceive it as slow, using too much memory, or generally unstable. We should identify what are real problems and what is myth and come up with a plan how to address both.
Basically, there are two issues:
- Akonadi is perceived to be useless
- Akonadi is perceived to be unstable, buggy, slow
Both can be addressed by some decent articles and improvements to the website(s). The recent 'what did we fix in KMail' was great way of addressing the second point and we need to start writing about concrete examples of what will be possible (and esp about what is already done) asap to address the first issue.
libkolabxml
Audience: all, Desired results: Decide about exposed payload formats
State & implementation of the new XSD based Kolab library, see
- http://kolab.org/pipermail/kolab-format/2011-December/001568.html
- http://kolab.org/pipermail/kolab-format/2011-December/001569.html
including:
- Which payload format could/should be exposed through ASAP for Server Side Akonadi clients?
Server Side Akonadi
Audience: people interested in Kolab, Desired results: design decisions
See http://wiki.kolab.org/User:Greve/ServerSideAkonadi
Points to discuss:
- Dependencies, in particular kcalcore, kabc
- Formats, see above
- D-Bus related concerns for server architecture
KDE PIM on Mobile
Audience: mobile people, Desired result: Plan how to get Kontact in app store
How is Kontact and other parts of KDE PIM doing on the N9, on Android, on other mobile platforms?
Kontact Touch should be available through the community app store, rather than hand-b0rked installation, see
- http://apps.formeego.org/applications/
- http://www.slideshare.net/jukkaeklund/fosdem2012-community-apps-repository/
- http://bergie.iki.fi/blog/application_quality_assurance_in_linux_distributions/
How to make that happen?
Akonadi bugs
Audience: Akonadi developers, Desired results: Update list of bugs
Getting input on a number of Akonadi bugs
Resource scheduler
Audience: Akonadi developers, Desired results: Design for resource scheduler
Discussing design of resource scheduler
Maildir flags
Discussing handling of maildir flags
Presentations
Presentations of things interesting to the KDE PIM community. Please state targeted audience.
- Bachelor thesis: REST interface for Kolab (Thomas Koch) (Audience: all)
Agenda
Friday
Arrivals, come up with agenda start meeting.
~19:30 Dinner at Chow's Garden (Japaneese / Asian Food)
Saturday
20:00 Dinner at Arabesque (Arabian Food http://www.arabesque-osnabrueck.de/)
Sunday
Date Finding Table (for reference)
Legend:
X: available
- (or empty): not available
?: available but troublesome
| Name | 6.-8.1 | 13.-15.1 | 20.-22.1 | 27.-29.1 | 10.-12.2 | 17.-19.2 | 24.-26.2 | 3.-4.3 |
|---|---|---|---|---|---|---|---|---|
| Andre Heinecke | ? | X | X | X | X | X | X | X |
| Georg Greve | ? | - | X | X | X | X | X | X |
| Björn Ricks | ? | X | X | X | X | - | X | X |
| Sérgio Martins | ?? | X | X | X | X | X | X | X |
| Christian Mollekopf | - | - | - | - | X | X | X | X |
| Kevin Ottens | - | X | X | - | X | X | X | - |
| Bernhard Reiter | X | X | X | X | X | ? | ?? | X |
| Guy Maurel | - | X | X | X | X | X | X | X |
| ThorstenStaerk | X | X | X | X | X | X | X | X |
| Christoph Wickert | X | - | X | X | X | - | X | X |
| David Jarvie | - | - | - | X | X | X | - | X |
| Till Adam | - | - | X | - | X | X | X | X |
| David Faure | X | X | - | X | X | X | X | X |
| Volker Krause | X | X | X | X | X | X | X | X |
| Thomas McGuire | - | - | X | X | X | X | X | X |
| Cornelius Schumacher | X | ? | X | X | X | X | X | X |
| Andras Mantia | ? | X | X | X | X | X | - | - |
| Stephen Kelly | - | X | - | - | X | - | X | X |
| Torgny Nyblom | - | - | - | - | - | - | - | - |
| Camila Ayres | X | X | X | X | X | X | X | X |
| Jos Poortvliet | X | X | X | X | X | X | ? | X |
| Jeroen van Meeuwen | - | - | X | X | X | X | X | X |
| Ingo Klöcker | X | X | X | - | X | - | X | X |