SoC calendar plugin - Revision history

Dirk: added Vinny as the possible mentor

2010-03-06T11:03:25Z

added Vinny as the possible mentor

Vinny: added outlook sync to "nice to haves"

2010-03-04T23:48:28Z

added outlook sync to "nice to haves"

Vinny: Separated out "must haves" and "nice to haves". Added Notes section. Fixed some spelling, grammer, and "clarity" errors.

2010-03-04T23:42:27Z

Separated out "must haves" and "nice to haves". Added Notes section. Fixed some spelling, grammer, and "clarity" errors.

Dirk: locale: time, entry

2010-02-24T19:42:57Z

locale: time, entry

Dirk: Typo

2010-02-24T19:39:22Z

Typo

Vinny: Added some more links, WebDAV

2010-02-24T18:29:09Z

Added some more links, WebDAV

Vinny at 17:36, 24 February 2010

2010-02-24T17:36:44Z

Vinny: Initial Overview and Requriements.

2010-02-24T17:20:55Z

Initial Overview and Requriements.

New page

<center>(This is an idea page for the [[Google Summer of Code]])</center>

== Overview ==
Geeklog's current calendar plugin is old and unmaintainable. It has no support for modern calendar standards and cannot support such basic functionality as recurring events. It's interface is antiquated and its sharing/group features are extremely limited.

A new Calendar plugin, written from scratch, could be designed from the group up to work with calendar standards and support a wide variety of use cases.

== Requirements ==
Listed below are an initial set of requirements. Students applying to complete this project can use the below list as a design outline.

* The calendar shall support events for individual users.
** Individuals shall be able to create multiple calendars (limited to number defined by an administrator).
** The calendar owner shall be able to control the visibility of the calendar (private, shared to a group, public).
* The calendar shall support group events.
* The calendar shall support site wide events.
** Who can submit site wide events shall be controlled by the site administrator.
** When given permission to submit site wide events, users can submit existing individual events to the site wide calendar.
** The site administrator shall be able to moderate events submitted by non-admin users.
* The calendar shall have the ability to import, export and perhaps sync using the iCal ([http://tools.ietf.org/html/rfc5545 RFG5545]) format.
** Ability to share with services like [http://upcoming.yahoo.com/ Upcoming], [http://www.dopplr.com/ Dopplr], or [http://www.google.com/calendar Google Calendar], so events only have to be entered once.
* The calendar shall support [http://microformats.org/wiki/hcalendar HCalendar].
* The calendar shall support recurring events.
* The calendar shall have an efficient implementation (responsive).
** A smart design will be needed to support recurring events without causing a lack of responsiveness.
* The calendar shall support for event reminders.
* The calendar shall support sending event invitations and tracking responses.
* The calendar shall implement Geeklog's [[Multilingual Support|Multi-language support]].

== Bonus ==
* A migration utility to convert existing Geeklog calendar tables to work with the new plugin.

== Level of Difficulty ==
''medium'' to ''difficult''

The level of difficulty on this project will be dependent upon the chosen design and implemented features.

== Further Reading ==

[[Category:Summer of Code]] [[Category:Development]]

← Older revision		Revision as of 11:03, 6 March 2010
Line 54:		Line 54:
	The level of difficulty on this project will be dependent upon the design and feature set chosen to be implemented.		The level of difficulty on this project will be dependent upon the design and feature set chosen to be implemented.

		+	'''Possible Mentor:''' [http://www.geeklog.net/users.php?mode=profile&uid=1461 Vincent Furia]

	== Further Reading ==		== Further Reading ==

@@ Line 30: / Line 30: @@
 * The calendar shall implement Geeklog's [[Multilingual Support|Multi-language support]].
 * The calendar shall support "locales".
-** Configurable date format (e.g. 01/21/2010 vs 2010/01/21 vs 21/01/2010)
+** Configurable date and time format (e.g. 01/21/2010 vs 2010/01/21 vs 21/01/2010, 8:00pm vs 20:00h)
 ** Configurable first day of week (e.g. Monday vs Sunday)

@@ Line 19: / Line 19: @@
 ** The site administrator shall be able to moderate events submitted by non-admin users.
 ** Only site administrators shall be able to modify existing events.
-* The calendar shall have the ability to import, export and perhaps sync using the iCal ([http://tools.ietf.org/html/rfc5545 RFG5545]) format.
+* The calendar shall have the ability to import, export and perhaps sync using the iCal ([http://tools.ietf.org/html/rfc5545 RFC5545]) format.
 ** Ability to share with services like [http://upcoming.yahoo.com/ Upcoming], [http://www.dopplr.com/ Dopplr], or [http://www.google.com/calendar Google Calendar], so events only have to be entered once.
 ** The calendar shall optionally support WebDAV ([http://tools.ietf.org/html/rfc2518 RFC2518]) for calendar and schedule sharing.

@@ Line 21: / Line 21: @@
 * The calendar shall have the ability to import, export and perhaps sync using the iCal ([http://tools.ietf.org/html/rfc5545 RFG5545]) format.
 ** Ability to share with services like [http://upcoming.yahoo.com/ Upcoming], [http://www.dopplr.com/ Dopplr], or [http://www.google.com/calendar Google Calendar], so events only have to be entered once.
 * The calendar shall support [http://microformats.org/wiki/hcalendar HCalendar].
 * The calendar shall support recurring events.
@@ Line 45: / Line 46: @@
 == Further Reading ==
-===From the Bug Tracker===
+===References===
 * [http://project.geeklog.net/tracking/view.php?id=974 0000974: Make order of day/month/year dropdowns configurable in editors (without template change)]
 * [http://project.geeklog.net/tracking/view.php?id=635 0000635: Required visual cues in Calendar Plugin's Event Editor v1.5b1]

@@ Line 4: / Line 4: @@
 Geeklog's current calendar plugin is old and unmaintainable. It has no support for modern calendar standards and cannot support such basic functionality as recurring events. It's interface is antiquated and its sharing/group features are extremely limited.
-A new Calendar plugin, written from scratch, could be designed from the group up to work with calendar standards and support a wide variety of use cases.
+A new Calendar plugin, written from scratch, could be designed from the ground up to work with calendar standards and support a wide variety of use cases.
 == Requirements ==
-Listed below are an initial set of requirements. Students applying to complete this project can use the below list as a design outline.
+Listed below are an initial set of requirements. Students applying to complete this project can use the below list as a design outline. Though, don't let the requirement set here limit you!
 * The calendar shall support events for individual users.
-** Individuals shall be able to create multiple calendars (limited to number defined by an administrator).
+** Individuals shall be able to create multiple calendars (possibly limited to a number defined by an administrator).
 ** The calendar owner shall be able to control the visibility of the calendar (private, shared to a group, public).
 * The calendar shall support site wide events.
 ** Who can submit site wide events shall be controlled by the site administrator.
@@ Line 19: / Line 19: @@
 ** The site administrator shall be able to moderate events submitted by non-admin users.
 ** Only site administrators shall be able to modify existing events.
 * The calendar shall support recurring events.
 * The calendar shall have an efficient implementation (responsive).
 ** A smart design will be needed to support recurring events without causing a lack of responsiveness.
 * The calendar shall implement Geeklog's [[Multilingual Support|Multi-language support]].
 * The calendar shall support "locales".
@@ Line 34: / Line 28: @@
 ** Configurable first day of week (e.g. Monday vs Sunday)
-== Bonus ==
+=== Bonus Items ===
 * A migration utility to convert existing Geeklog calendar tables to work with the new plugin.
 * Create a calendar block for display in Geeklog's left or right blocks.
@@ Line 43: / Line 51: @@
 ''medium'' to ''difficult''
-The level of difficulty on this project will be dependent upon the chosen design and implemented features.
+The level of difficulty on this project will be dependent upon the design and feature set chosen to be implemented.