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.

Registration required
The sprint is open for all contributors. But in order to be able to do some advance scheduling as well as resource planning, registration is required. If you wish to participate, please enter your name, the time you would like to participate, and the topics of your interest below.

When

Monday 23rd of July 2012 through Friday 27th of July 2012

Where

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.

Who

What

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

Configuration Management

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.

Background

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.

Free/Busy

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.

OpenLDAP Support

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.

ownCloud Integration

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.

Packaging

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.

Resource Management

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.

Syncroton

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.

Web Client

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.

Tasks

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.

Agenda Planning

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.

Other topics

• apt packaging workflow
• Bugzilla vs. OTRS
• Bugzilla workflow

Presentations

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.