Thoughts and observations about dinner arrangements on developer
gatherings:

 - Organising the dinners can be a rather time consuming task.

 - When the task is given to a person, the maximum amount of money
   available for each meal should be known.  Any special needs or
   wishes should also be mentioned at this point.

 - table reservations should be made in the beginning of the week in
   which the gathering is to happen.  This is particularly important
   when a large number of people are attending the gathering.

 - be aware that it is an advantage to be a large group of people when
   booking - this is not to be considered a burden on the restaurant.
   Try to negotiate for a good price!

 - a list of restaurants should be compiled - places we've been, and a
   short description of relevant metrics like prices, location, and
   how many people there are room for.  This is only provided as a
   starting point, to ensure the person organising the food has
   something to start out with.

 - measures should be taken to ease the job of keeping count of who
   are attending the dinners.  One solution is to make a stricter
   system for registration, and steps are being taken to this effect
   at the moment.  This is done in the form of a web interface which
   will be the only way to register for gatherings, which will, among
   other things, force each participant to say 'yes' or 'no' to dinner
   each day of the gathering.

List started by Mari Wang <mariwan@skolelinux.no>, 2005
Adopted from an email in Norwegian from Frode Jemtland 2005