ITK/Tcons/Agendas/2011 06 10: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(One intermediate revision by one other user not shown) | |||
Line 85: | Line 85: | ||
** http://www.atlassian.com/software/greenhopper/ | ** http://www.atlassian.com/software/greenhopper/ | ||
** http://www.atlassian.com/software/jira/ | ** http://www.atlassian.com/software/jira/ | ||
** GreenHopper 101: | |||
*** http://confluence.atlassian.com/display/GH/GreenHopper+101/?utm_source=JIRA&utm_medium=Introduction%2BGadget&utm_campaign=CAC%2BGreenHopper%20101 | |||
=== Example === | === Example === | ||
Line 165: | Line 167: | ||
== SimpleITK == | == SimpleITK == | ||
* GIT: http://itk.org/gitweb?p=SimpleITK.git | |||
**Moved Repository [[http://www.vtk.org/Wiki/ITK_Release_4/SimpleITK/Tcon_2011_6_8#IMPORTANT-new_repository-_IMPORTANT]] | |||
* Doxygen: http://erie.nlm.nih.gov/~blowek1/SimpleITK/index.html | * Doxygen: http://erie.nlm.nih.gov/~blowek1/SimpleITK/index.html | ||
Latest revision as of 13:45, 10 June 2011
How to Join the Tcon
Number to Call
Please be patient, due to some unforeseen circumstances, the call may not start on time...
- 1-800-728-9607 (in the US) or
- +1 9139049873 (international)
- access code 6815251
Webex
- Meeting link
- https://emeetings.webex.com/emeetings/j.php?ED=138191182&UID=482060457&PW=NNzJiNDk1ZGU3
Project Management
June Meeting in Chapel Hill
- Summer_ITKv4_2011_Meeting
- Will take place on June 27-29
- Chapel Hill, North Carolina.
- The Meeting will take place at the Franklin Hotel
- Registration Form
- NEW AGENDA
Schedule
BETA RELEASE
- Postponed.
- New Date : July 31
- What are the non-ready tasks that led us to postpone the Beta ?
- Why is that they are not ready ?
- SCRUM Process
- Tools: (demo) https://itk.icts.uiowa.edu/jira/secure/Dashboard.jspa
- Six weeks to Beta release
- Three Sprints (two weeks each)
- Defining goals for every sprint
- Splitting task to 2~3 days granularity
- Kitware will provide examples
Next ALPHA
- Next Alpha will be tagged on June 15.
- What will be ready by June 15 ?
- FEM ?
- LevelSets ?
- Registration ?
- DICOM ?
- Video ?
- GPU ?
- Review ?
- What will be ready by June 15 ?
ITKv4 Status
- Lack of Focus
- Feature Creep
- Project Schedule
- State of the Refactoring Efforts ?
- State of A2D2 ?
Adopting SCRUM
- We need project planning & tracking
What is SCRUM ?
- http://en.wikipedia.org/wiki/Scrum_%28development%29
- http://en.wikipedia.org/wiki/Sprint_%28scrum%29
- Sprints of 2/3 week
- Specific targets for that period
- Decomposed in tasks for 1/2 days each
- Regular short meetings
Using JIRA at U.Iowa
- Hans setup a Jira installation at U. Iowa
- We could use JIRA to record and track tasks
- Break down targets into sprints
- Break down sprints into tasks
- Tools
Example
- Sprint for the Summer Meeting
- What we want ready by that meeting
- Migration Guide XML uploads to phpfaq
- Testing data upload (workflow)
- CVPR Tutorial on ITK+OpenCV
- Report/Presentation on what is new (&ready) in ITKv4
- What we want ready by that meeting
Kitware
- We have been using SCRUM for about six months
- In three different large projects
- Excellent method for keeping track of goals and intermediate tasks
- Keeps focus
- Leads to rapid solution of roadblocks
Technical Topics
Bug Database
- Defining categories in MANTIS
- Schedule a bug triage session (next week ?)
Review Tasks
- Starting to review classes
- Target: June Meeting
- Review Directory: hackathon
- All files were classified
- https://spreadsheets.google.com/a/kitware.com/ccc?key=0ApfVzIsZe0VFdFUxdE95WE5kMVE4LTJ6b3ZYQnpRalE&hl=en&authkey=CMyS68EE#gid=0
- Missing Insight Journal references were added
- Now: Select the ones that must be moved into the toolkit
- Finally: We will move the remaining Review directory out of the toolkit and into an external module.
Dashboard
Monolithic Dashboard
- Dashboard Status - Today's Dashboard
- Need more Windows machines in Gerrit builds.
Valgrind Errors
- 2,000 in one Machine? and 0 in another?
- Almost all of these are NRRD related. Why do we see them on this build and not this other build?
Refactoring Workflow
- Right now
- code is developed on other remote
- once the code is mature, we submit to gerrit
- lost history
- refactoring may appear as single commit from one person (not team spirit oriented)
- Any other solution?
Schedule
Teaching ITK
- CVPR Tutorial : June 20th
- "ITK meets OpenCV"
- https://github.com/InsightSoftwareConsortium/ITK-OpenCV-Bridge-Tutorial
- MICCAI SimpleITK Tutorial : September
- MICCAI ITKv4 Tutorial : September
Gerrit Reviews
SimpleITK
- GIT: http://itk.org/gitweb?p=SimpleITK.git
- Moved Repository [[1]]
- Doxygen: http://erie.nlm.nih.gov/~blowek1/SimpleITK/index.html