ITK/Release 4/New Code Contribution Process: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
| Line 33: | Line 33: | ||
== Wiki Examples == | == Wiki Examples == | ||
Wiki examples are independent, compilable examples that illustrate ITK concepts. | Wiki examples are independent, compilable examples that illustrate ITK concepts. | ||
Follow [[ITK/Examples/Instructions/ForDevelopers|this procedure]] to add a Wiki example. | |||
'''NOTE:''' The examples illustrate existing ITK classes and do not introduce new classes. | |||
Revision as of 19:37, 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.
- Follow the procedure to become an ITK developer.
- Posted as Gerrit Patches
- Peer-reviewed
- Cdash@home tested
- Merged
New Classes and Filters
A new class (or filter) must be submitted to the Insight Journal.
- Submission to the Insight Journal
- Code Reviewed using the Checklist
- Posted as Gerrit Patches
- Peer-reviewed
- Cdash@home tested
- 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. Follow this procedure to add a Wiki example.
NOTE: The examples illustrate existing ITK classes and do not introduce new classes.
