Re: OGo and SOGo

On 21.06.2008, at 11:06, No=E8l K=F6the wrote:
> It looks like (this might be wrong!) OGo development is slow =20
> (stopped?)
> and the active development is now done in SOGo.
>
> Is this correct?

Almost.

OGo is basically 'done', its mature software in development and wide =20
deployment since over 10 years now. You mostly see bugfixes to the =20
current OGo version and smaller additions, hence, little 'progress' =20
feature wise. The next big 'feature' will be a Java 'client library' =20
for OGo, but even that is just an addition (but which might ultimately =20=

lead to a new user interface, etc etc).

SOGo is still very fresh and sees a lot of development to reach its =20
first 1.0 status. Development today is mostly driven by the developers =20=

of Inverse, which do a lot of great work on it to bring it forward. =20
Though the development model is very closed (they basically maintain =20
their own, internal fork which is made available to a public branch =20
now and then).


> Can you clarify the status/differences of OGo and SOGo?

They are completely different applications, although they share a lot =20=

of basics (the SOPE application server frameworks).

ScalableOGo is a very lightweight and highly scalable server, =20
comparable to Apple CalendarServer, Chandler Server or Bedework. It =20
stores vCard and iCal entities as-is in the database and is developed =20=

with native iCal/vCard/CalDAV/GroupDAV clients in mind.
The status is: no 1.0 release yet, but Inverse seems to be close.

OGo is a feature rich application, initially designed as a web =20
application, but with great support for access protocols like XML-RPC, =20=

WebDAV, etc.
As mentioned, it does not see a lot of 'big' development, since the =20
functionality is basically done and proven. (itch has been scratched ;-)

Feel free to ask more questions.

Thanks,
   Helge
--=20
Helge Hess
http://www.helgehess.eu/=
-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss