Developer Meetings/20140527 - Revision history

JChris.FillionR: /* Conclusion */

2014-05-27T19:01:45Z

Conclusion

2014-05-27T19:01:18Z

Conclusion

2014-05-27T18:59:26Z

Conclusion

2014-05-27T18:53:16Z

To discuss

2014-05-27T18:37:27Z

Conclusion

2014-05-27T18:36:08Z

To discuss

2014-05-27T17:15:02Z

To discuss

2014-05-27T17:14:32Z

Created page with '== To discuss == * Review Roadmap and issue tracker'

New page

== To discuss ==
* Review Roadmap and issue tracker

@@ Line 4: / Line 4: @@
 == Conclusion ==
-* Extensions: Will add a convenience launcher to allow easy use of the ExtensionWizard
+* Extensions: We will add a convenience launcher to allow easy use of the ExtensionWizard (Jc & Matt W.)
 * SubjectHierarchy: Csaba will rebase the commits and then integrate into Slicer core
-* Matt will look at jsonld and finalize integration of the parameter serializer
+* Matt M. will look at jsonld and finalize integration of the parameter serializer
 * Update of Teem version
 ** Currently using teem-1.1.10 (Dec 10, 2008) built from source. See [https://github.com/Slicer/Slicer/blob/3c4dc4490488e545c354472521f634a786f121c6/SuperBuild/External_teem.cmake#L47 here]

@@ Line 13: / Line 13: @@
 ** Question to address:
 *** In case we depend on teem master/trunk/release-branch ... is there a github repo that could be forked and would make contribution of fixes easier ?
-*** vtkTeem: In Slicer we are maintaining a layer allowing to easily integrate with teem. See [https://github.com/Slicer/Slicer/tree/master/Libs/vtkTeem here], should we change anything ?
+*** vtkTeem: In Slicer we are maintaining a layer allowing to easily expose teem by integrating VTK and teem. See [https://github.com/Slicer/Slicer/tree/master/Libs/vtkTeem here], should we change anything ?
 *** vtkTeem: Should this later be maintained in a dedicated repository ? With it own dashboard and testing infrastructure ?

← Older revision		Revision as of 18:59, 27 May 2014
Line 7:		Line 7:
	* SubjectHierarchy: Csaba will rebase the commits and then integrate into Slicer core		* SubjectHierarchy: Csaba will rebase the commits and then integrate into Slicer core
	* Matt will look at jsonld and finalize integration of the parameter serializer		* Matt will look at jsonld and finalize integration of the parameter serializer
		+	* Update of Teem version
		+	** Currently using teem-1.1.10 (Dec 10, 2008) built from source. See [https://github.com/Slicer/Slicer/blob/3c4dc4490488e545c354472521f634a786f121c6/SuperBuild/External_teem.cmake#L47 here]
		+	** The idea would be to use teem-1.1.11 when available ? or teem trunk ?
		+	** Raul will check with Gordon what is the status.
		+	** Question to address:
		+	*** In case we depend on teem master/trunk/release-branch ... is there a github repo that could be forked and would make contribution of fixes easier ?
		+	*** vtkTeem: In Slicer we are maintaining a layer allowing to easily integrate with teem. See [https://github.com/Slicer/Slicer/tree/master/Libs/vtkTeem here], should we change anything ?
		+	*** vtkTeem: Should this later be maintained in a dedicated repository ? With it own dashboard and testing infrastructure ?

← Older revision		Revision as of 18:37, 27 May 2014
Line 6:		Line 6:
	* Extensions: Will add a convenience launcher to allow easy use of the ExtensionWizard		* Extensions: Will add a convenience launcher to allow easy use of the ExtensionWizard
	* SubjectHierarchy: Csaba will rebase the commits and then integrate into Slicer core		* SubjectHierarchy: Csaba will rebase the commits and then integrate into Slicer core
		+	* Matt will look at jsonld and finalize integration of the parameter serializer

← Older revision		Revision as of 18:36, 27 May 2014
Line 2:		Line 2:
	* Switch VTK_VERSION_MAJOR to 6		* Switch VTK_VERSION_MAJOR to 6
	* Review Roadmap and issue tracker		* Review Roadmap and issue tracker
		+
		+	== Conclusion ==
		+	* Extensions: Will add a convenience launcher to allow easy use of the ExtensionWizard
		+	* SubjectHierarchy: Csaba will rebase the commits and then integrate into Slicer core

@@ Line 1: / Line 1: @@
 == To discuss ==
 * Review Roadmap and issue tracker
 == Conclusion ==

← Older revision		Revision as of 17:15, 27 May 2014
Line 1:		Line 1:
	== To discuss ==		== To discuss ==
		+	* Switch VTK_VERSION_MAJOR to 6
	* Review Roadmap and issue tracker		* Review Roadmap and issue tracker