Difference between revisions of "KDE Core/Platform 11"

Jump to: navigation, search
(Participants)
Line 330: Line 330:
  
 
|KDE Platform, integration, mobile
 
|KDE Platform, integration, mobile
|
+
|01.06
|
+
|07.06
 
|
 
|
 
|no
 
|no

Revision as of 10:53, 3 May 2011

Insert logo here

making it now (Nuno)

Coreproposal.png

User:Saleel's Proposal. SVG:Media:Coreproposal.svg

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.)

Participants

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 Email Role / Work Arrival Depart Est. Cost Need Sponsor? Need Hotel? Food Req. Airport Flights
Aaron Seigo [email protected] Meeting facilitation, libplasma ~170 Euro (could be 1/2) yes yes vegetarian
John Layt [email protected] Localization, Printing, Geolocation Wed 1 June Tues 7 June €200 Yes Yes Yes Zurich EZY5113 arrives 9:50, EZY5118 departs 21:20
Marijn Kruisselbrink [email protected] kdelibs mobile, meego packaging, koffice yes yes vegetarian
Thiago Macieira [email protected] Qt, used to work in kdelibs no no any
Andreas Hartmetz [email protected] kdelibs - mostly KIO and some kdeui yes yes yes
Dario Freddi [email protected] Authorization Framework, Solid, Possibly all things KCM* yes yes any LIN/BGY/MXP
Kevin Ottens [email protected] KDE Platform+Frameworks modularity, interaction with Qt yes yes no seafood coming by train from Toulouse via Avignon
David Faure [email protected] kdelibs, interaction with Qt no yes coming by train from Avignon
Alexander Neundorf [email protected] buildsystem (kdesupport +kdelibs +kdepimlibs +kdebaselibs) modularization yes yes any
Raphael Kubo da Costa [email protected] Mostly kdecore and kio. KDE/Qt on FreeBSD. yes yes any
George Kiagiadakis [email protected] drkonqi, small contributions to kdelibs, debian packaging yes yes any
Olivier Goffart (not sure) [email protected] Qt, former kdelibs contributor (port to Qt4, knotify) maybe maybe 2500 kcal/day
Till Adam [email protected] 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ügler [email protected] release team probably probably omnivore AMS
Frederik Gladhorn [email protected] Qt, knewstuff maybe probably any Oslo
Albert Astals Cid [email protected] l10n, misc yes yes almost any Dublin
Sune Vuorela [email protected] Packaging and weirdness most likely most likely yes cph; prefers train.
Stephen Kelly [email protected] kdelibs, modularisation, Qt interfacing yes yes Anything but sushi TXL/SXF
Volker Krause [email protected] kdepimlibs, kdepim, KDE on MeeGo/Maemo5/WinCE yes anything TXL/SXF
Ivan Čukić [email protected] libplasma, activities yes yes anything
Teo Mrnjavac [email protected] Social desktop yes please yes vegan coming by car
Marco Martin [email protected] libplasma, mobile profiles, activities yes yes anything
Cornelius Schumacher [email protected] Used to work on kdelibs, kdebase-runtime, and KDE PIM, these days mostly 3rd party applications. Would love to pitch the idea of merging Qt and the KDE platform to this group to trigger some productive discussion and some out-of-the box thinking maybe yes any
Valentin Rusu [email protected] Authorization Framework, KCM* yes yes any coming by car from Lyon
Helio Castro [email protected] KDE Platform, integration, mobile 01.06 07.06 no yes any FLN
Mario Fux [email protected] Sonnet (NLP framework), Nepomuk 01.06. 07.06. 0 CHF no no any
Alex Fiestas [email protected] libsolid, BlueDevil, Kamoso yes yes vegetarian (eggs+milk)
Will Stephenson [email protected] kdelibs, kdepim, packaging 01.06. 03.06. ? CHF no yes any
Gregory Schlomoff [email protected] Developer of a non-KDE app that uses kdelibs and kdepimlibs. Small contributor to kdepimlibs. Wants to help making it easier for Qt devs to use relevant kde libraries. yes, if possible. yes any looking for some cheap way to come from Paris. Car pooling?
Davide Bettio davide.bettio -at- kdemail.net libplasma and mobile developer On friday I'll leave few days after the arrival ~150 € yes yes any except fish I'll take a train
Ryan Lortie [email protected] dconf yes yes any Zurich, probably

Topics

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

  • Qt OpenGov
  • Policy towards QtMobility
  • Geolocation

Redundancies

KLocale & co vs QLocale & co: How to act local everywhere while retaining configurability.

Build Profiles

Build system

What level modularity do we want/need here ? Chances of CMake becoming the buildsystem for Qt.

QML and Javascript

Logistics

Dates

June 1/2 - 6/7

Location

Randa, Switzerland

Travel and Accommodations

See at the general Randa page.

Food, Drink and Shopping

See at the general Randa page.


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