Re: Fwd: libkolab* in debian
Christoph Wickert <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Organization | Kolab Systems |
| Message-ID | <3831376.HMrWdjFNAi__19101.6883509748$1364380445$gmane$org@thinkmatic.localdomain> |
On Wednesday 27 March 2013 10:28:27 Paul Klos wrote: > -------- Original message -------- > Onderwerp: libkolab* in debian > Datum: 26-03-2013 16:03 > Afzender: Sune Vuorela <[email protected]> > Ontvanger: [email protected] > > Hi Paul > > I got your contact details from my friend Paul (Adams). He said that > you were > the one maintaining kolab-ish debian packages. > > I'm considering getting the libkolab/libkolabxml packages inside debian > and > was considering starting off from your work or even using your work > directly. > > Are you interested in maintaining the packages inside debian? > > /Sune > > -------- End of original message -------- > > Yesterday I received this request. I have been in touch with Sune and I > can see a few benefits here: > - Already he and another Debian maintainer have had a look at the > libkolab* packages and have given a bunch of > pointers/suggestions/questions that will undoubtedly increase the > packaging quality of these libs +1 > - If the libs are part of Debian proper, kdepim-runtime can link > against them, meaning kontact/kmail in Debian would be Kolab-enabled +1 > On the other hand, if these packages were maintained inside Debian we'd > sometimes have to be careful while Debian is frozen. I don't think this will become a problem. We can still have more up-to-date versions on mirror.kolabsys.com and we will, we'll probably continue to update them there, but that shouldn't stop us from having the packages in Debian, too. We can have multiple remotes in the git repos, so we can easily pull/push changes from one repo to the other. > For both packages, Jeroen is listed as the official maintainer. As long > as he is, he should be involved in this. I've been doing a lot of > packaging work , but we haven't as yet discussed a formal change of > "maintainership". > > If so desired, I'd be happy to become the official maintainer and work > with the Debian guys to make this happen, but this is by no means the > only option. > > For now, no official steps have been taken yet, but I do plan to use > their feedback to make the packages better. Regardless of where they are > maintained, this is a clear benefit already. Even though I'm working on deb-packaging, too (mainly for UCS), I have no idea what is required to become an official maintainer. I think you would be the best candidate to take over maintainer ship in Debian as you are deeper involved with their community than Jeroen or me. I don't even think that he or me have the time to get more involved as we are already active in Fedora - and Kolab or course. So for me the situation is quite clear: We definitely want the packages in Debian and we want somebody who is involved both in Kolab and in Debian to maintain them. This makes you a good candidate. If possible, we could have multiple owners (or at least uploaders), but I'm not sure about the exact details of the Debian policies. I guess Jeroen agrees, but he (officially) is on holidays. Kind regards, Christoph P.S.: my first post on this list for quite a while. Yes, I'm still alive, yes, I still work for Kolab Systems, but I'm spending most of my time working for paying customers. I hope I will find time to be more active for and with the community again in the future. -- Christoph Wickert Senior Engineer Kolab Systems AG Zürich, Switzerland e: [email protected] t: +49 251 871 369 77 w: http://kolabsys.com pgp: 85DACC63 Christoph Wickert _______________________________________________ Kolab-devel mailing list [email protected] https://www.intevation.de/mailman/listinfo/kolab-devel
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEABECAAYFAlFSyvkACgkQFotiFoXazGOjQQCfT/H7h1AGv/ge8vlsY/oWuf09 xTMAn32aEHTIerch6o6My/LKFol5BWfi =c3ZX -----END PGP SIGNATURE-----