User:Herlo/Fedora Calendar Project Desired Features (Draft)
From FedoraProject
A calendaring server can be very useful to a large project like the Fedora Project. The benefits are limitless with regard to scheduling, meetings, events and other activities held within and without the Fedora Project.
It would seem the efficiency of the Fedora Project as a whole could be improved in many ways:
- Eliminating problems with time zone conversion for one.
- Fedora Meetings could be scheduled identifying conflicts.
- Individuals could import the calendar into their personal calendars
- Adding and removing personal events on their calendar could be shown with the fedora calendar events
- Depending on the sub-project or SIG, individuals could help update events for the group. (access controls would be needed here)
Contents |
Initiators (and possible owners)
Background
For information on the history and reasoning for this effort, read these entries:
Target (sub-)domains and paths
- http://calendar.fedoraproject.org* - Main web calendar / provides calendar server functionality
- https://fedoraproject.org/en/get-fedora - Shows upcoming release dates (alpha, beta, etc)
Time frame/schedule
No timeframe exists at this point, but it would be nice to see some testing started before Fedora 11 hits (end of May 2009). We'd also like to see a implementation well before Fedora 12 (end of November 2009?? <-- something the calendaring system could tell us!) which means it could/should be packaged and available in Fedora 12.
Tasks
The tasks below are a list (with tentative dates) of the process to choose a good calendaring server. Many variables may come into play that make these dates impossible. However, we will do our best to stick to the schedule.
- February 28, 2009: Identify possible candidates for calendaring servers. Several were listed in the above email thread.
- March 31, 2009: Contact calendaring maintainers/developers to obtain information and write reviews of calendaring servers.
- May 31, 2009: Obtain resources and implement top 2 or 3 candidates for testing purposes. This requires help from infrastructure and the calendaring server communities at a minimum.
- July 31, 2009: Testing of candidates should be complete including security reviews.
- August 15, 2009: Choose a calendaring server option
- August 31, 2009: Calendaring server should be packaged and ready to be added to Fedora 12.
Solution requirements
Must have
- Ability to push/pull data from handheld clients in an "acceptable" format. ical is a good candidate format.
- Ability to view a calender on a web page and edit it from there.
- Ability to support individual calenders as well as shared event calender.
- Must be readable by world.
- New submissions should be held for approval.
- Events should be editable by admins.
- Ability to support Free/Busy scheduling.
- Support automatic TimeZone conversion.
Should have
- Use OpenID for authentication.
Other good qualities
- Be a modular design (v. monolithic)
- Have an active and large community
Raw list of Calendaring Servers
- http://trac.calendarserver.org/ (Apache v2.0)
- Bongo Project - http://bongo-project.org/Main_Page (formerly Hula) (GPLv2)
- Bedework - http://www.bedework.org/bedework/ (BSD License)
- DAViCal - http://rscds.sourceforge.net/ (GPLv2)
- Zikula - http://zikula.org/ [A CMS being packaged by Docs, has some calendaring support] (GPLv2+)
- Chandler Project - http://chandlerproject.org/ (Apache v2.0)
- OpenGroupWare - http://www.opengroupware.org/ (GPL or LGPL)
Vetted list of Calendaring Server solutions to try
Team requirements for deployment and maintenance
We are looking for a team of people who wish to deploy and maintain a new calendar server for the whole of the Fedora Project. This project will provide a way to schedule events within each sub-project with access control. Larger calendaring functionality could become commonplace with something like this and help to provide better management of schedules, releases, etc.
Scope of work
Skills needed
- Web systems administration
- Possible Design (graphics, CSS)
- Coding (PHP, Python, Java, etc.) in the particular CMS solution
- Some understanding of caldav or ical functionality
