We're almost there

Building my first COD7 for http://drupaljam.nl

Pulled latest Cod7 from git.
Missing Event content type with fields:
-- Title
-- body
-- location
-- event date (this was one date)
-- promotional fields like twitter and so on

Time slots:
Timeslots are a bit nerfted, display in views can't be properly customized and sorted so i replaced this content type with timefield module (one day event)
In multiple day events one wants to have some entity table of date and times (separated) so the planning can be flexible

Organizing the conference schedule:
Great work this was done in no time :) ++

Ideally one wants drag 'n drop scheduling this can could done with flag:
adding flag_weights and draggableviews could make this system even more awesome

i18n issue:
Schedule view looks cool in english however if the default language is not English it breaks for some things seem to be hardcoded.
So i had to create own view:

Schedule view details:
(grid) display of fields (timeslot, room, track, title, speaker(s), level, flag (session))
grouping field: timeslot
sorts: timeslot (ascending), room_capacity (descending) so the biggest room is left
relations: Flag: session_scedule (by user), Timeslot, Room

BOF: not working in this conference, could not reproduce the sprint, we used flipover board to do ad-hoc
[update] latest pull from git makes bof work, great work there.
Still not i18n compliant

Video:
Cod should not include a full video system. Some want to host on third party services ilke youtube or vimeo while others have full fledged ffmpeg or zendcoder capacity. So feature modules are the solution here.

Tickets.
We use pen to fill up pre printed badges (free conference many attendees who never register) however there is a great tutorial on how to do it right with QR codes and all at http://drupal.org/node/1199914

Print the Programm:
This quite a load of work to produce, it would be helpful to have some XML or other data feed that cooperates with a DTP package.

e-commerce:
This was a free conference so we didn't need e-commerce;
however http://drupal.org/project/commerce_tickets
could provide one of the last missing parts for the cod7 puzzle

"The data for the customers are saved in the Order object in the data property ($order->data), It can be used to create a report of the tickets purchased for each content, like a Ship passenger manifest, or a Bus passenger list…etc"

"…etc" immediately rings the bell of create users with rules and tokens so a list of users who are bought with the same credit card can be automatically created.
Tested this in a dev clone and did not find any issues.

Theme:
We used Omega theme, that worked pretty well.
Almost all elements we could put inline or scalable.
The big challenge for next year is how to show a multi track (4+) programme on a small screen i.e. table or grid are not suited for this.