Planning meeting notes for 2008-07-15

Igal Koshevoy

Ian Dees

Ed Borasky

Interacted with potential sponsors, competitors and speakers.

Created todo page to track tasks and contacts.

Updated competition page to more clearly define requirements and generalize terms so that we can accept any persistent storage mechanism, not just SQL databases.

Ask audience members to raise their hand if they want to be on the judging panel.

Pick someone outside our usual group that doesn't personally know many within the audience, and just have them randomly choose 10 people to be on the panel

After coding is done, the panel will rank each team to determine their ranked order

We may have 5 teams: Rails, Django, Symfony, Drupal, Seaside.

We probably can only run 3 teams concurrently.

We can run two heats, one set of teams builds their apps, then the second team goes.

We can run Rails, Django, Symfony first, and the Seaside and Drupal teams second

We can sequester the later teams so they don't learn about the “secret ingredient” extra requirements until they start coding.

5 minutes for intro

20 minutes for first heat

5 minutes for transition

20 minutes for second heat

10 minutes for judging and awards