add some good tasks to get started

[wiki.git] / projects / clockworks.mdwn

diff --git a/projects/clockworks.mdwn b/projects/clockworks.mdwn
index db045b5892c960d652a6fec508f7fa32cb7fa1f5..5554ad4abd44c265c3b77eac145efcb93fa9d0d8 100644 (file)
--- a/projects/clockworks.mdwn
+++ b/projects/clockworks.mdwn
@@ -2,7 +2,11 @@
 
 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!
 
-We have a mailing list - if you're interested in helping design the app, or if you just want to hear more about what we're up to,  blanche yourself onto **clockworks**.
+We have a mailing list - if you're interested in helping design the app, or if you just want to hear more about what we're up to,  just blanche yourself onto **clockworks**.
+
+## Development info
+
+Our Git repository is located in AFS in the clockworks locker: /mit/clockworks/clockworks.git
 
 ## Phase 1
 
@@ -13,12 +17,29 @@ What do people not like about Doodle?
 * Too much clicking
 * No obvious "I can, but would rather not"
 
+### What to do?
+
+* Configure the default TurboGears scaffolding
+* 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?)
+* Setup database configuration and installer (an auxiliary issue is the presence of an installer for people). Also, make sure SQLAlchemy is being used
+* Learn SQLAlchemy
+* Make sure the default scaffolding works on Scripts
+* Write a .gitignore file for generated/not versionable items
+* Get friendly URLs working
+* Learn TurboGear's templating interface (ezyang would like XSLT, but I don't think anyone else will let him use that)
+
 ### Architecture
 
 * Python and Turbogears
 * Git repository
 * Use 15 minute timeslices to simplify interface (?)
 
+### Principles
+
+* Simplicity
+* Extendibility
+* Open Source
+
 ### Schema
 
 To be transferred from the whiteboard
@@ -27,12 +48,43 @@ To be transferred from the whiteboard
 
 List of "screens" in Doodle
 
+* Home page
+* Help pages (screencasts, interactive JavaScript, etc.)
+* Schedule event (should be one-page-able)
+  * General info (title, description, name, email)
+  * Days (calendar, should be AJAX)
+  * Times (timezone (JS fill-in), add more timeslots, copypaste first row)
+  * Options (yes-no-ifneedbe, hidden poll, limit OKs)
+  * Poll created (admin, participant links)
+* View poll (timezone, name, times, information, functions)
+  * Edit entry (completely wiki!)
+  * Delete entry
+  * Add a comment
+  * Calendar export (both ways)
+  * File export (excel, pdf)
+  * Subscribe (atom, and then social feed services)
+  * Embed poll (iframe)
+* Admin poll (participation link)
+  * Edit poll (all original options)
+  * History
+  * Delete all participants/comments
+  * Delete poll
+
 ## Phase 2
 
 Doodle killer. Extra features. Pump it up.
 
 * Integration
-** Basic: integration with ICS calendars, GoogleCalenar, Exchange, and TechTime (for faculty)
-** Advanced: integration with MIT's course schedules
-** Would store persistent profiles of calendar data for users
-* automatically prioritize and schedule events for you
+  * Basic: integration with ICS calendars, GoogleCalenar, Exchange, and TechTime (for faculty)
+  * Advanced: integration with MIT's course schedules, Facebook
+  * Would store persistent profiles of calendar data for users
+* Automatically prioritize and schedule events for you
+* Create mobile phone friendly version
+
+## Developers
+
+* Geoffrey Thomas
+* Paul Baranay
+* Edward Yang
+* Paul Weaver
+* <a href="mailto:clockworks@mit.edu">You?</a>