Difference between revisions of "Documentation/Labs/EasyExtensionContribution"

From Slicer Wiki
Jump to: navigation, search
m
m
Line 1: Line 1:
The current process to contribute a new or updated [[Documentation/Nightly/Developers/Extensions/DescriptionFile|extension description file (*.s4ext)]] is documented [[Documentation/Nightly/Developers/Tutorials/Contribute_Extension_Description_File|here]].
 
  
  
We all agree it involves a lot of steps. To simplify this process, the idea would be to provide a set of git custom command automating most of it.
+
This page serves as roadmap for the Slicer Extensions project.
  
 +
= Roadmap =
  
 +
== Extension contribution process ==
  
The proposed improvement would be:
+
=== In progress ===
  
1. Clone the ExtensionsIndex
+
=== Done ===
  
2. Checkout either <code>master</code> or <code>4.3</code> branch
+
=== To be done ==
  
3. run <code>./Utilities/SetupForDevelopment.sh</code>
+
== Extension catalog ==
  
4. run this command:
+
=== In progress ===
 +
* [http://na-mic.org/Mantis/view.php?id=3564 3564: Add search option in extension manager]
  
    git prepare-extension-update /path/to/description-file.s4ext
+
=== Done ===
  
This would:
+
=== To be done ==
* locally create the topic "update-<ExtensionName>[-X.Y]" or "add-<ExtensionName>[-X.Y]"
 
* generate meaningful commit message if possible (for svn and git based repo)
 
* associate compare link if possible
 
  
5. Then, if everything look good:
+
== Extension manager ==
  
  git push-extension-update
+
=== To be done ===
 
+
*
This would publish the topic on your fork and submit the pull request
+
*
 +
*

Revision as of 17:45, 27 February 2014

Home < Documentation < Labs < EasyExtensionContribution


This page serves as roadmap for the Slicer Extensions project.

Roadmap

Extension contribution process

In progress

Done

= To be done

Extension catalog

In progress

Done

= To be done

Extension manager

To be done