# HG changeset patch # User Paul Boddie # Date 1445969216 -3600 # Node ID 908fe241e2de8c0ad05088ee3f9a36e59b28cb0e # Parent bbeea1b587db5b9ea3b342bf08e51daa4c9a28e0 Fixed list formatting for MoinMoin. diff -r bbeea1b587db -r 908fe241e2de docs/wiki/FrontPage --- a/docs/wiki/FrontPage Tue Oct 27 18:56:08 2015 +0100 +++ b/docs/wiki/FrontPage Tue Oct 27 19:06:56 2015 +0100 @@ -4,47 +4,47 @@ Postfix) providing extra support for calendaring and scheduling. * It uses the [[https://tools.ietf.org/html/rfc5545|iCalendar]], - [[https://tools.ietf.org/html/rfc5546|iTIP]] and - [[https://tools.ietf.org/html/rfc6047|iMIP]] Internet standards. + [[https://tools.ietf.org/html/rfc5546|iTIP]] and + [[https://tools.ietf.org/html/rfc6047|iMIP]] Internet standards. * It can inspect messages containing calendar objects and extract - availability information for sharing and publication. You and your users - decide exactly which kind of messages it will inspect, whose messages it - will inspect, and for whom no inspection or sharing will occur at all. + availability information for sharing and publication. You and your users + decide exactly which kind of messages it will inspect, whose messages it will + inspect, and for whom no inspection or sharing will occur at all. * It can provide a Web-based interface to calendar information for users who - cannot or choose not to use mail software with calendaring support. This is - optional and your users can choose to adjust, ignore or disable this - functionality. + cannot or choose not to use mail software with calendaring support. This is + optional and your users can choose to adjust, ignore or disable this + functionality. * It supports autonomous entities such as meeting rooms and resources, - automatically accepting or declining invitations according to their - schedules. You can adjust this behaviour to implement your own policies. + automatically accepting or declining invitations according to their + schedules. You can adjust this behaviour to implement your own policies. * It is licensed as Free Software, giving you the freedom to see what the - software does, as well as the freedom to modify and share the software with - others. + software does, as well as the freedom to modify and share the software with + others. Unlike some monolithic groupware solutions... * It does not require you to change your mail delivery software or your mail - storage software (subject to existing support provided by imip-agent; - support for other software can always be added). + storage software (subject to existing support provided by imip-agent; support + for other software can always be added). * It does not require your users to change their mail client software. * It does not insist that everybody must store their schedules on a single - server in order to collaboratively schedule events. + server in order to collaboratively schedule events. * Instead, imip-agent takes advantage of the decentralized nature of the - [[http://tools.ietf.org/html/rfc5545|iCalendar]] and - [[http://tools.ietf.org/html/rfc5546|iMIP]] Internet standards. + [[http://tools.ietf.org/html/rfc5545|iCalendar]] and + [[http://tools.ietf.org/html/rfc5546|iMIP]] Internet standards. * It allows people in your organisation to collaborate with people outside - your organisation without insisting that they join your infrastructure or - that everybody join some cloud service that keeps everyone's information - within a single, typically proprietary, remote service (that may also be - potentially vulnerable to intrusion and surveillance). + your organisation without insisting that they join your infrastructure or + that everybody join some cloud service that keeps everyone's information + within a single, typically proprietary, remote service (that may also be + potentially vulnerable to intrusion and surveillance). The role of imip-agent is to bridge the gap between plain e-mail and "full-stack" groupware solutions, thus allowing organisations and individuals diff -r bbeea1b587db -r 908fe241e2de docs/wiki/UseCases --- a/docs/wiki/UseCases Tue Oct 27 18:56:08 2015 +0100 +++ b/docs/wiki/UseCases Tue Oct 27 19:06:56 2015 +0100 @@ -8,13 +8,13 @@ * Enforce booking privileges * Enforce booking "budgets" to prevent people booking too many things or - booking things simultaneously that they will attend + booking things simultaneously that they will attend * Support pools of resources where one address may be responsible for multiple units that are not individually identified at the time of booking * Support duration limits and start/end time granularity, using `COUNTER` to - suggest acceptable periods + suggest acceptable periods == Appointment Booking == @@ -31,13 +31,13 @@ participants followed by the selection of a specific period by an organiser. 1. Free/busy information is solicited from potential recipients by the - organiser. + organiser. 1. Recipients respond with details of their availability (typically - emphasising when they are free for the event, busy otherwise). + emphasising when they are free for the event, busy otherwise). 1. The organiser then decides on a free period and notifies all free - participants as normal. + participants as normal. 1. Recipients respond as normal to the event invitation.