WarpDoctor Agenda for June 9, 2002

1. Call the meeting to order.
2. Make sure some one else is taking the log.
3. Apache upgrade.
   1. Scheduled upgrade on Thursday went badly, as you all know.
   2. Procedures to avoid repeat of such a catasrophe in the future:
      1. Each person--e.g. Doug & Jeremy--complete the area of the project in which they are best skilled;
      2. When everyone's done, we'll meet in a separate chat (private if necessary) to discuss the merging the areas into one install or one update pkg.
      3. When everyone involved is happy with the changes, we'll install the new server SEPARATELY, and run it in parallel (using a different port #) long enough to be sure there are no bugs in it.
      4. If we find a problem, we'll fix the problem and go back to step ii.
      5. When the new version has run long enough that everyone's comfortable with it, I'll ask Jeremy as Webmaster to make the conversion to the new version.
      6. Finally, I learned this much: TAKE OUR TIME. Some of our problems resulted from communication delays that resulted in people having to rush to meet our target conversion time. I'd rather miss a target conversion time than have VOICE1 go down for a day as we did last week. :-)
   3. We are looking into different ways to access the server so we won't be depended on IW's staff.
   4. Other Apache/server related suggestions or ideas?
4. Other Business?
5. Motion to adjourn.