From perusing the Manual, my sense is that most of it's really
material for the Admin, even though it often touches on end-user
functionality, it's end-user functionality from an admin's perspective.
If you're running Chandler Server for a Law Office, the lawyers
aren't constructing tickets and using the Account Browser to manage
resources. They're using the end-user web application Dashboard and
Calendar views.
The person reading this kind of documentation is really an admin,
where perhaps they are their own end-user...
===
Cosmo supports two kinds of calendars:
* "webcal", in which an entire calendar is stored on the server
in a single resource (file). This is the format popularized by iCal
and supported by just about every calendar client, but it is too
limited to allow effective read-write subscriptions; usually only the
person who published the calendar can update it.
* CalDAV, where a calendar is represented on the server as a
collection (folder), and each event is stored inside the calendar
collection as a separate resource. This format makes read-write
subscription (real calendar sharing) possible, and it makes syncing
medium- and large-sized calendars much easier.
===
So, I'd actually advocate lumping all of this together as Chandler
Server reading material (with all the usual caveats that not all of
it is up to date) and not try to position the Manual as something for
end users.
Mimi
On Jul 19, 2007, at 10:59 AM, Ted Leung wrote:
On Jul 19, 2007, at 7:13 AM, Mimi Yin wrote:
In-line...
On Jul 18, 2007, at 11:32 PM, Ted Leung wrote:
I found a number of different Chandler Server related guides/
manuals and had a few questions.
Is this document up to date? Who is the intended audience?
http://chandlerproject.org/Documentation/
ChandlerServerEndUserManual
The document is not up to date for Cosmo 0.7, but the intended
audience is people using Cosmo to share via CalDAV / WebDAV
How is the EndUser Manual audience different from the Server
Bundle Adminsitrator audience?
http://chandlerproject.org/Developers/ServerBundleAdministrator
One is for end users (although not the hub target user) the other
is for the person who downloads Cosmo and needs to configure/set
it up
End-users for Chandler Server or end-users of Chandler Hub or
both? (I think users will likely self-identify by whether they're
using Chandler Hub or someone else's instance of Chandler Server.)
Is this something we want to maintain / update for Preview?
Primarily end users of the Server, although some of the info would
be useful for advanced users of the hub. We are assuming that the
quickstart guide will be sufficient doc for the initial launch, but
I think that we are going to find that we need "fuller" end user
manuals/docs for both the desktoip and server/hub. Whether we
actually have the bandwidth to do that is a separate question.
Perhaps we should split out a separate section in the FAQ for
Chandler Server Administrators...
I think so.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
