Minutes for Meeting 11

  1. Welcomed everyone to the project (sometimes for the 2nd or 3rd time). Described that we have weekly meetings over IRC. If you come to the meeting late, you can't complain if you get sucky tasks.
  2. Overhead Items
    1. Recorders are tasked with saving a log of the weekly meetings, writing up a summary (meeting minutes) and sending them to the webmasters for posting on the web site. We have 2 recorders, for redundancy and workload sharing. They are: Sobby and Larry.
    2. For web masters, Schoudel is staying on. Uday would like to learn how to do HTML, so Schoudel can assign tasks to him. Sandra will act as a backup webmaster if needed.
    3. Saurabh was requested to get a SourceForge account and tell Sid.
    4. Schoudel will post HW1 on the web site on Friday so it's available to the team members.
    5. For configuration management, each team member is tasked with setting up the standard source tree, and be able to compile and run dbViZ. Instructions on how to do this are on the site. This should be completed by next week. Those having troubles can ask Ross. Ross is authorized to slap them with wet fish if they ask questions that are answered in the CM documents.
    6. Java. Those that do not know Java should understand that they will have to teach themselves it if they wish to code. We won't force people to code; there are plenty of documentation tasks. This was mentioned to try to address the scheduling risk.
    7. Overhead-related questions resulted in:
      • Ross will update the Config management doc to include specific tag and release names.
  3. Project Plan
    1. The project plan calls for four phases: 3 construction and 1 transition.
    2. For use case prioritization:
      • We decided to make query construction and execution low priority. Sid will reconsider this issue for next week's meeting..
      • We will implement the database-import use case.
  4. Tasking
    1. Document revisions: SDP, Test Plan
      • Sandra will work on a revision of the Software Development Plan doc.
      • Jim and Sobby will work on a revision of the Master Test Plan doc.
    2. Get people knowledgeable in JDBC to prep for design and coding.
      • Larry and Uday are tasked with learning JDBC and dbViZ's schema import architecture.
    3. Ross will setup an Oracle server for testing with Sid's assistance.