[sync] merging the eGroupWare and Horde SyncML codebase

[Chuck Hagenbuch]

Quoting Lars Kneschke <l.kneschke at metaways.de>:

> 2-3 years ago, i took the Horde SyncML code, and integrated it with
> eGroupWare. I did much changes to made it working with eGroupWare. So far
> the result mostly ok. But not perfect.
>
> As we have started to rewrite big parts of eGroupWare anyway, i would like
> to take this opportunity and resync our code bases.
>
> I would like to take your codebase again. Hopefully i will find a way, how
> we share our code bases in the long run. It makes not much sense, that i
> maintain a separate codebase then yours.
>
> If i remember correctly i posted already the same 1 or 2 years ago. But now
> we will really do it!! :-)

That's great. However, I would strongly prefer that you not fork the  
code this time.

Instead, you should write an eGroupware SyncML_Backend class, and all  
development should stay in Horde CVS. Otherwise I don't see how we  
won't have the same situation shortly, with fixes not making their way  
back to the Horde code and some users complaining to us about problems  
with the eGroupware code.

I want to make it very clear that I'm happy to get the code used and  
to have your input. But last time, we didn't get very much in the way  
of input or fixes. So I would strongly, strongly prefer that  
development stay in Horde CVS this time and that eGroupware use the  
packaged SyncML releases  
(http://pear.horde.org/index.php?package=SyncML).

Best,
-chuck