ITK/Release 4/New Code Contribution Process: Difference between revisions

From KitwarePublic
< ITK‎ | Release 4
Jump to navigationJump to search
Line 15: Line 15:
== New Classes and Filters ==
== New Classes and Filters ==
A new class (or filter) must be submitted to the [http://www.insight-journal.org/ Insight Journal].
A new class (or filter) must be submitted to the [http://www.insight-journal.org/ Insight Journal].
# Submission to the Insight Journal
# [http://www.insight-journal.org/help/submission Submission to the Insight Journal]
# Code Reviewed using the [[ITK_Release_4/Modularization/Code Reviews/Checklist|Checklist]]
# Code Reviewed using the [[ITK_Release_4/Modularization/Code Reviews/Checklist|Checklist]]
# Posted as Gerrit Patches
# Posted as Gerrit Patches

Revision as of 19:31, 11 June 2011

This page describes the multiple mechanisms available to contribute code to the ITK Ecosystem.

Overview

Level of Contribution

Bug Fixes

Bug fixes are contributions that repair defects reported in the Mantis Bug Tracker or repair daily defects that creep into ITK.

  1. Follow the procedure to become an ITK developer.
  2. Posted as Gerrit Patches
  3. Peer-reviewed
  4. Cdash@home tested
  5. Merged

New Classes and Filters

A new class (or filter) must be submitted to the Insight Journal.

  1. Submission to the Insight Journal
  2. Code Reviewed using the Checklist
  3. Posted as Gerrit Patches
  4. Peer-reviewed
  5. Cdash@home tested
  6. Merged

Internal Modules

External Modules

External Layers

Applications

Applications are programs that often provide a GUI and/or use other toolkits, e.g. VTK.

Wiki Examples

Wiki examples are independent, compilable examples that illustrate ITK concepts. The procedure for adding a Wiki example is define here.