gunnar: server/kolab-freebusy/freebusy/docs AUTHORS, NONE, 1.1 ChangeLog, NONE, 1.1 INSTALL, NONE, 1.1

cvs at kolab.org cvs at kolab.org
Wed Aug 8 11:47:31 CEST 2007


Author: gunnar

Update of /kolabrepository/server/kolab-freebusy/freebusy/docs
In directory doto:/tmp/cvs-serv4139/freebusy/docs

Added Files:
	AUTHORS ChangeLog INSTALL 
Log Message:
A draft version of the new kolab-freebusy package. This is now only the webserver part and also requires the PEAR-style Kolab_Freebusy library within php-kolab.

--- NEW FILE: AUTHORS ---
Originally written by Steffen Hansen <steffen at klaralvdalens-datakonsult.se>

  Copyright (c) 2004 - 2007  Steffen Hansen
  Copyright (c) 2004 - 2007  Klaraelvdalens Datakonsult AB

Portions based on work by the following people:

  (c) 2004         Stuart Bingë         <s.binge at codefusion.co.za>
  (c) 2006         Thomas Jarosch       <thomas.jarosch at intra2net.com>
  (c) 2005 - 2006  Richard Bos          <richard at radoeka.nl>
  (c) 2005 - 2006  Marcus Hüwe          <suse-tux at gmx.de>
  (c) 2005 - 2006  Martin Konold        <martin.konold at erfrakon.de>
  (c) 2006 - 2007  Gunnar Wrobel        <wrobel at pardus.de>


Portions based on work by the following companies:

  (c) 2004         Code Fusion cc
  (c) 2006         Intra2net AG
  (c) 2005 - 2006  erfrakon Partnerschaftsgesellschaft
  (c) 2006 - 2007  p at rdus


Contributions by the following people:

  Sascha Wilde  <wilde at intevation.de>  


(Established based on the following guidlines:

 People with CVS access and more than two commits are being listed in
 the first list, their corresponding company in the second list. The
 order of appearences is sorted by date of last contribution, longest
 period of contributions and finally based on alphabetical order. The
 listed contributors comitted less than three patches or do not have
 CVS access.)
--- NEW FILE: ChangeLog ---
2006-11-22  Gunnar Wrobel  <wrobel at pardus.de>

	* freebusy/freebusy.php.in:

	Avoid notices because of undefined
	$params['ldap_classname_suffix'].

	Avoid notices because of undefined $_REQUEST['cache'] and
	$_REQUEST['extended']

	* freebusy/pfb.php.in:

	Avoid notices because of undefined
	$params['ldap_classname_suffix'].

	* freebusy/pfb.php.in ():

	Completed fixing cache dir path problem.

2006-11-22  Sascha Wilde  <wilde at intevation.de>

	* freebusy/freebusy.php.in: Replaced @freebusy_cachedir@ with
	$parms['cache_dir'].

2006-11-22  Gunnar Wrobel  <wrobel at pardus.de>

	* freebusy/pfb.php.in:

	Fixed cache dir path problem described in

	https://intevation.de/roundup/kolab/issue1490

	and introduced with

	http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/freebusy.conf.template.in.diff?r1=1.3&r2=1.4

	The use of $params['kolab_prefix'] originated from the original
	caching patch but should not be used as introduced with

	http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-resource-handlers/kolab-resource-handlers/freebusy/pfb.php.in.diff?r1=1.5&r2=1.6

	since this breaks compatibility with running kolab on other
	distros.

2006-11-13  Gunnar Wrobel  <wrobel at pardus.de>

	* freebusy/freebusy.php.in:

	Trailing newline introduced in
	http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolab-resource-handlers/kolab-resource-handlers/freebusy/freebusy.php.in.diff?r1=1.3&r2=1.4
	may trigger php warnings depending on php verbosity

2006-03-28 Richard Bos <richard at radoeka.nl>
	* freebusy/pfb.php.in: Add missing prefix 'kolab_php_module_prefix'

2005-12-17 richard Bos <richard at radoeka.nl>
	* freebusy/pfb.php.in,
	  freebusy/freebusy.php.in: @freebusy_cachefile@ replaced by
	  @freebusy_cachedir@


--- NEW FILE: INSTALL ---
===========================
 Installing kolab-freebusy
===========================

This document contains instructions for installing the Kolab free/busy
support on your server. Usually you won't need to do this manually
since it is part of the OpenPKG based installation of the Kolab
Groupware Server. These instructions are only relevant if you wish to
install free/busy on a non-OpenPKG platform.


Obtaining kolab-freebusy
========================

Currently no source packages of kolab-freebusy are being
distributed. You will have to use CVS to check out the source code and
build a package by running

 make tar


Prerequisites
=============

To function properly, kolab-freebusy requires the following:

1. PHP:

   You need a PHP variant that has been patched for Kolab. It needs to
   support IMAP annotations. You are advised to use PHP 5

2. The following Horde PEAR packages (They should be availabe if you
   installed horde-framweork):

   a. Horde_Util

   b. Horde_String

2. The following Kolab PEAR packages:

   a. Kolab_Freebusy


Installing kolab-freebusy
=========================

kolab-freebusy is written in PHP, and must be installed in a
web-accessible directory.  The precise location of this directory will
differ from system to system.  Conventionally, kolab-freebusy is
installed in the /freebusy directory in the webserver's document tree.

Since kolab-freebusy is written in PHP, there is no compilation
necessary; simply expand the distribution where you want it to reside
and rename the root directory of the distribution to whatever you wish
to appear in the URL.  For example, with the Apache webserver's
default document root of ``/usr/local/apache/htdocs``, you would
type::

   cd /usr/local/apache/htdocs/horde
   tar zxvf /path/to/kolab-freebusy-x.y.z.tar.gz

and would then find Kronolith at the URL

   http://your-server/freebusy/


Configuring kolab-freebusy
==========================

You can modify the config.php within the kolab-freebusy base directory
to suit you needs but on a standard Kolab Server installation you will
usually have a configuration template somewhere in your
kolab/templates directory that will get rewritten to the location of
the config.php file.

Make sure the values within that template match your platform.


Obtaining Support
=================

If you encounter problems with kolab-freebusy, help is available!

1. Wiki

   A lot of typical question have been collected in the Kolab wiki at

     http://wiki.kolab.org

   You'll find both a FAQ and a troubleshooting section there.

2. Mailing lists

   The Kolab project also runs a number of mailing lists where you ask
   all the question left unanswered by the wiki.  Information,
   archives, and subscription information can be found at
  
     http://www.kolab.org

3. IRC

   Kolab developers, contributors and users may also be found on IRC,
   on the channel #kolab on the Freenode Network (irc.freenode.net).

4. Commercial support

   Commercial support is available at 

     http://www.kolab-konsortium.com





More information about the commits mailing list