i10 Thoughts

[ All in my opinion, of course ]

We need to have 2 or 3 meetings prior to i10.

The first meeting should deal with the network configuration.  Everything from
the hardware, up to and including the game server software.  Proposed
attendees:

    Wizzo
    Bugs
    Culture
    Tango
    Nik
    Pumpkin
    tguyver (IRC op)
    WildHog (Intranet requirements)
    Killing
    FearHawk

The second meeting should deal with the configuration of the game servers,
tournament system, and so forth.  Proposed attendees:

    Wizzo
    Killing
    All the head game admins (not all the red shirts).

Killing thinks this can be done by e-mail/IRC, and won't need a physical
meeting.

The third meeting should be a yellow shirt training day (or training weekend).

The key is going to be documenting things.  I don't want a repeat of the i9
experience, where work had to be halted when key members of staff were
unavailable for some reason, and no one was quite sure how things were
supposed to be configured.

I'm really only directly concerned with the first meeting, so...

Proposed agenda for first meeting:

  *  Identify which games MPUK will be running servers for

  *  Document the network design, and assign IP ranges to individual 
     networks -- the network maps at http://people.freebsd.org/~nik/mpuk/
     might be a sensible place to start.

  *  Identify the server services.  A starting list is:

       DHCP
       DNS
       FTP
       IRC
       HTTP
       Games
       Master servers

  *  Identify non-server tasks.  A starting list is:

       Extreme switch configuration (port allocation, etc)
       UPS arrangements
       Power supply
       Staff room layout
       Staff room cabling
       "Task" documentation
         -- The sort of thing we can all do, if we have a step-by-step
	    guide to hand.  For example "Blocking a MAC address at the
	    Extreme switches".  We need to identify these tasks.
       
  *  Assign 'owners' for each service and task.  Some might have several
     owners -- FTP, for example, where one group is responsible for the 
     service, another for the content.  We also need probably at least one
     additional person (a) for backup (b) to make sure that thing is
     documented properly.

  *  Determine how to handle porn/warez/misc. file sharing at the event.

     [ "file share" == an open file share, FTP site, web server, or anything
                       else that can be used to do 
    
     There are some questions that I think need to be answered by a lawyer 
     first, irrespective of what are own views might be:

       1.  Do we have the right to port-scan individual hosts, if we don't
           explicitly tell people that's what we do?

       2.  Can we port-scan even if we do say that's what we do?

       3.  We discover an open file share.  Can we go in, get a file listing,
           or is this trespass?

       4.  We go in and get a file listing.  It looks illegal.  Can we 
           download it to find out?

       5.  Assume it is illegal.  Does MPUK have a legal obligation to inform
           the relevant authorities?

       6.  What about people swapping CDs, or, as has happened, 9GB discs
           about the place?

     I think the answers to those will play a big part in deciding what we
     have to do.

  *  Schedule the setup tasks (including those that can happen before the 
     event setup actually starts -- DNS configs, etc).

  *  Troubleshooting tree for the yellow shirts?

Probably much more. . .