IGSTK Weekly T-con March 24, 2005 1pm EST *** Reminder: Passcode has changed! Agenda: 1. Project updates (KC) 1. Updates relevant to Advisory Board Meeting? (KC) 2. Update on tracking code, licensing, and DG's status? (KC, DG) 2. Development status 1. Iteration 2 - Waiting on a release build on the Wiki. - Is this even important? Is it enough to just ensure CVS is tagged? 2. Iteration 3 status 1. Requirements for Iteration 3 on the Wiki need to be updated. 2. Updates on design and implementation progress. (LI) 3. Decision point: Integrate new tracking code for this iteration or go back to simulated interface? - The decision last week was to attempt to wrap the Atamai code as a separate "R&D" project - Requirements for a simulated interface replaced with plans to make tracker Internet-accessible. 4. Initially planned simple logging. In light of 4.2 below, what is next? 3. Review of action items / individual status 1. A reminder to please put your update under the status page for this date to save time here 4. Technical topic: (Luis) 1. KG raised questions via email on 2/23 2. Logging (LI, HS, JJ) - Log4cxx issues - ITK plans - Do we understand our logging requirements? 5. Any other business Outstanding Action Items: * Brian Blake: 1. Send requirements document back to KG * Kevin Gary: 1. Complete requirements process on Wiki (defer to BB's #1) * Andy: * Kevin Cleary: 1. Work contractual/licensing issues with Atamai (done?) 2. Set agenda for Advisory Board meeting (finalized?) * Luis: 1. Iteration 2 CVS tag * Sohan: 1. Create page with licensing information (status?) * Julien: * Hee Su: * Other: Updated Future Milestone Dates: * February 4 - April 1: Iteration 3 development, "Demo Application with State Machine + Timestamp support" * April 4 - April 8: Iteration 3 review activities * Iteration 4 has been cancelled in favor of stabilizing Iteration 3 and Tracker before April advisory board meeting. * April 12 - April 13: IGSTK Advisory Panel Meeting * May: Iteration 4 / Release 2 Planning