KDE PIM/Meetings/PIM Winter 2014 meeting: Difference between revisions
No edit summary |
Cmollekopf (talk | contribs) No edit summary |
||
| Line 8: | Line 8: | ||
Discuss the future (architecture) of QML APIs for PIM stuff. | Discuss the future (architecture) of QML APIs for PIM stuff. | ||
Interested: Michael Bohlender; Daniel Vrátil | Interested: Michael Bohlender; Daniel Vrátil, Christian Mollekopf | ||
===Active Mail/ KMail Mobile=== | ===Active Mail/ KMail Mobile=== | ||
| Line 22: | Line 22: | ||
=== Mail Search Testing === | === Mail Search Testing === | ||
Searching within emails still has problems for quite a few people. We could use the collective brainpower present at the sprint to try to get to the bottom of the problem. | Searching within emails still has problems for quite a few people. We could use the collective brainpower present at the sprint to try to get to the bottom of the problem. | ||
=== Frameworks release schedule & Repository divisions === | |||
Another discussion on how we exactly split up the repositories for frameworks (we know already many parts, but some are still left). Additionally we should discuss options for the release schedule. | |||
Interested: Christian Mollekopf; Daniel Vrátil; Aaron Seigo | |||
=== PIM Architecture and Design === | |||
I think we should take a high level overview of what parts we have in kdepim, how they fit together and how this structure helps us getting done what we want in the future. | |||
This becomes especially relevant with changes in akonadi, the QML API etc. We need to know why we implment what where, and be able to draw clear lines between the various components in order to avoid them getting to complex. For this we need to have an idea how the architecture should look like that we are moving towards (even if this cannot be achieved as short-term goal). | |||
Interested: Christian Mollekopf; Daniel Vrátil; Aaron Seigo | |||
=Agenda= | =Agenda= | ||
Revision as of 15:12, 12 November 2014
Topics
Usability - User stories and scenarios
Enable user-centered design through user stories and scenarios based on actual users form the city administration of Munich.
Interested: Michael Bohlender; Thomas Pfeiffer
QML API
Discuss the future (architecture) of QML APIs for PIM stuff.
Interested: Michael Bohlender; Daniel Vrátil, Christian Mollekopf
Active Mail/ KMail Mobile
Discuss the future of Active Mail.
Interested: Michael Bohlender; Daniel Vrátil; Thomas Pfeiffer
Akonadi Framework
We already discussed this a lot during Akademy, this time I'd like to look into solving specific problems that Kolab guys have run into while preparing Akonadi and KDE PIM for Munich. I also want to actually sit down and design some of the major features/changes we are planning.
Interested: Daniel Vrátil; Christian Mollekopf
Mail Search Testing
Searching within emails still has problems for quite a few people. We could use the collective brainpower present at the sprint to try to get to the bottom of the problem.
Frameworks release schedule & Repository divisions
Another discussion on how we exactly split up the repositories for frameworks (we know already many parts, but some are still left). Additionally we should discuss options for the release schedule.
Interested: Christian Mollekopf; Daniel Vrátil; Aaron Seigo
PIM Architecture and Design
I think we should take a high level overview of what parts we have in kdepim, how they fit together and how this structure helps us getting done what we want in the future.
This becomes especially relevant with changes in akonadi, the QML API etc. We need to know why we implment what where, and be able to draw clear lines between the various components in order to avoid them getting to complex. For this we need to have an idea how the architecture should look like that we are moving towards (even if this cannot be achieved as short-term goal).
Interested: Christian Mollekopf; Daniel Vrátil; Aaron Seigo
Agenda
Meeting Notes
Organization
See the KDE Sprints page.