From 40269c999cbd54c7b3f38e9aebbec9b01bec25b1 Mon Sep 17 00:00:00 2001 From: Andrew McMillan Date: Thu, 30 Nov 2006 20:46:31 +1300 Subject: [PATCH] Go for the royal 'we' here, since this won't always be a one-person project. --- docs/website/index.php | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/docs/website/index.php b/docs/website/index.php index 25ca7097..79c7066d 100644 --- a/docs/website/index.php +++ b/docs/website/index.php @@ -3,17 +3,18 @@ include("inc/page-header.php"); ?>

Background

-

The CalDAV specification has been under development for a few years now, and at the same time I -have seen increasing pressure from clients to provide a solution to their shared calendaring problems. +

The CalDAV specification has been under development for a few years now, and at the same time we +have seen increasing pressure from people and organisations in the open source world to provide a +solution to their shared calendaring problems.

In evaluating the possibilities for shared calendaring, there are a number of possible approaches, but -I have elected to follow the path of implementing CalDAV because I believe it is a good specification +we have elected to follow the path of implementing CalDAV because we believe it is a good specification and that it will in due course gain client implementations and provide the richest user experience through those client implementations.

Goals

CalDAV is a client-server protocol specific to managing and reporting on collections of calendar resources.

-

As such, my intentions in developing this application are as follows:

+

As such, our intentions in developing this application are as follows:

Simplicity of Prerequisites

-

I have chosen to write this in PHP because I believe that PHP is a widely available web scripting language.

-

I have chosen to use the Apache web server because it is also widely available. This is not necessarily a requirement, -but I do not have other PHP environments available to me at this time.

-

I have chosen to use the PostgreSQL database, because it is a free, open-source database, which operates on a very wide set of +

We have chosen to write this in PHP because we believe that PHP is a widely available web scripting language.

+

We have chosen to use the Apache web server because it is also widely available. This is not necessarily a requirement, +but no testing has been undertaken in other PHP environments to date.

+

We have chosen to use the PostgreSQL database, because it is a free, open-source database, which operates on a very wide set of operating environments, and which is fully ACID compliant.

Simplicity of Setup

-

I use the Debian GNU/Linux distribution, so at this stage I have made Debian packages available. If -I find willing people I will make packages available in other forms.

-

This goal is not expected to be achieved in the first few releases.

+

For the greatest ease use you should consider installing RSCDS on the Debian GNU/Linux +distribution from the readily available, signed packages.

+

We expect to increase the level of automation and simplicity for the Debian target release in particular, although other +distributions might also become easier at the same time. We do expect slightly greater installation complexity in the first +few releases as we come to understand the particular problems people experience.

Simplicity of Operation

In general RSCDS should not need significant maintenance to keep it operating.

@@ -60,12 +63,13 @@ works using the CalDAV protocol.

Your Name Here!

If you are interested in helping, there are several areas where I need help at the moment:

-