diff options
| -rw-r--r-- | ADMIN.md | 4 | ||||
| -rw-r--r-- | README.md | 36 | ||||
| -rw-r--r-- | TODO.md | 10 | ||||
| -rw-r--r-- | USE.md | 66 | ||||
| -rwxr-xr-x | bin/git-init.sh | 10 |
5 files changed, 114 insertions, 12 deletions
diff --git a/ADMIN.md b/ADMIN.md new file mode 100644 index 0000000..3895db2 --- /dev/null +++ b/ADMIN.md @@ -0,0 +1,4 @@ +Quick'n'dirty locating events containing recurrence rules, +except (most likely) summertime rules: + + grep -rP 'RRULE:FREQ=(?!YEARLY(;UNTIL=19430919T000000Z)?;(BYMONTH=(2|3|4|9|10|11);BYDAY=(-1|1|2|3)SU|BYDAY=(-1|1|2|3)SU;BYMONTH=(2|3|4|9|10|11)))' @@ -1,8 +1,34 @@ -# Overview of calendaring info +# Scheduling of calendar events _(event)_ -[[!template id=realm]] handles personal and group calendars. -Some calendars are also public readable. +iCalendar specifies a file format for events. -## Setup +CalDAV specifices how to manage events. - * Short [[event/intro]] to start using calendaring +iCalendar spec is relatively simple, and widely supported. +CalDAV spec is very big and complex, however, +and no system supports all of it. + +This system supports a limited subset of CalDAV +tested to work with Apple and Mozilla clients. +Currently non-shared calendars are supported, +without iTIP or iMIP. + +It is possible to extend our current system with iTIP/iMIP support, +but that has not yet been explored. + +Technically, the CalDAV service uses [Radicale]. + +[Radicale]: https://radicale.org/ + + +## Invites + +Triggering and tracking (semi-)automated invitations to events +(i.e. CalDAV extensions [iTIP][] and [iMIP][]) +is currently not supported. + +[iTIP]: <https://devguide.calconnect.org/Scheduling/iTIP/> + "iTIP - specification on handling participant invites for CalDAV events" + +[iMIP]: <https://devguide.calconnect.org/Scheduling/iMIP/> + "iMIP - specification on distributing iTIP invites via email" @@ -7,6 +7,14 @@ Pending: * Define calendar naming logic shared_$GROUP public - * Maintain shared calendar + * Create shared calendar + * Publish shared calendar + * Archive public shared calendar + + Stop mirroring from CalDAV to iCalendar + + Copy iCalendar file to archive section + + Update iCalendar link on public web page + + Remove iCalendar file at old location + + Remove CalDAV symlink for all members of sharegroup + + Remove CalDAV directory for sharegroup owner * Document personal calendaring * Document shared calendaring @@ -17,12 +17,6 @@ Recommended calendaring client depends on the operating system you use: and [ICSdroid](https://f-droid.org/app/at.bitfire.icsdroid) -## Security - -Before you setup any password-protected calendars, -make sure to install the [CACert.org security certificate](http://wiki.cacert.org/FAQ/BrowserClients). - - ## Read-only access When you only need to read a calendar, @@ -54,3 +48,63 @@ use this alternative approach: (replace USERNAME with either personal or calendar-group account name) 2. Open calendaring client, and add new account profile of type "CalDAV". 3. Paste the calendar address as server address. + + +## FIXME + +FIRST: open Calender - +Under Calendar>Preferences>Accounts find the old kpstaff calendar, +mark it and hit the - in the button to delete it, +It is not working anymore and can not be used. + +THEN: set up the new one following the steps below. + +Step 1: +Under Calendar>Preferences>Accounts create a new account by pressing the "+" +and select "Other CalDAV Account" + +If it says 'AUTOMATIC' change it to \'91MANUAL\'92 in the top drop down menu. + +Step 2: +Fill in the following: + +Username: Your Username +Password: Your Password + +URL: <https://event.homebase.dk/ + +press "add" + +All team calendars + staff and room booking calendar should now pop up. +And we can all edit them (students cannot of course). + +How to create an additional calendar? + +Step 3: Press the "+" icon in the bottom left of the screen: +you now have a new calendar. +Name it what you want by double clicking on it and editing it. + +This new Calendar is personal and is not shared to other, +but is synchronised between your own devices. + +If you want let's say a new Team xx calendar to be read/write for all staff, +then create it and write <mailto:teknik@lists.homebase.dk> +and ask to make it available for all staff. + +How do the students see the calendar(s)? + +Go to <http://event.homebase.dk/>, +copy the URL to the calendar(s) they need, +and mail it to them, +then in Calendar, +by going to Calendar > Subscribe in the menu and pasting the URL +or just dobbelclik the link you send (works most of the time). +They still need to refresh to update +and any changes you make will take 10 minutes to go across. + +For tech support, contact the teknik list. +<teknik@lists.homebase.dk> + +Important: Never ever share passwords. +Not to technicians, not to police. +Never. diff --git a/bin/git-init.sh b/bin/git-init.sh new file mode 100755 index 0000000..6ca03e2 --- /dev/null +++ b/bin/git-init.sh @@ -0,0 +1,10 @@ +#!/bin/sh + +# FIXME: Run as user radicale in dir ~/collections/collection-root + +git init +echo '.Radicale.cache' > .gitignore +echo '.Radicale.lock' >> .gitignore +echo '.Radicale.tmp-*' >> .gitignore +git add '*.ics' '*.vcf' '*.props' .gitignore +git commit -m "Initial snapshot." |