Roadmap

Roadmap for Where's The Party At.

We'll do the usual Web 2.0 release thingy where we announce a private beta and collect email addresses of people and invite them in as we please. Then we'll announce a public beta and get huge.

In the beta we want:

• host a party
• find a party
• Atom
  • See http://www.codezoo.com/pub/component/5324.
• forum per party
  • See: http://wiki.rubyonrails.com/rails/pages/ForumExample
• voting
• users
  • profile
    • previous parties
    • ratings
• OpenID

Things I don't want to think about yet:

• API
  • See http://manuals.rubyonrails.com/read/book/10. Ridiculously easy? I think so. ActionWebService supports only SOAP and XML-RPC. We don't want this. Will develop something on our own.
• Flickr
  • Flickr.rb rocks. See http://redgreenblu.com/flickr/.
• Trackback
  • See http://www.sixapart.com/pronet/docs/trackback_spec. Matt will take this on when the time comes.
• mailing list
  • Should a mailing list be tied to party, or announcer? As Mike Burns throws many parties, it may be a bit silly to have a new mailing list for each. The only problem is some people on one watch list may not be interested in other parties. Discuss.
    • I'm going with tied to announcer.
• find a DJ
  • Craigslist?
• FOAF
• Structured data about a party: DJ, band, type of beer, theme
• Disclaimer
• Mashups
  • Keg
  • Party location
• Ajax!
  • Used to narrow down list of parties
    • City, State, thrower, etc ...
• iCal, duh!
  • See http://icalendar.rubyforge.org/. Sexy iCal library.