Differences between revisions 4 and 5
Revision 4 as of 2005-07-25 16:02:54
Size: 1349
Editor: anonymous
Comment:
Revision 5 as of 2005-07-25 21:32:18
Size: 1604
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
 * Do not start before 10:00 (or possibly 11:00)  * Do not start before 10:00 (or possibly 11:00). madduck sez: I actually would prefer them to be at 9 and end early so that the afternoon is mostly free. Maybe have the more specific talks in the morning and the broader ones in the afternoon? We should probably calculate for the obligatory siesta too!

<<< DebConf6

DebConf6 Suggestions

Things to keep in mind, learned from previous experience:

Accomodation

  • Plan for at least 300, maybe 400 people.
  • Try to get some accomodation where most people will be happy. It does not need to be a hotel, but it does need to have beds (and curtains :).
  • In Comas, add a field "wants to share room with", and "does not want to share room with".
  • Define where the DebConf reception, the Server Room and the Store Room will be, in advance.

Food

  • There are a lot of Vegetarians and Vegans among the Debian community. It's important to take this into account when talking with the food guys.
  • Also, it's nice to have some flexibility. I.e. allow for people to switch to vegetarian meals, if the non-vegetarians suck.
  • It would be nice not to need food tickets: use a bar code reader and read the person's badge? (this is sort of geekie, but would be really nice).

Website

  • Have all information online and easy to find.
  • Do not have confusing links, like allowing to register for the web interface instead of Comas.

Talks

  • Do not start before 10:00 (or possibly 11:00). madduck sez: I actually would prefer them to be at 9 and end early so that the afternoon is mostly free. Maybe have the more specific talks in the morning and the broader ones in the afternoon? We should probably calculate for the obligatory siesta too!
  • Have the talks as near as possible from the hacklab.
  • Have the full schedule published, at least two weeks before the conference.