1 [[!meta title="Clockworks"]]
3 Hey guys, I heard there was this app called [Doodle](http://www.doodle.com/main.html). It's closed source. Let's make an open-source Doodle killer and call it Clockworks!
5 We have a mailing list - if you're interested in helping design the
6 app, just [let one of the developers know](mailto:clockworks@mit.edu)
7 and we'll add you to our mailing list, **clockworks**. Or if you just
8 want to hear more about what we're up to, blanche yourself to the
9 public list **clockworks-announce**.
13 Our Git repository is located in AFS in the clockworks locker: /mit/clockworks/clockworks.git
17 Doodle clone. 100% duplication of Doodle functionality. Modifications to improve usability as necessary.
19 What do people not like about Doodle?
22 * No obvious "I can, but would rather not"
26 * [Configure](http://docs.turbogears.org/1.0/Configuration?action=show&redirect=1.0%2FGettingStarted%2FConfiguration) the default TurboGears scaffolding
27 * Work through the [TurboGears tutorial](http://docs.turbogears.org/1.0/Wiki20/Page1) (the tutorial seems to focus on SQLObject, which is not necessarily the best thing. Maybe someone can find some better docs?)
28 * Setup database configuration and installer (an auxiliary issue is the presence of an installer for people). Also, make sure SQLAlchemy is being used
30 * <del>Make sure the default scaffolding works on Scripts (this includes running TurboGears as CGI). Any work done here should be considered for a TurboGears auto-installer, the equivalent of tgsetup) (**ezyang**)</del>
31 * Write a .gitignore file for generated/not versionable items
32 * Get friendly URLs working
33 * Learn TurboGear's templating interface (would like XSLT, but I don't think anyone else will like that)
34 * <del>Setup a zephyrbot that watches the repository</del>
38 * Python and Turbogears
40 * Use 15 minute timeslices to simplify interface (?)
51 To be transferred from the whiteboard
55 List of "screens" in Doodle
58 * Help pages (screencasts, interactive JavaScript, etc.)
59 * Schedule event (should be one-page-able)
60 * General info (title, description, name, email)
61 * Days (calendar, should be AJAX)
62 * Times (timezone (JS fill-in), add more timeslots, copypaste first row)
63 * Options (yes-no-ifneedbe, hidden poll, limit OKs)
64 * Poll created (admin, participant links)
65 * View poll (timezone, name, times, information, functions)
66 * Edit entry (completely wiki!)
69 * Calendar export (both ways)
70 * File export (excel, pdf)
71 * Subscribe (atom, and then social feed services)
73 * Admin poll (participation link)
74 * Edit poll (all original options)
76 * Delete all participants/comments
81 Doodle killer. Extra features. Pump it up.
84 * Basic: integration with ICS calendars, GoogleCalendar, Exchange, and TechTime (for faculty)
85 * Advanced: integration with MIT's course schedules, Facebook
86 * Would store persistent profiles of calendar data for users
87 * Automatically prioritize and schedule events for you
88 * Create mobile phone friendly version
98 * <a href="mailto:clockworks@mit.edu">You?</a>