ITK/Release 4/New Code Contribution Process

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

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

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. Follow this procedure to add a Wiki example.

NOTE: The examples illustrate existing ITK classes and do not introduce new classes.