Things to keep in mind, learned from previous experience:
- 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.
- There is 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-vegetarian food sucks.
- It would be nice not to use food tickets: use a bar code reader and read the person's badge? (This is sort of geekie, but would be really nice.)
- Have all information online and easy to find.
- Do not have confusing links, like allowing to register for the web interface instead of Comas.
- Set in advance the dates for registration, confirmation, paper submission, talks voting, key submission, etc. Send a confirmation message with all those dates when someone registers with COMAS.
- 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 to both the hacklab and the restaurant.
- Have the full schedule published, at least two weeks before the conference.
Start at 9:00 every morning with a keynote speech and before it draw a number to give away a nice, brand new laptop to one of the persons present in the room. That was very effective during http://linux.conf.au/ in Canberra in April 2005 and IBM was the sponsor of the keynote laptops. (Suggested by anibal.)