[Kolab-devel] Kolab Bootstrap redesign

[Ian Reinhart Geiser]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 10 March 2004 10:12 am, Stephan Buys wrote:
> You will notice that this implies the ability to dynamically map
> your users, contacts and the Kolab object to different places in
> LDAP.
I think this is a core feature for us.  Since we are integrating kolab into 
existing infrastructures we require more to make kolab look like their ldap 
schema than to manhandle theirs into our schema.

This should simplify my hack to get mailing lists and aliases to work 
properly.  Requiring the mucking with the perl script to extend kolab is a 
nightmare.  Perl is ill-suited to maintain over a long term, so the less we 
need to rely on that the better.  As long as the real data can be kept in 
LDAP and filled into templates I feel that is the best approach.

The other issue is migration of current Kolab to this "new" approach.  Since 
Kolab 2.0 has been quite tight lipped about any migration, I'm very curious 
if this new method will make migrations less painful.  Ideally kolab 1.0 -> 
2.0 will be trivial to migrate, but due to the hacks I have had to include 
for spam filtering, anti-virus, webmail, sieve editing and group aliases I 
may be in for some fun, but thats my fault ;)

Cheers
	-ian reinhart geiser

- -- 
+-Ian Reinhart Geiser geiseri at sourcextreme.com
+-Vice President of Engineering 
+-http://www.sourcextreme.com 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAT0MSPy62TRm8dvgRAspRAKDacT9D4EDH2ZyzGb1ZeLkkwIdUOQCg04cc
nuaqSbqZsLycuf/JoDyTQEI=
=QAa4
-----END PGP SIGNATURE-----


!DSPAM:404f44d5274111127263623!