On Fri, 2007-01-12 at 12:00 +0100, user-request at open-xchange.org wrote:
> Date: Fri, 12 Jan 2007 10:35:03 +0100 (CET)
> From: Leonardo Di Lella <leonardo.dilella at open-xchange.com>
> Subject: Re: [OX User] Outlook Connector Crashing when Kalendar data
>         is      processed - OXLook
> To: User support <user at open-xchange.org>
> Message-ID:
>         <23817301.951168594503198.OPEN-XCHANGE.WebMail.tomcat at ox.netline-is.de>
>         
> Content-Type: text/plain; charset=UTF-8
> 
> On Jan 12, 2007 10:06 AM, JU <magog001 at web.de> wrote:
> 
> > Hello!
> 
> Hello,
> 
> > We have this problem sind end of december 2006 with two new
> groupware
> > user which
> > need the Connector to sync with their Windows PDAs.
> > 
> > We've tested OXLook v3.8.9, v4.0.18, v4.2.3 and v4.2.5.
> > 
> > The Groupware Server is still 0.8.0-6 as the currently available
> > OpenSource
> > 0.8.2-x has an error at the project tasks (no access) which has been
> > fixed on
> > 31.08.2006. This doesn't help when it's not released as OpenSource.
> 
> Please update to the newest server version.

	Funny, *I* was able to understand from that sentence that you quoted
that they can't update to "the newest server version", because the
newest GPL version 0.8.2-1 "has an error at the project tasks (no
access) which has been fixed on 31.08.2006", but which hasn't been
released as open source. And I'm not even in the business of supporting
a GPL program that's at least 6 months behind in bugfixes.

	The failure of OX.com to keep the buggy OX current is the reason OX
isn't in every datacenter instead of MS Exchange. Even more important
(to the community) is that the policy is killing the community. The
GPL/commercial diff strategy is a bad strategy. Combined with secrecy
and mystery about the relationships between the versions and the core
team to the community, it's a recipe for failure that's very
disappointing, especially after trying to be part of the community for
several years.
-- 

(C) Matthew Rubenstein