Differences between revisions 2 and 3
Revision 2 as of 2006-05-24 01:44:07
Size: 1554
Editor: MeikeReichle
Comment:
Revision 3 as of 2006-05-24 01:47:41
Size: 1624
Editor: MeikeReichle
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 *
Line 19: Line 18:


=== Lessons learned from DC5 but still not implemented ===

 * ...

A list of clever ideas that came out of DC6. So they won't be forgotten

For now as I remember them, in no particular order or system.

  • Have people who know about infrastructure/video/accessibility look at the place well beforehand.
  • Accessibility is a must, not a plus
  • Prepare/plan for a backup location
  • Prepare a "DebConf-Box" that contains stuff (Cables, sound/video equipment, signs etc.) that is needed for every DebConf, so we don't have to get together everything from scratch every year

  • Doublecheck the local team more often, rinse, repeat
  • Make sure the local team has good personal relations with the people responsible for venue/accomodation etc
  • Assign tasks to people instead of saying "We should". We is nobody. Also give these people authority over their tasks, so they don't have to check back all the time.
  • A "Welcome" talk/session is nice, but also do a "Goodbye" session. Working until you have to leave, with no particular/official thank you doesn't make volunteers/orga people happier/more likely to help again next year.
  • Make sure sponsor money is there before DebConf begins

  • Instead of using mail/wiki for announcements use a central black/white board. No funny tech stuff. Plain old pen/chalk works best. Also make sure the info desk knows about stuff.
  • Try to outsource things when/if possible (possible examples may include network stuff, daytrip, formal dinner ...)
  • Let people know when you are (not) available so they know there is (no) use in searching for you.
  • ...

Lessons learned from DC5 but still not implemented

  • ...