previous next
Satisfaction: 1
Liked_Best: Interacting with peers and attending tech talks (and giving them :-)) The \"short\" tech talks were a *great* way for me to grab a quick \"focused\" no-fluff-all-stuff overview of many topics.
Short_Talk: Like
Short_Talk_Length: 10
Short_Talk_Format: Vertical
Parallel: Just_Right
Number_Of_Parallel: 7
Format: 1+3
Later_Sessions: No
Exhibit_Hall_Hours: In 2006, the exhibit hall was only open 2 of the 3 tech talk days. I wish it had been open on the last day of the conference as well. But then again, maybe our sales VP was happy that it was not :-)
OS_Pavillion: Yes
Keynotes: Fewer
Reduced_Number_of_Keynotes: 3
Improve_Next_Year: The short talks were *great*, but:
* 1 minute break between each so I can dash from one to another (if you keep them horizontal)
* physically locate them together (same reason, again if they are horizontal)
* code camp on tutorial day(s) for those wanting to fix Eclipse bugs (er... I mean enhance Eclipse :-) People submit code topics (anything really), a few selected and featured in the code camps. Brainstorming, write stories, tests and prototyping, submit stories and code to bugzilla, done. 2 hour max from brainstorming to submitting code to bugzilla. Keep it short, suggest stories written directly into bugzilla, suggest a schedule (e.g 20 min brainstorming, 20 write stories, etc), move onto the next \"issue\" to tackle. 7 code \"issues\" in parallel x 4 2 hour blocks a day = 28 \"issues\" addressed.
Location: us_or_canada