Meeting Agenda - 8 June 2005
- CCB Presentation report (5 min)
- Other Items (5 min)
- Project Review - (20 min)
- Lessons Learned - (10 min)
- What's next for Revision 2.0 - (20 min)
Meeting Notes - 8 June 2005
CCB / Shape Tools - Notes on 8 June 2005 Meeting
Discussed:
- The CCB Presentation went well.
- CCB Feeback:
- Need products
* Need Solid Identity.
- CCB main products are software.
- CCB software will need good software engineering.
- Advised to clarify the CCB identity: what are we doing ?
- Future CCB research will need a good wayhow to represent shapes.
We are well positioned to solve that need with ShapeTools.
- Version numbering schema : we adopted Apple's convention of
<major>.<minor>.<patchlevel>[<type><release>]
Thus: current library and shape viewer is 1.0.0 .
- Jeff has added a "Reverse Points" button to viewer
to alter lighting model. This would be version 1.1.0d0
- We have two types of users:
- Neuroscientists, who will just want to use , say, the viewer.
- Algorithm developers and researchers who will use the library for computations.
- A Review of what worked, and did not work, in last development cycle.
To Do for next week:
- [X] Craig - confirm ShapeViewer CCB_Tools_MeiheXu_SurfaceExtractionTutorialUsage manual available on web
w/o having to download the entire package.
- [X] Craig - critique ShapeTools library.
- [X] Craig - distribute review items and summarize with recommendations
to improve process of software development.
- [ ] Craig (with Jeff) - revise and post Software developer style guidelines.
- [X] Craig - complete comments in ShapeViewer code, after Jeff revises the Shape3d class (see below).
- [X] Craig - Check revised ShapeViewer code into CVS as version 1.1.0d1
- [X] Craig - Check ShapeTools code into CVS as version 1.0.0
- [X] Craig - create and distribute TWiki topic to hold feature wish
lists for both Viewer and Tools.
- [ ] Jeff - critique ShapeViewer.
- [X] Jeff - Move "Shape3D" inner class to a separate, package private class.
- [ ] Jeff (with Craig) - revise Software developer style guidelines.
- [ ] All - add features to feature lists
- [ ] All - outline development plan for next 4 development cycles.
At Next Meeting (15 June 2005) :
- Plan LONI Presentation
- Select release timetable
- Outline future work plan
