Here is an overview of the knowledge needed, so we can plan who does what and when. Remember, if you feel that you don't know all that is needed for a task, you can still do it, we should always pair program, and only one person in the pair needs to know the details. Pairing with somebody who knows other things that you do is a great way of learning!

• Finishing up the p4a.ploneevent recurrence support: Finalizing the schema, indexing the recurrences. [Lennart: Done]
  You need to know: Plone 3 including some knowledge of Five/Zope3-type technologies.
• Adding recurrence support to collective.calendaring (probably via dateable.kalends)
  You need to know: Five or Zope3, some quick coaching on dateable.kalends from Lennart
• Making Dateable support recurring events. [Lennart: Done]
  You need to know: Five/Zope3, Plone 3, Dateable.
• Better calendar views (week, month, day)
  You need to know: Plone development.
• Better event search (from the Weblion usecases)
  You need to know: Plone development.
• A replacement for the calendar portlet that supports recurring events.
  You need to know: Plone 3, dateable.kalends (again, some ciaching from Lennart is all it takes)
• Location provider support.
  You need to know: Five/Zope3, some experience with event servies like eventful etc.
• Fix usability issues as identified by Weblion team
  You need to know: Plone 3 development.
• Documentation of calendaring features
  You need to know: English, or your language of choice. :)
• Merging dateable and p4a.calendar. [Rocky: Done]
  You need to know: ateable and p4acalendar. Better leave this to Lennart. :) This can be a lot of work or little work, depending on if we want to keep the old month view or not.
• Better tests
  You need to know: How to write tests. Probably a good way to learn testbrowser and the calendaring products.
• Confirm and try to fix bugs:
  You need to know: A bit of Plone development. Probably a good way to get started and get an overview over the calendaring products.
• Add CalDAV support. [Eric]