[Members] XSF's new calendaring infrastructure

Tobias Markmann tmarkmann at googlemail.com
Sat Nov 7 06:04:30 CST 2009


During the last week I've worked on a new calendaring infrastructure for the
XSF so that we don't miss any important events (like Meetings and that
alike). It's kept pretty simple and is based on a python script and our
already existing repository.
Peter and I decided to add some more meta-data to the XEPs and now we
basically have all we need.

At the moment the system's output are 5 ICS calendars:

   1. xsf-extensions.ics: This one includes all Last Call end dates and the
   expire dates of the Experimental XEPs.
   2. xsf-council.ics: This is based on trunk/council/events.xml. Intended
   for council meetings and that alike.
   3. xsf-board.ics: This is based on trunk/xsf/board/events.xml. Intended
   for board meetings and that alike.
   4. xsf-general.ics: This is based on trunk/xsf/events.xml. Intended for
   local XSF events, XSF summits, etc.
   5. xsf-all: This is just a simple aggregation of the four distinct

All the iCalendar-files (.ics) are supposed to be generated automatically
when their dependencies change (either a XEP gets changed or one of those
events.xml files).

The syntax of the events.xml file is like this:
<?xml version='1.0' encoding='UTF-8'?>
<date>2009-11-09T19:00:00</date> <!-- Date and time in the UTC timezone. -->
 <duration>30</duration> <!-- duration in minutes -->
<summary>Council Meeting 5</summary>
        <all-day/> <!--this one is optional and indicates an all-day event;
doesn't make sense for any meetings or that alike. -->

If you notice any bugs, have ideas for improvement or other issues please
let me know.

Tobias Markmann
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/members/attachments/20091107/bfd1f242/attachment.htm>

More information about the Members mailing list