Purpose of the Sprint
To examine the current state and near future of the KDE Platform (kdelibs and kdebase-runtime), particularly as it relates to the growing usage of it in new contexts such as mobile or on Windows and MacOS and its traditional usage as a set of conveniences and consistency creators for KDE application development.
The sprint will aim to create an actionable, multi-year roadmap for kdelibs and kdebase-runtime and will examine issues of modularity, topicality and the inherent dichotomy between the KDE Platform as an application development framework (similar to Qt) and as a stand-alone platform to target (similar to, e.g. Windows, MacOS, etc.)
This sprint will aim to bring together developers who contribute to the KDE Platform directly, who use it in sophisticated applications, packagers of it and those involved in setting similar policies for Qt.
The proposed break down of attendees:
- 12-15 kdelibs and kdebase-runtime commiters
- 3-5 KDE application developers
- 2-3 packagers
- 1-2 people from the KDE Release Team
- 1-2 Qt representatives
making for a total of 19-27 people.
If you would like to attend, please record your name below. Date organization will occur at a later point.
|Name||Role / Work||Arrival||Depart||Est. Cost||Need Sponsor?||Need Hotel?||Food Req.||Airport||Flights|
|Aaron Seigofirstname.lastname@example.org||Meeting facilitation, libplasma||yes||yes||vegetarian|
|John Laytemail@example.com||KLocale & co||yes||yes|
|Marijn Kruisselbrinkfirstname.lastname@example.org||kdelibs mobile, meego packaging, koffice||yes||yes||vegetarian|
|Jeremy Whitingemail@example.com||knewstuff, accessibility||yes||yes||any|
|Thiago Macieirafirstname.lastname@example.org||Qt, used to work in kdelibs||no||no||any|
|Andreas Hartmetzemail@example.com||kdelibs - mostly KIO and some kdeui||yes||yes||yes|
|Kevin Ottensfirstname.lastname@example.org||KDE Platform+Frameworks modularity, interaction with Qt||yes||yes||no seafood|
|David Faureemail@example.com||kdelibs, interaction with Qt||no||yes||MRS/LYS|
|Artur Souzafirstname.lastname@example.org||KDE UI/Core + QML/JS||yes||yes||any|
|Dario Freddiemail@example.com||Authorization Framework, Solid, Possibly all things KCM*||yes||yes||any||LIN/BGY/MXP|
|Alexander Neundorffirstname.lastname@example.org||buildsystem (kdesupport +kdelibs +kdepimlibs +kdebaselibs) modularization||yes||yes||any|
|Raphael Kubo da Costaemail@example.com||Mostly kdecore and kio. KDE/Qt on FreeBSD.||yes||yes||any|
|George Kiagiadakisfirstname.lastname@example.org||drkonqi, small contributions to kdelibs, debian packaging||yes||yes||any|
|Olivier Goffart (not sure)||email@example.com||Qt, former kdelibs contributor (port to Qt4, knotify)||maybe||maybe||2500 kcal/day|
|Till Adamfirstname.lastname@example.org||kdepim, kdelibs, KDE/Mac, KDE/Windows, KDE/Maemo, KDE/WinCE, KDE/MeeGo||if you don't want it eaten, don't keep it around me|
|Sebastian Kügleremail@example.com||release team||probably||probably||omnivore||AMS|
Note: these are simply sample topics, not final direction on what will actually be discussed. Actual topics will be generated at a pre-sprint meeting online as well as through group authorship of this section.
Modularization of KDE libraries
Alex: should IMO include not only kdelibs, but also kdesupport, kdepimlibs and kdebase libs
Framework vs Platform
KLocale & co vs QLocale & co: How to act local everywhere while retaining configurability.
What level modularity do we want/need here ? Chances of CMake becoming the buildsystem for Qt.
One week sometime in March-May 2011?