Contributing

Extension description files

To contribute an extension description file, consider the following check list:

1. Extension belongs to Category 1 or Category 2 as described in Slicer requirements
2. Set up an account on the extension server and obtain an API key
3. Extension has been built and tested on the following platform: Linux, MacOSX and Windows. You could for example do an ExperimentalUpload and make sure the extension can be installed successfully. See manual build
4. Fork ExtensionIndex
5. Create an issue on Slicer/ExtensionsIndex tracker. Issue title should be <ExtensionName> - Add extension, issue description should provide details about the extension
6. Clone your fork, then create a topic named <IssueNumber>-add-<ExtensionName>

git clone [email protected]:<yourlogin>/ExtensionsIndex SlicerExtensionsIndex
cd SlicerExtensionsIndex
git checkout -b <IssueNumber>-add-<ExtensionName>

7. Commit your description file. Commit title should be Add <ExtensionName> extension and the the issue number should be reference adding See issue #<issuenumber> at the end of the commit message.
8. Push the topic to your fork and Slicer folks will be automatically notified
9. That's it !

Remarks:

• <IssueNumber> and <ExtensionName> should be replaced with their actual value.

To contribute fixes associated to your extension, consider the following check list:

TBD

Dashboard submissions

Submission of experimental builds are welcome. See manual build instructions.

Submission of either continuous or nightly builds of extensions on Slicer CDash should be done solely by the slicer factory machine maintained by Kitware folks. While nothing prevent such submission from happening, it won't be possible to upload extensions on the extensions server without the appropriate credentials.