ITK/Tcons/Agendas/2011 06 03: Difference between revisions

From KitwarePublic
< ITK‎ | Tcons‎ | Agendas
Jump to navigationJump to search
 
(11 intermediate revisions by 2 users not shown)
Line 22: Line 22:
* Chapel Hill, North Carolina.
* Chapel Hill, North Carolina.
* The Meeting will take place at the Franklin Hotel
* The Meeting will take place at the Franklin Hotel
* Registration form will send to you by email.
* [[Media:ITKv4 Summer2011Meeting Registration.pdf |Registration Form]]
** [[Summer_ITKv4_2011_Meeting#Meeting_Agenda|NEW AGENDA]]
* [[Summer_ITKv4_2011_Meeting#Meeting_Agenda|NEW AGENDA]]


== BETA RELEASE ==
== BETA RELEASE ==
Line 29: Line 29:
* Postponed.
* Postponed.
** New Date :  July 30 ?
** New Date :  July 30 ?
** What are the non-ready tasks that led us to postpone the Beta ?
** Why is that they are not ready ?
** Need to restructure ?
== Next ALPHA ==
* Next Alpha will be tagged on June 15.
* Next Alpha will be tagged on June 15.
** What will be ready by June 15 ?


== ITKv4 Status ==
== ITKv4 Status ==


* Lack of Focus
* Lack of Focus
* Feature Creep
* Project Schedule
* Project Schedule
* State of the Refactoring Efforts ?
* State of the Refactoring Efforts ?
* State of A2D2 ?
* 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
** http://www.atlassian.com/software/greenhopper/
** http://www.atlassian.com/software/jira/
=== 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
=== 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 =
= Technical Topics =
Line 98: Line 146:


* Design discussion
* Design discussion
* Add new part of pipeline to check inputs
**http://review.source.kitware.com/#change,1820


==== Constant Inputs ====
==== Constant Inputs ====

Latest revision as of 14:26, 3 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

Project Management

June Meeting in Chapel Hill

BETA RELEASE

  • Postponed.
    • New Date : July 30 ?
    • What are the non-ready tasks that led us to postpone the Beta ?
    • Why is that they are not ready ?
    • Need to restructure ?

Next ALPHA

  • Next Alpha will be tagged on June 15.
    • 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 ?

Using JIRA at U.Iowa

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

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

Review Tasks

Dashboard

Monolithic Dashboard

Valgrind Errors

  • 2,000 in one Machine? and 0 in another?

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

Gerrit Reviews

BinaryFunctorImageFilter

Managing Physical Space

Constant Inputs

  • Luis: proposal for backing out changes for supporting constant inputs. Restoring the operation with a constant filters.

SimpleITK