New Horde web client finished

Hi!

As most of you know Horde has been an incomplete Kolab2
client for
quite a while now. The development to convert the web client
into a
fully compatible Kolab2 client has been restarted last year
and is
about to reach its final stage.

Last year prdus (http://www.pardus.de)
started developing a new Horde
driver for Kolab groupware folders. At the same time Thomas
Jarosch
from Intra2net (http://www.intra2net.de)
developed a caching framework
to boost the speed and usability to a reasonable level. 

The Kolab Konsortium (http://www.kolab-konso
rtium.de) decided to
sponsor and accelerate the Horde development done by prdus at
the
beginning of this year and the new caching framework was
sponsored by
KONSEC (http://www.konsec.de) and WU
Wien (http://www.wu-wien.ac.at
).

In the last two months we did join forces in order to
integrate the
improvements into Horde CVS. This has been an extremely
successful
cooperation and the new Kolab framework has now been
committed to
Horde CVS. We believe that this finally converts Horde into
a fully
compatible Kolab2 client. With these changes in place
Horde/Kolab is
now moving into a bug fixing phase in order to stabilize the
Kolab
specific code for the Horde 3.2 release which is to be
expected soon.

Development took place in a special Horde branch
(http://projec
ts.pardus.de/kolab/browser) which made it hard for
others to follow the development. With this final CVS commit
the Horde
CVS system can be considered the ultimate point of reference
again. So
if you have bug fixes or wish to improve the Horde code,
Horde CVS
HEAD will be your friend.

prdus did create the necessary packages for both
OpenPKG and
Gentoo. These packages are now based on CVS snapshots and
provide some
specific Kolab patches that have not yet or will not be
included into
Horde CVS. Once Horde 3.2 has been released Horde/Kolab will
start to
use reliable, released packages.

In the meantime we encourage all people that do not run a
production
server and that are interested in hosting a Horde web client
to join
the bug hunting phase. In order to install Horde please
consult the
updated installation instructions in the Kolab wiki
(http://wiki.kolab.org/index.php/Kolab2_Installation_-
_Horde).

Please submit any problems you might have either to the
Kolab bug
tracker (https://www.
intevation.de/roundup/kolab/) using the keyword
"horde" or to the Kolab queue of the Horde bug
tracker
(http://bugs.horde.org/).

Cheers,

Thomas and Gunnar

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On Wednesday 30 May 2007 14:24, Gunnar Wrobel wrote:
> As most of you know Horde has been an incomplete Kolab2
client for
> quite a while now. The development to convert the web
client into a
> fully compatible Kolab2 client has been restarted last
year and is
> about to reach its final stage.
[...]

This is great news - thanks to everybody involved!


[...]
> In the meantime we encourage all people that do not run
a production
> server and that are interested in hosting a Horde web
client to join
> the bug hunting phase.
[...]

Well, as the only machine I can use for testing *is* a
production server, I 
have a few questions...

- I have a few users who are eagerly awaiting a fully
operable web client
  and would most likely be willing to take the risk and help
debugging.
  Is there any chance that using Horde could screw things up
for *other*
  users? From what I understand it *shouldn't*, but what do
I know... :-}

- Currently, we use Squirrelmail for users who need to have
access from the   
  outside - is it possible to use Horde in parallel?

Thanks in advance!

Cheerio,

Thomas

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

> As most of you know Horde has been an incomplete Kolab2
client for quite a

> while now. The development to convert the web client
into a fully
compatible 
> Kolab2 client has been restarted last year and is about
to reach its final
stage.

Very well done to everyone involved. This is truly a huge
step forward for
Kolab.

Best Regards

Joon Radley
Radley Network Technologies CC
Cell: +27 (0)83 368 8557
Fax: +27 (0)12 998 4346
E-mail: joonradleys.co.za
Web: www.toltec.co.za



_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

ITSEF Admin <itsef-adminitsef.com> writes:

> On Wednesday 30 May 2007 14:24, Gunnar Wrobel wrote:
>> As most of you know Horde has been an incomplete
Kolab2 client for
>> quite a while now. The development to convert the
web client into a
>> fully compatible Kolab2 client has been restarted
last year and is
>> about to reach its final stage.
> [...]
>
> This is great news - thanks to everybody involved!
>
>
> [...]
>> In the meantime we encourage all people that do not
run a production
>> server and that are interested in hosting a Horde
web client to join
>> the bug hunting phase.
> [...]
>
> Well, as the only machine I can use for testing *is* a
production server, I 
> have a few questions...
>
> - I have a few users who are eagerly awaiting a fully
operable web client
>   and would most likely be willing to take the risk and
help debugging.
>   Is there any chance that using Horde could screw
things up for *other*
>   users? From what I understand it *shouldn't*, but
what do I know... :-}
>
> - Currently, we use Squirrelmail for users who need to
have access from the   
>   outside - is it possible to use Horde in parallel?
>

The last release for the Kolab-2.1_RC1 was definitely more
problematic
in terms of "could damage you server". The last
release had a patched
kolabd and kolab-webadmin package. The new release only has
a newer
CVS version of the kolab-webadmin package. This makes it
unlikely that
you damage any essential parts of your server. Once the next
Kolab
version has been released, there will be no patched packages
necessary
anymore. At that point the horde packages will be a simple
add-on and
installing them means no risk (installing, not using!).

Now what could happen to the data of a user using the Horde
web
client? I can give you no guarantees. While we stated that
the web
client is finished this is only true with regard to the
major
structural changes that were necessary. There will still be
bugs that
will cause trouble when using Horde with Kolab. Since I
currently
don't know most of these bugs  I don't
know if your users could
loose data when using Horde.

The current problem is also that we are using CVS snapshots
(http://ftp.horde.org/
pub/snaps/). While this is a drastic improvement
to the prepatched prdus packages I used before it is not the
same as
using stable, released packages. New packages will still be
released
like every other week or so and I won't be able to test all
Haorde
functionality for such a release.

I hope this helps in judging the potential problems of the
current
packages. For production server I'd wait at least until the
next Kolab
version has been released. And if you want to provide your
users with
something reliable you should wait until Horde-3.2 has been
released. And no, this is not in a far and distant future

... http://wik
i.horde.org/ShowStoppersThreeTwo

Cheers,

Gunnar


-- 
____ http://www.pardus.de
_________________ http://gunnarwrobel.de _

    >> Mail at ease - Rent a kolab groupware server at
prdus <<

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On Thursday 31 May 2007 17:05, Gunnar Wrobel wrote:
[...]

> I hope this helps in judging the potential problems of
the current
> packages. For production server I'd wait at least until
the next Kolab
> version has been released. And if you want to provide
your users with
> something reliable you should wait until Horde-3.2 has
been
> released. And no, this is not in a far and distant
future 
> ... http://wik
i.horde.org/ShowStoppersThreeTwo

Thanks for your clarifications, that helps making the
decision(s). I thinks 
I'll probably hold of a while longer, then - but I'll
definitely watch this 
space! 

Cheerio,

Thomas

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

So much appreciated .. I am waiting for this for so long
Congratulations a and a big thanks

On Wednesday 30 May 2007 08:24:14 Gunnar Wrobel wrote:
> Hi!
>
> As most of you know Horde has been an incomplete Kolab2
client for
> quite a while now. The development to convert the web
client into a
> fully compatible Kolab2 client has been restarted last
year and is
> about to reach its final stage.
>
> Last year prdus (http://www.pardus.de)
started developing a new Horde
> driver for Kolab groupware folders. At the same time
Thomas Jarosch
> from Intra2net (http://www.intra2net.de)
developed a caching framework
> to boost the speed and usability to a reasonable
level.
>
> The Kolab Konsortium (http://www.kolab-konso
rtium.de) decided to
> sponsor and accelerate the Horde development done by
prdus at the
> beginning of this year and the new caching framework
was sponsored by
> KONSEC (http://www.konsec.de) and WU
Wien (http://www.wu-wien.ac.at
).
>
> In the last two months we did join forces in order to
integrate the
> improvements into Horde CVS. This has been an extremely
successful
> cooperation and the new Kolab framework has now been
committed to
> Horde CVS. We believe that this finally converts Horde
into a fully
> compatible Kolab2 client. With these changes in place
Horde/Kolab is
> now moving into a bug fixing phase in order to
stabilize the Kolab
> specific code for the Horde 3.2 release which is to be
expected soon.
>
> Development took place in a special Horde branch
> (http://projec
ts.pardus.de/kolab/browser) which made it hard for
> others to follow the development. With this final CVS
commit the Horde
> CVS system can be considered the ultimate point of
reference again. So
> if you have bug fixes or wish to improve the Horde
code, Horde CVS
> HEAD will be your friend.
>
> prdus did create the necessary packages for both
OpenPKG and
> Gentoo. These packages are now based on CVS snapshots
and provide some
> specific Kolab patches that have not yet or will not be
included into
> Horde CVS. Once Horde 3.2 has been released Horde/Kolab
will start to
> use reliable, released packages.
>
> In the meantime we encourage all people that do not run
a production
> server and that are interested in hosting a Horde web
client to join
> the bug hunting phase. In order to install Horde please
consult the
> updated installation instructions in the Kolab wiki
> (http://wiki.kolab.org/index.php/Kolab2_Installation_-
_Horde).
>
> Please submit any problems you might have either to the
Kolab bug
> tracker (https://www.
intevation.de/roundup/kolab/) using the keyword
> "horde" or to the Kolab queue of the Horde
bug tracker
> (http://bugs.horde.org/).
>
> Cheers,
>
> Thomas and Gunnar
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users


_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

What is messing up the dates. messages all over the month
and even from May
Thomas

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users