Difference between revisions of "2013 Summer Project Week Breakout Session:SlicerExtensions"

From NAMIC Wiki
Jump to: navigation, search
m
Line 1: Line 1:
 
  [[2013_Summer_Project_Week#Agenda|Back to Summer project week Agenda]]
 
  [[2013_Summer_Project_Week#Agenda|Back to Summer project week Agenda]]
  
 +
== Before the breakout session ==
 +
# Complete the [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/StartHere New community member checklist]
 +
# [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Build_Instructions Build Slicer] revision >= 22100 with default options
  
== Topics requested by the community ==
+
 
===Infrastructure===
+
== During the breakout session ==
How much of slicer's core infrastructure should be used by extensions?
+
 
 +
* What is an extension ?
 +
 
 +
* How to
 +
 
 +
We will follow the updated documentation and
 +
 
 +
== Q&A ==
 +
 
 +
''Do not hesitate to edit this page and add more questions''
 +
 
 +
=== Infrastructure: How much of slicer's core infrastructure should be used by extensions ? ===
 
From Andra Lasso: Currently the picture is quite mixed:
 
From Andra Lasso: Currently the picture is quite mixed:
 
* Source control: separate for all extensions
 
* Source control: separate for all extensions
Line 14: Line 28:
 
* Dashboard: shared between Slicer core and extensions (extensions appear in
 
* Dashboard: shared between Slicer core and extensions (extensions appear in
 
a different category)
 
a different category)
===Simplifying the process===
+
 
* Can you make a python scripted extension without a built version of slicer?
+
=== Process: Can you make a python scripted extension without a built version of slicer? ===

Revision as of 19:11, 13 June 2013

Home < 2013 Summer Project Week Breakout Session:SlicerExtensions
Back to Summer project week Agenda

Before the breakout session

  1. Complete the New community member checklist
  2. Build Slicer revision >= 22100 with default options


During the breakout session

  • What is an extension ?
  • How to

We will follow the updated documentation and

Q&A

Do not hesitate to edit this page and add more questions

Infrastructure: How much of slicer's core infrastructure should be used by extensions ?

From Andra Lasso: Currently the picture is quite mixed:

  • Source control: separate for all extensions
  • Issue tracking: separate for most extensions
  • Module documentation: shared between Slicer core and extensions

(extensions appear in a different section)

  • Hosting of binary releases: shared between Slicer core and extensions

(extensions appear in a different category)

  • Dashboard: shared between Slicer core and extensions (extensions appear in

a different category)

Process: Can you make a python scripted extension without a built version of slicer?