NoiseCal - Revision history

SpammerHellDontDelete: /* Specifications */

2010-01-25T23:00:30Z

Specifications

← Older revision		Revision as of 16:00, 25 January 2010
Line 7:		Line 7:

	= Specifications =		= Specifications =
			== Mailing List Threads ==
			* [https://www.noisebridge.net/pipermail/noisebridge-discuss/2010-January/thread.html#11661 NoiseBridge Calendar by Kelly, started on 2010-Jan-19]
			* [https://www.noisebridge.net/pipermail/noisebridge-discuss/2010-January/thread.html#11785 NoisyCalendary by Ian Atha, started on 2010-Jan-23]

	== Requirements ==		== Requirements ==
	* Publicly editable		* Publicly editable

SpammerHellDontDelete: /* Implementation */

2010-01-25T22:58:04Z

Implementation

← Older revision		Revision as of 15:58, 25 January 2010
Line 39:		Line 39:

	There is some code on [http://github.com/ github] but it's expected to be in great flux.		There is some code on [http://github.com/ github] but it's expected to be in great flux.
	* [http://github.com/thatha/noisecal thatha's repo]		* [http://github.com/thatha/noisecal thatha's repo]
	* [http://github.com/radii/noisecal radii's repo]		* [http://github.com/radii/noisecal radii's repo]

	= Meeting Notes =		= Meeting Notes =

SpammerHellDontDelete at 22:57, 25 January 2010

2010-01-25T22:57:53Z

← Older revision		Revision as of 15:57, 25 January 2010
Line 1:		Line 1:
	This page describes the specifications and implementation of a '''~~NoisyCalendar~~''', a calendaring solution that adheres to Noisebridge's practices and principles.		This page describes the specifications and implementation of '''NoiseCal''', a calendaring solution that adheres to Noisebridge's practices and principles.

	= Folks =		= Folks =

SpammerHellDontDelete: Cleaning up notes.

2010-01-25T22:57:38Z

Cleaning up notes.

← Older revision		Revision as of 15:57, 25 January 2010
Line 29:		Line 29:
	* Some kind of reputation system, likely usernames. Edits can be associated with usernames.		* Some kind of reputation system, likely usernames. Edits can be associated with usernames.
	* Tagging/Categorizing of events are useful so as to group similar events. There's a lot going on at NB! IE: "5MoF", "Conlang", "Not Happening on a Regular Basis", "Reoccuring"		* Tagging/Categorizing of events are useful so as to group similar events. There's a lot going on at NB! IE: "5MoF", "Conlang", "Not Happening on a Regular Basis", "Reoccuring"

			== Überbonus Point ==
			* Views based on tags. IE, view all room reservations for the next day/week/month on a calendar with the tag "Dark Room" or "Project Euler Group", or the word "foo" mentioned anywhere in the entry (this last one
			might make searches expensive).
			* Printable tag views. IE, I can print out all the room reservations for "Dark Room" this week and put it on the door (which will instantly be made out of date when the first edit comes along, phoey). This feature also lets conferences at NB self-schedule and you have an instantly printable/viewable calendar.

	= Implementation =		= Implementation =
	We are still at the brainstorming phase		We are still at the brainstorming and exploring phase.

	~~The~~ code is on github: [http://github.com/thatha/noisecal thatha's repo] ~~and~~ [http://github.com/radii/noisecal radii's repo].		There is some code on [http://github.com/ github] but it's expected to be in great flux.
			* [http://github.com/thatha/noisecal thatha's repo]
			* [http://github.com/radii/noisecal radii's repo]

	= ~~Meetings~~ =		= Meeting Notes =
	== 2010-01-23 15:00 ==		== 2010-01-23 15:00 ==
	* ~~replace prefixsearch~~ with ~~cateogry->getMembers~~		* We will base our work on the [http://www.mediawiki.org/wiki/Extension:Calendar_(Kenyu73) Calendar MediaWiki extension by Kenyu73].
			* Replace PrefixSearch with a category search. (Fetch all events from Category:Event.)
	* Parsing		* Parsing
	** add parsing for time		** We shall use a human-readable wiki-ish format.
	** ~~validate~~ stuff (on ArticleSave ~~or on every ViewHook~~). ~~you could get a preview, even if~~ you clicked save, if your ~~edit is invalid~~. ViewHook?		*** Every section titled '''Event Details''' shall contain details of a NoiseCal event. The section shall contain a list of key-value pairs of the form: <code>* Key: Value</code>.
	** ~~let~~ event description be wherever in the article		*** Keys and values are case-insensitive.
	* iCalendar		*** Valid keys, for now, are: "Description" (required), "When" (required), "Where", "Recurring", "Organizer". Values of "When" must be valid ISO8601 timestamps.
			** We parse out the event on save, and add categories as a layman's index. (Does this make sense?)
			** Add parsing for time.
			** Add recurring events. (this needs more thought)
			** Validate stuff (on ArticleSave). If you clicked save, but your NoiseCal-related edits do not validate, you will get a preview with an error message--as specific as possible. We could render events "in the wild" via ViewHook?.
			** Let event description be wherever in the article (currently the first line of an event article is the description).
			* Multiple events per wikipage.
			* iCalendar (RFC 5545)
	** iCalendar export		** iCalendar export
	** ~~use objectcache~~ for caching		** Use ObjectCache for caching
	* ~~we shall use a human-readable wikiformat of the format:~~		** How does iCalendar deal with past events? Do iCalendar feeds always export the entire history of a calendar?
	~~<nowiki>~~		** We should have a way to restrict an iCalendar feed to the past <code>n</code> months and to the past <code>m</code> months in the future. Defaults should be <code>n=1</code> and <code>m=3</code>.
	~~= Event Details = (any heading level is acceptable)~~

	* ~~Key: Value~~
	~~</nowiki>~~

	Valid keys, for now, are: "Description" (not optional), "When" (not optional), "Where", "Recurring", "Organizer". Values of "When" must be valid ISO8601 timestamps. Everything is case insensitive (both keys and values where applicable).

	~~We parse out the event on save, and add categories as a layman's index.~~

	How does iCalendar deal with past events? Or?

	a way to ~~only get~~ the x past months ~~of events~~. ~~default to one month~~.

SpammerHellDontDelete: /* Implementation */

2010-01-25T22:24:58Z

Implementation

← Older revision		Revision as of 15:24, 25 January 2010
Line 33:		Line 33:
	We are still at the brainstorming phase		We are still at the brainstorming phase

	The code is on github: [http://github.com/thatha/noisecal ~~thatatha~~'s repo] and [http://github.com/radii/noisecal radii's repo].		The code is on github: [http://github.com/thatha/noisecal thatha's repo] and [http://github.com/radii/noisecal radii's repo].

	= Meetings =		= Meetings =

Adi: /* Implementation */

2010-01-25T22:22:54Z

Implementation

← Older revision		Revision as of 15:22, 25 January 2010
Line 32:		Line 32:
	= Implementation =		= Implementation =
	We are still at the brainstorming phase		We are still at the brainstorming phase

			The code is on github: [http://github.com/thatha/noisecal thatatha's repo] and [http://github.com/radii/noisecal radii's repo].

	= Meetings =		= Meetings =

SpammerHellDontDelete: Undo revision 9566 by 75.101.62.88 (Talk)

2010-01-24T06:17:41Z

Undo revision 9566 by 75.101.62.88 (Talk)

← Older revision		Revision as of 23:17, 23 January 2010
Line 2:		Line 2:

	= Folks =		= Folks =
	* [[User:~~httf~~\|Kelly]]		* [[User:hurtstotouchfire\|Kelly]]
	* [[User:Leif\|Leif]]		* [[User:Leif\|Leif]]
	* [[User:Thatha\|Ian]]		* [[User:Thatha\|Ian]]

SpammerHellDontDelete: /* Folks */

2010-01-24T06:17:00Z

Folks

← Older revision		Revision as of 23:17, 23 January 2010
Line 2:		Line 2:

	= Folks =		= Folks =
	* [[User:~~hurtstotouchfire~~\|Kelly]]		* [[User:httf\|Kelly]]
	* [[User:Leif\|Leif]]		* [[User:Leif\|Leif]]
	* [[User:Thatha\|Ian]]		* [[User:Thatha\|Ian]]

Thatha: /* 2010-01-23 15:00 */

2010-01-24T01:48:27Z

2010-01-23 15:00

← Older revision		Revision as of 18:48, 23 January 2010
Line 55:		Line 55:

	How does iCalendar deal with past events? Or?		How does iCalendar deal with past events? Or?

			a way to only get the x past months of events. default to one month.

Thatha: /* 2010-01-23 15:00 */

2010-01-24T01:46:36Z

2010-01-23 15:00

← Older revision		Revision as of 18:46, 23 January 2010
Line 46:		Line 46:
	<nowiki>		<nowiki>
	= Event Details = (any heading level is acceptable)		= Event Details = (any heading level is acceptable)

	* Key: Value		* Key: Value
	</nowiki>		</nowiki>

	Valid keys, for now, are: "Description", "When", "Where", "Recurring", "~~Organiser~~"		Valid keys, for now, are: "Description" (not optional), "When" (not optional), "Where", "Recurring", "Organizer". Values of "When" must be valid ISO8601 timestamps. Everything is case insensitive (both keys and values where applicable).

			We parse out the event on save, and add categories as a layman's index.

			How does iCalendar deal with past events? Or?