FUGU	Weekly Team Task and Status Meeting Report	Report #3

Team Fugu	Meeting Date: 2004.02.11
Project Title: OpenBSD Tools
Team members present: All (Erik, Nauman, Thad, Ben)	On-time: All (Erik, Nauman, Thad, Ben)

Progress of Team Meetings

last meeting(s): 2004.02.02, 02.04, 02.06, 02.08

next meeting(s): 2004.02.11, 02.13

Communication Problems: None.

Last week’s Tasks: Status

Task Title: Peer evals	Task Initiation: Various	Orig. Due Date: 2004.02.02	Status: Complete
Who (%): Each team member individually
Description: First peer evaluation
Outcome/Progress: Each team member finished his own peer evaluation.
Task Eval: Relatively trivial. All team members doing well, attending meetings and performing their required tasks.

Task Title: CVS/shell scripting research	Task Initiation: 2004.01.30	Orig. Due Date: Rough	Status: This phase complete
Who (%): Ben: 70%; Erik: 30%
Description: Researching shell scripting for main interface and CVS for version handling.
Progress: We have finished our initial research into CVS and set up a repository in fugu/cvs. We have examined some of the shell scripts for the existing OpenBSD install and found it lacking, insufficient to build on except from a conceptual standpoint.
Task Eval: The early work is done. We are still exploring methods for coding the tools.

This week’s Tasks: Work plan

Task Title: Requirements document	Task Initiation: 2004.02.02	Orig. Due Date: 2004.02.13	Status: Expect to complete first draft tonight
Who (%): Ben: 40%; Erik: 20%; Nauman: 20%; Thad: 20%
Description: Requirements document to explain what is needed for the project
Progress: First draft is nearly complete. We expect to send a finished copy to the sponsor tonight in preparation for Wednesday's meeting (see below).

Task Title: Requirements meeting with sponsor	Task Initiation: 2004.02.09	Orig. Due Date: 2004.02.13	Status: Scheduled for 2004.02.11
Who (%): All team members will attend.
Description: We will meet with the sponsor and go over the draft of our requirements document, resolve any questions on either side, and fix any inconsistencies in expectations.

Task Title: Project presentation	Task Initiation: 2004.02.09	Orig. Due Date: 2004.02.13	Status: In progress
Who (%): Intended to be split relatively evenly; Nauman will integrate various portions
Description: Presentation of project status
Progress: We have split up the various portions of the project for individual work and will integrate them at the next meeting.

Task Title: Project development plan revision	Task Initiation: 2004.02.09	Orig. Due Date: 2004.02.16	Status: In progress
Who (%): Whole team
Description: Revise development plan based on Dr. Doerry's suggestions and observations

Task Title: Peer evals	Task Initiation: Various	Orig. Due Date: 2004.02.13	Status: Various
Who (%): Each team member individually
Description: Second peer evaluation

Task Title: Home test machine acquisition	Task Initiation: Various	Orig. Due Date: Rough	Status: Various
Who (%): Each team member individually
Description: Acquire additional test computers for home use
Progress: Nauman, Erik, and Thad have test machines. Ben has opted to learn to use Bochs to run a virtual OpenBSD install on top of his Linux installation.

Task Title: Tepatche study	Task Initiation: 2004.02.08	Orig. Due Date: None	Status: In progress
Who (%): All team members
Description: Ernest has suggested we base our automatic patching tool on Tepatche, an existing automated OpenBSD patching tool. We need to familiarize ourselves with the Tepatche program and code, determine its strengths and weaknesses, and confirm with Ernest what we need to add.
Progress: We have read the documents on the Tepatche website, installed it on the group test machine, and given it a quick run. We still need to examine the code and determine strengths and weaknesses and specifically what we need to add.

Task Title: Installation flow chart	Task Initiation: 2004.02.09	Orig. Due Date: None	Status: Pending
Who (%): Ben
Description: Ben has volunteered to make a flow chart representing the existing OpenBSD installation procedure so that we have a visual guide for what our installation procedure needs to do.

Upcoming Tasks: Planning

Task Title: Tool study	Who (%): All team members; emphasis on Erik and Ben	Rough Due Date: Next two weeks
Description: We are looking for more specific tools – shell scripting, Perl, Ncurses, ISO & FS extraction / creation, and others – for how best to design our tools.

Task Title: Logo selection	Who (%): Thad, Ben	Rough Due Date: By this weekend if time permits
Description: We should have a project logo, presumably a fugu. Adapting from other OpenBSD logos is a start, but we'd like to find an artist to draw an original logo all our own.
Progress: Ben and Thad have been speaking with Jon Gardener, a graphic design student, who is eager to help with a design.

Task Title: T-shirt design	Who (%): Thad	Rough Due Date: Next two weeks
Description: Tangential to project, but once logo is selected, FUGU T-shirt (parody of “FUBU” line) should be easy to generate. Intend to use 99dogs.com.

Timeline check:

Meeting all deadlines.

Notebook current.

Website in good shape.

Other Problems / Other Issues:

Deadlines are tight and we are doing more work and meeting more often than previously, but no major issues at this point. Project going well.

2004-02-09T17:43:37