18 month Review Meeting Tcon
From IGSTK
Contents |
IGSTK 18 Month Project Review Meeting
1 June 2006 IGSTK 18mo Review Meeting Slides
Notes by Kevin Cleary
Slide 9: Luis: maintenance will become the major part of the toolkit -need some more regression tests
Slide 13: current process: mistake pointed out by David: don’t move code in until is it reviewed.
- David noted we need places on the Wiki to have requirements from new users
- Status for requirements: unconfirmed, new, assign, verified, closed, etc
- How will we handle requirements in maintenance mode?
- Need to keep track of requirements from new users
- Open up sandbox to other users
- Review requirements perhaps quarterly
- How to get resolution of issues as noted by David
- Have someone responsible for the topic
- Put more details of discussion on Wiki
Action items
- Slide 7: David to manage tcons until end of August
- Slide 7: Patrick to take over on monthly tcons after that
- Slide 6: Patrick to monitor user list and contact others are needed, but all are welcome to reply to the user’s list as they wish
- Slide 13: Brian will work with Luis to get rejected added to the bug tracker and move requirements as necessary
- Slide 13: The current process has some issues soon as noted by David. It was suggested that this diagram be updated by David and Brian and could be a topic of future discussions. For example, we may want to have a link to the design discussion pages on the code review pages. Also need to add headings to the REQ sections of the PDF document.
- Slide 28: in maintenance mode we should transition all classes to use these techniques as noted by Luis, particularly the event passing mechanism
- Slide 33: Luis: add check on state machines to code review list
- Slide 51: Julien: renaming of spatial objects as noted here will be done in next iteration
- Slide 43: David: tracker: consider adding MicroBird to this class if possible as Georgetown will have a 60 day loan of one of these systems soon
- Tracker action item: for iteration 9 modify tracker classes as suggested by Luis
- Slide 56: Andinet: views: need to set up more regression tests for views, discuss view class at following tcon
- Slide 69: Andinet: bug tracking: too many open bugs: need to pay attention to this
Future activities
- Publicity in Insight Journal, etc
- Can we write articles for this?
Discussion
- Collaborators
- Yves Starrveld: a long-term potential clinical user
- Funding
- Small business prospects with Kitware may still be an option
- NSF: partnerships for innovation: Kevin Gary will send the link
- Outreach: MICCAI open source workshop papers: due July 1
- http://www.insightsoftwareconsortium.org/wiki/index.php/2006_MICCAI_Open_Workshop
- Validation of the State machine: Kevin Gary
- Patrick and Julien: applications
