From Kolab Wiki
Kolab 3.0 Sprint
The Kolab 3.0 sprint will be used to wrap up all remaining issues for the Kolab 3.0 release. Its goal: Get Kolab 3.0 Alpha Release Ready.
The sprint is the perfect opportunity for existing or new community members to learn more about the new generation of Kolab technology and work with the people who made it all happen.
Monday 23rd of July 2012 through Friday 27th of July 2012
We'll be convening in the offices of the world's premier Qt company and Kolab Systems shareholder: Klarälvdalens Datakonsult AB
KDAB (Deutschland) GmbH & Co. KG Tempelhofer Ufer 11 10963 Berlin Germany
Kolab Systems will be staying at the
NH Berlin Potsdamer Platz Stresemannstrasse 47 10963 Berlin Germany
which is only a few minutes walking distance from the office. If you wish to stay in the same hotel, please contact Kolab Systems and we can reserve you a room under our corporate rate.
|Name||Affiliation||Present from||until||Flight Details||Topics and primary interests|
|Paul Adams||Kolab Systems||23.7.||31.7.||Arr: TXL, BA0986, 19:15 Dep: TXL, BA0983, 12:20||Community pages|
|Camila Ayres||-||23.7.||27.7.||from Berlin||libkolabxml, libkolab, KDE PIM, Server Side Akonadi|
|Björn Balazs||User Prompt GmbH||26.7.||27.7.||from Berlin||Usability|
|Karl Beecher||Agile Workers (Freelance)||26.7.||31.7.||from Berlin||Kolab Enterprise Community, User Support, Web Presence|
|Lydia Bossers||-||22.7.||28.7.||Arr: TXL, 18:20 Dep: TXL, 17:25||-|
|Thomas Brüderli||Kolab Systems||26.7.||27.7.||Arr: Train (Hbf), 07:20 Dep: Sunday||Web client, Tasks|
|Georg Ehrke||ownCloud||25.7.||27.7.||ownCloud integration|
|Frank Fiedler||bergwerk IT||25.7.||25.7.||Kolab 3.0, sales|
|Georg Greve||Kolab Systems||23.7.||31.7.||Arr: TXL, 08:50 Dep: TXL, 14:50||Beer & pork scratchings|
|Torsten Grote||Kolab Systems||23.7.||27.7.||from Berlin||Community interaction, Debian integration|
|Frank Karlitschek||ownCloud||25.7.||27.7.||birthday at 25.7.||ownCloud integration|
|Lars Kneschke||Metaways / Tine2.0||25.7.||27.7.||Arr: Dep:||Syncroton|
|Alexander Machniak||Kolab Systems||25.7.||27.7.||Arr: MyCar, 12:00 Dep: MyCar, 17:00||Syncroton, web client, web admin frontend|
|Jeroen van Meeuwen||Kolab Systems||22.7.||28.7.||Arr: TXL, 18:20 Dep: TXL, 17:25|| Server architecture, configuration management, Web API, Fedora/EL integration,|
Syncroton, Debian integration, Beer,
|Christian Mollekopf||Kolab Systems||23.7.||26.7.||Arr: TXL, 08:50 Dep: TXL, 19:50||libkolabxml, libkolab, free/busy, KDE PIM, Server Side Akonadi, conflict resolution|
|Arthur Schiwon||ownCloud||25.7.||27.7.||ownCloud integration|
|Christoph Wickert||Kolab Systems||23.7.||27.7.||Arr: Hbf, 9:19 Dep:||Resource management, Fedora/EL integration, UCS integration|
This is a provisional list of topics that the sprint will tackle. Please feel free to add/substantiate/improve. But remember that if you add something to the list, you might be expected to work on it. :)
Kolab 3.0 must have a robust 'single host setup mechanism' that must work on any distribution and should be as automagic as possible in order to make it very simple to set up a Kolab server for any 'advanced user' of GNU/Linux.
Kolab servers must be able to integrate into any existing environment and configuration management system, which means it should not depend on any particular methodology. Simultaneously there should be a default configuration mechanism that is simple, robust and can set up a single host installation quickly on any native distribution.
Because most integrated solutions use LDAP for configuration management, LDAP has high priority. At the same time, large scale installations are based on puppet or similarly powerful systems.
On the lowest scale, cfengine or augeas could be used for adjusting system components to play well with Kolab such that other services do not get into the way.
This seems like the sensible path to create the standard single host installation that is going to be shipped with Kolab 3.0.
Because Kolab 3.0 will no longer have the Horde Framework Version 3 as part of its server side dependencies, and because the old free/busy system was not up to some of the tasks we want our FreeBusy_in_Kolab_3.0 system to be capable of, free/busy was essentially redesigned from the ground up.
For the side of technical description of the new system, please see the Free_Busy page in this Wiki.
Some Kolab 3.0 components have been mostly tested against the 389 Directory Server. For release it must be fully tested (and where necessary fixed) against the OpenLDAP server used in most smaller installations including the single host setups.
The ownCloud integration into the Kolab web client on https://webmail.klab.cc is already quite usable in many ways, but rough edges remain. Volunteers to work with us on finishing this would be very welcome.
Kolab Systems will do what is necessary to provide Kolab 3.0 packaged for Enterprise Linux, but we want as many community packagers to join the effort, and not just for Fedora, but also Debian, Ubuntu, OpenSuSE and every other distribution out there.
Join us to work with our team to make sure you get the code in ways that makes your life easier, and help us making the Kolab 3.0 release happen for as many distributions as possible.
Kolab 3.0 has a fully reworked resource management that is not yet fully complete because other tasks took precedence. As this is an essential feature it should be finished by the end of the Kolab 3.0 sprint.
The new ActiveSync stack co-developed with Tine 2.0 in true Free Software/Open Source fashion. Cleaner, more modular, and more efficient than Z-Push with a transparent and clean development and issue resolution process. Kolab System's Alec has been working on the Kolab backend for Syncroton and has come close to finishing integration. Now we need to complete the last steps, work on Q&A and finish the user interface.
The new skin for the web client should be finalized and improved where necessary so Kolab 3.0 will appear with a fully revamped user experience on the web.
Some general discussion about how tasks are managed in the web client and the future Zanshin client as well as how PIM items are stored in the Kolab backend.
The purpose of this section is NOT to lay out the agenda fully, but rather to get an idea of who is available to potentially work on which aspects when, such that tasks that should be jointly tackled can be put on an agenda on Monday 23.7. when the week's agenda is going to be planned. So please adjust as appropriate and enter yourself into all the tasks you wish to participate in / are willing to help with, and (if you are willing to take the lead) propose other things to be done during this week.
|Free/busy||Christian, Jeroen, Georg||Christian, Jeroen, Georg||Christian, Jeroen, Georg||Christian, Jeroen, Georg||Christian, Jeroen, Georg|
|ownCloud Integration||-||-||Alec, Torsten||Alec, Torsten||Alec, Torsten|
|Packaging||Christoph, Jeroen||Christoph, Jeroen||Christoph, Jeroen||Christoph, Jeroen||Christoph, Jeroen|
|Syncroton||-||-||Alec/Lars(part time?)||Alec, Lars, Christian, Jeroen||Alec, Lars, Christian, Jeroen|
|Tasks||-||-||-||Thomas, Paul, Christian, Georg||Thomas, Paul, Christian, Georg|
|Web Client||-||-||-||Thomas, Alec, Paul||Thomas, Alec, Paul|
- apt packaging workflow
- Bugzilla vs. OTRS
- Bugzilla workflow
Each day we will have a short presentation to bring us all up to speed on some subject. Abstracts are available in the latest Sprint News.
|Monday 10am||Jeroen van Meeuwen||Kolab 3.0 walk-through|
|Tuesday 6pm||Christian Mollekopf||libkolab: Kolab made easy, everywhere|
|Wednesday 6pm||Alexander Machniak and Lars Kneschke||Syncotron - Synchronization done right|
|Thursday 6pm||Thomas Brüderli||Roundcube – The new Web Client for Kolab|