[pkg-kolab] introducing me
math.parent at gmail.com
Wed Nov 9 08:41:20 UTC 2011
2011/11/8 Thomas Koch <thomas at koch.ro>:
> I'm starting to learn about Kolab and will start writing my bachelor thesis
> about calendaring formats and protocols in relation to REST. Since I'm a
> Debian maintainer (java stuff mainly) I thought I start by looking in the
> Debian packaging.
> Have you thought about moving the packaging to GIT? I could do the migration,
I'm in favor of moving to Git. There are several ways to do it:
- create the upstream branch using upstream git as remote (aka: keep
upstream commit ids)
- create the upstream branch using upstream tarballs
The first solution is better for continuous merge, but it increase the
commit number of our repo.
I prefer solution 1. What other team members think?
Can you join the pkg-kolab team on alioth? You will have the rights to
create git repositories (please import the svn history in the debian
> if you like. If you'd like, I could also provide a patch to use some debhelper
> magic to shorten the debian/rules considerably.
This is a good first thing to do.
There is also some bug triagging to do (see ). Most important one
is probably #647221(kolab-cyrus-common Needs to be build from the
standard Cyrus source package)
More information about the pkg-kolab-devel