Difference between revisions of "2010-09-Leadership-Brainstorming"
From NAMIC Wiki
| (16 intermediate revisions by 4 users not shown) | |||
| Line 24: | Line 24: | ||
=Computer Science= | =Computer Science= | ||
| − | *[[AlgorithmRetreat2010|Algorithm]] retreat | + | *[[AlgorithmRetreat2010|Algorithm]] retreat in Chapel Hill on Nov 5/6 |
| − | *Engineering | + | *[[EngineeringRetreat2010|Engineering]] retreat in Boston on Nov 17/18 |
**TCON participation is mandatory for each site. Each engineering group has to be represented at all engineering TCON's. | **TCON participation is mandatory for each site. Each engineering group has to be represented at all engineering TCON's. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=Outreach= | =Outreach= | ||
| Line 49: | Line 35: | ||
=Service= | =Service= | ||
* Centralize testing data outside of code repository (using method from ITKv4?) | * Centralize testing data outside of code repository (using method from ITKv4?) | ||
| + | * "Core" Slicer distributed with InsightApplications repository with ITKv4 | ||
| + | * Switch to centralized CDash ("CDash at Home") | ||
| + | * Support independent dashboard for each extension | ||
| + | ** Track platforms and slicer versions supported by each extension | ||
| + | ** Enable and track inter-extension dependencies | ||
| + | * Transition to GIT | ||
| + | ** Establish a GIT workflow / policy | ||
| + | * Support extensions hosted at other git repositories | ||
| + | ** Use ITKv4 module management technology | ||
| + | * Transition to ITKv4 | ||
* [[2010-Slicer-Factory|factory.slicer.org]] : Have the new setup ready for the AHM | * [[2010-Slicer-Factory|factory.slicer.org]] : Have the new setup ready for the AHM | ||
**superbuild | **superbuild | ||
| Line 56: | Line 52: | ||
**updating website to reflect those changes | **updating website to reflect those changes | ||
*support migration of Na-mic and Slicer websites | *support migration of Na-mic and Slicer websites | ||
| + | * [http://hub.opensolaris.org/bin/view/Project+opengrok/WebHome opengrok] for the na-mic kit? | ||
=Leadership= | =Leadership= | ||
Latest revision as of 17:30, 22 October 2010
Home < 2010-09-Leadership-BrainstormingBack to Leadership Main
Everybody
- Please check to see that you have enough money budgeted for all necessary travel expenses: Project Weeks, All-Hands Meeting (AHM), core retreats, working meetings, participation in outreach activities.
DBP
| Although the full NA-MIC team is engaged in supporting the DBPs, each DBP has been assigned specific algorithm and engineering partners from the Computer Science Cores 1A and 1B who are responsible either for providing technical support to the DBP directly, or for connecting them to the relevant NA-MIC resources. Partners have been allocated a separate line item in the budget that is distinctly allocated to support their time and travel to the DBP site. |
- Each new DBP must host an in-person kick-off meeting at their site with their algorithm and engineering partners before the end of the year. The goal of this meeting is to develop concrete and short-term plans for the DBP roadmap project.
- Each DBP will present their plans during their AHM presentation.
- It is crucial to identify the DBP engineer as soon as possible.
- wiki presence: DBP third generation
Computer Science
- Algorithm retreat in Chapel Hill on Nov 5/6
- Engineering retreat in Boston on Nov 17/18
- TCON participation is mandatory for each site. Each engineering group has to be represented at all engineering TCON's.
Outreach
- Update the website after NOGA is issued
- Plan Slicer training on the west coast
- Consider a NAMIC training activity at University of Utah to be done in conjunction with January 2011 AHM.
Service
- Centralize testing data outside of code repository (using method from ITKv4?)
- "Core" Slicer distributed with InsightApplications repository with ITKv4
- Switch to centralized CDash ("CDash at Home")
- Support independent dashboard for each extension
- Track platforms and slicer versions supported by each extension
- Enable and track inter-extension dependencies
- Transition to GIT
- Establish a GIT workflow / policy
- Support extensions hosted at other git repositories
- Use ITKv4 module management technology
- Transition to ITKv4
- factory.slicer.org : Have the new setup ready for the AHM
- superbuild
- nightlies
- extensions
- dashboards for trunk, extensions, selected
- updating website to reflect those changes
- support migration of Na-mic and Slicer websites
- opengrok for the na-mic kit?
