From ccfff62118ec13c09238b598cddcd5781a17a677 Mon Sep 17 00:00:00 2001
From: Jim Fenton The administration of this application should be fairly simple. You can administer: There is no ability to view and / or maintain calendars or events from within this administrative interface. To do that you will need to use a CalDAV capable calendaring application such as Evolution, Sunbird, Thunderbird
-(with the Lightning extension), Mulberry, Apple iCal, an iPhone or something else. These are the things which may have collections of calendar resources (i.e. calendars). In the lists of principals you can click on any principal to see the full detail
-for that record. The primary differences between the types of principal are as follows: These differences are more conceptual than actual, however: in the DAV specification they are really all 'principals' and all equal. Groups exist to simplify the maintenance of privileges. Rather than assigning a write privilege
- to each individual with write access, you can create a group with the members being the people
- needing write access, and assign the write privilege to that group. In this way as people come and go you can maintain the members of the group and it is easier to see
- who has the desired level of access. If the needed level of access changes, you can change the grant
- to the individual group, rather than to each member of the group The basic DAV permissions are as follows: read, write-properties, write-content, unlock, read-acl, read-current-user-privilege-set, write-acl, bind & unbind There are also a couple of useful aggregates of those, which are: Since none of those covered publication of Free/Busy information, CalDAV introduced an additional read-free-busy Unfortunately that didn't cover all of the possibilities of scheduling privileges, so the
- CalDAV Scheduling Extensions to WebDAV has added several further permissions: schedule-deliver-invite, schedule-deliver-reply, schedule-query-freebusy, schedule-send-invite,
- schedule-send-reply, schedule-send-freebusy
- Two more aggregate permissions are also added with this RFC: That's all way too complicated, even if it does need to be there under the covers. Mostly you just need to know
- about read, write & free-busy Suppose you have some resources, R1, R2 and R3 and you want to centralise the booking
-of the resources through an administrative assistant, A1. When A1 is away you want to
-have a backup person, so you also want A2 to be able to do that. In a case like this you should create an intermediate group "G" and make each
- of the people you want to be able to administer those resources members of that
- group. Each of the resources should be set up to grant default privileges to everyone
- to see the full schedule (read privilege), and the resources should be
- set up to grant write (or possibly all) privileges to the group "G". In this case you might only set up a single principal for the resources, and have
- multiple calendars, one for each resource. P1 will be able to see all of the scheduled events for R1, R2 and R3, but will
-not be able to create, delete or modify them. A1 and A2 will be able to see,
-create and modify all the events. In this case the manager will simply grant the desired specific privileges to their assistant. In this case you should create a group "G", which all team members are
-members of, and each team member will grant whatever privileges they wish to that group. Similar to above, you should create a group "G", which all team members are
-members of, and each team member will grant write privileges to that group. Also see the Permissions page on the DAViCal Wiki: http://wiki.davical.org/w/Permissions. The DAViCal client setup page on sourceforge has information on how
-to configure Evolution, Mozilla Calendar (Sunbird & Lightning) and Mulberry to use remotely hosted calendars. The administrative interface has no facility for viewing or modifying calendar data. If you can read this then things must be mostly working already. The DAViCal installation page on sourceforge has
-some further information on how to install and configure this application. 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
-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. CalDAV is a client-server protocol specific to managing and reporting on collections of calendar resources. As such, our intentions in developing this application are as follows: 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. For the greatest ease use you should consider installing DAViCal 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. In general DAViCal should not need significant maintenance to keep it operating. Administrative functionality will be kept as simple as possible, within the target of supporting
-organisations of up to several hundred staff. The server-side smarts in DAViCal are intended to be fairly minimal in order to support CalDAV
- only in a manner sufficient to inter-operate with clients, and with the focus primarily
- on the storage of calendar resources. General administration of the system should be through a web-based application. Calendars will not be made available in a web-based view in initial releases. It is unlikely that calendars will ever be
-maintainable through a web-based client, although the server should support the use of web-based client software which
-works using the CalDAV protocol.Administration Functions
-
-
-Users, Resources and Groups
-
-
-Groups
-Privileges
-
-
-
-
-Some Examples
-
-Several people administer a set of resources
-
-A1 ==>> is a member of ==> G
-A2 ==>> is a member of ==> G
-R1 ==>> grants write privilege to ==> G
-R2 ==>> grants write privilege to ==> G
-R3 ==>> grants write privilege to ==> G
-P1 is a different principal with no specifically granted privilege
-
-An administrative assistant has full access to a managers calendar
-A team wish to see each others calendars
-
-P1 ==>> is a member of ==> G
-P1 ==>> grants read privilege to ==> G
-P2 ==>> is a member of ==> G
-P2 ==>> grants read privilege to ==> G
-P3 ==>> is a member of ==> G
-P3 ==>> grants write privilege to ==> G
-P4 ==>> is a member of ==> G
-P4 ==>> grants read-free-busy privilege to ==> G
-
-
-A team can modify each others calendars
-
-P1 ==>> is a member of ==> G
-P1 ==>> grants write privilege to ==> G
-P2 ==>> is a member of ==> G
-P2 ==>> grants write privilege to ==> G
-P3 ==>> is a member of ==> G
-P3 ==>> grants write privilege to ==> G
-P4 ==>> is a member of ==> G
-P4 ==>> grants write privilege to ==> G
-
-
-Configuring Calendar Clients for DAViCal
-Configuring DAViCal
-Background
-Goals
-
-
-
-Simplicity of Prerequisites
-Simplicity of Setup
-Simplicity of Operation
-Web-based Administration
-
The Open Source Applications Foundation are developing Cosmo, which is a CalDAV server -written in Java and Chandler, which is a CalDAV capable mail and calendaring application -written in Python.
- -Basic setup is as follows:
- -
Chandler describes itself as 'an experimentally usable calendar', and it certainly feels that -way. It also will only synchronise to the CalDAV server either when you press the "Sync" -button or with a default frequency of quarter-hourly. This is quite different to the other clients I -have used which all aggressively push new and changed items to the server as soon as possible, -but which may be lazy about fetching updates.
- -Operation with DAViCal seems generally fine although Chandler does not correctly display the account -information correctly, even if it seems to remember it internally.
diff --git a/docs/website/clients/Chandler-dialog1.png b/docs/website/clients/Chandler-dialog1.png deleted file mode 100644 index c9b817785f127507091095aec8f732e9f02d1a19..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 4285 zcmZu!c{mha_a9NV#xCpFmk7leYGiE;QZZR)Xe4GZWhtUavTq?@LiQz0W5!q-S<)u5 zgk+GBr6ywR%UFhZec$iRAW24GEgiW4}wOD ZD^_mxD(%vd4!cmP2*L?SlKkietB=m
zao8m zwI%|02zGRUpn= o;&gey-Onlws)912VU)eE*5#GH?q6Ws;Gdb
z`e61{3~f2UK#YNq*OG<4TWl2*pP&{gMcr3*kp#)toDe`ocH{Ry-%ol}qk4~BV~A9G
zy=d^ADPpS8|CtDxDA3G}gKPporJ_i?5}8^iV@)>r#$C55H`mHmnW`gs*^-t&j-4GY
z>*-xL3slsI-~&)(3z3bgzJFwNTIKbXm9EWVlV6hwgZTvW=$)Nz+gumj01-K)F=0&6
ztPHPIgOy~EK|kdKM+nA&yi}z1^pQ&EGJ}>LuSW!3QeTXRN`|^|Gw3K{XU7s`tu(jv
zh!(ed#Z|613DHz{J#0EsO6Su}+RVXGV*&WEkNJ#^ }0IFfQk@jGPUz-
zb@dyS2s^^kn6p1i9)uJ`P#Hg|ro>wW*=P+c-lGcaK*bsb0VoHMl=SU@m`#8uVE8b*
zG#j4v{kL5IhsgeykzZ1_OG*rw@L%ocKg`%>_p<%?KjtG2vu+Cg4s=Zv1ZY}2om}I`
z4PPwO+Sl6rC8tDqR3e7KB%-+cP=#RA(0=xGtBHHh% Evolution is available in most Linux distributions. The CalDAV support was supposedly written
-in a frenzy of hacking one day when the draft specification was at around revision 8. As a result there
-was little in the way of a repository available to test against until recently. If you have problems with Evolution, you will need to quit evolution, remove the cache file which will be in ~/.evolution/cache/calendar/ and
-restart. If you still have problems try doing that, but killing evolution-data-server in addition.
- Sometimes Evolution writes error messages into the cache file, so if you have ongoing problems you may want to
-take a look inside that. There are some quirks with Evolution's handling of CalDAV too, prior to 2.12.0, so perhaps take a look at the following
-bugs (fixed in 2.12.0): There may also be bugs in Evolution's handling of SSL with CalDAV - I couldn't get it to work reliably. %JITSb^%q8Y#g*oAljFi8bKT~*Z9fudz6(L`ktBXSw+|yZ)X|(zbI;c
z(`92Ud%`(4OV{xM^grN(!Qu|V1~gZ=Gw2g=$|em>?7scq4d?%-0}cNFI?|Vk`DW^7
zay3Lc&{vs44n*+adht9R$Tz_h (Gm?-OfBzj_@-KIYj%#J7qrfqe_6
z{JL9*a|`&8SxEMHxWb){ldFrVgNO`QV;FT(>c6?e20;^Kqb2WR%>IGCNlD1VH659y-QE6=mwJiDb?UC)Cf+4|mNR50
zw-nM?x?m+HTOJU98q~S&B=?$|P5Ms*mB`TWh9nNz4N*Gm?N0az#ZA2ZKz4dwnZnw6
zp0}a6Hxe>x^;=73&dNFBEIj(zj%b(A?n!y`$P*Ekap5l2zX!vMd*{Pta-GR#3^Qh2
zb|KFsn$n)dp9ysyaipo*wA)dOH>T~#X%e#!gR#yKkz(GJjoUjA+C;|#BJe>=cSsY5
zS&m6}MfbRqim2_-_J74UU8RCX
z2Vy*pIKLZ}7jb(&2KB8;;<~`QCC|>B{-A`E)LEpkiPtCV1A3qRG1br#A=a$|KWg}0
zKGbGfFuhB+D0;tTwwaf|XUP;{>lU)e^n6fSku!-#iWc)EV3Vi)NQlbhI{PgDou%ds
zVhDy0wd~DiGYmQ!kvrd^RzWMIdM}erZ$SDxdz#Pv#yFgXkuM7L4g%S`zKkMYRrJNm
zVYA;2FMW}FN5wJ;nvwlJ`c}-X*zTA9jT_#Oes8(j5Fb98pRJ08*4JU0p5JNtuw<1W
z0tG%W?nv(2yK-t&e-HIMIk=hC@rJ=~cI6}y!%`dONEX=w+rdc+PhK7mmCv3VeG9up
zzNEv8ZSgELETz}0`PEG+&-)+CIo^2OkvbWxyFhu%KxjHXh>RVCWJ1`(PbJv)-|&W1
z{_gA&452|h{0aA!!-{~TzVtpno{J)0=b1FVIAs7me~>TFUBzqLyZ$H2i;6_dgL+&q
zAS1Q0U6GFi^xQkb1k2Mk?!w{z1|6@t
Yrp#UnA-b2r2>rMthE$|MWTc!+pCuO`HRhapgHUo}G`i26Kn+
z-7j9ha}#Mr{gD$ZzU$^1S9<^5_m(O3Npe*nT48mGQR$arql`YN(jfhhq%CuO&>@U}Y_Ey3}7
z9V6)-B7HcbhRt|A_2@?*%cUzH{OUDIkT@v6`B|we7!Tt!cmwCfW6M%KtQX&
-
-
-caldav://server.domain.name/caldav.php/username/calendar/, enter your user name for DAViCal and click "OK".
Caveats
-