Developer Meetings/20170328 - Revision history

JChris.FillionR: /* Conclusion */

2017-03-28T14:54:24Z

Conclusion

2017-03-28T14:49:14Z

Conclusion

2017-03-28T14:46:35Z

Conclusion

2017-03-28T14:43:36Z

Conclusion

2017-03-28T14:15:15Z

To Discuss

2017-03-28T14:14:29Z

2017-03-28T14:01:55Z

To Discuss

2017-03-28T08:18:51Z

To Discuss

2017-03-28T08:15:41Z

To Discuss

2017-03-28T05:59:03Z

To Discuss

@@ Line 67: / Line 67: @@
 ** Current license reference Brigham, should probably rephrased ?
 ** Keep Slicer License for the core, and use Apache 2.0 for extensions ...
 = Appendix =

@@ Line 64: / Line 64: @@
 ** Matt: Limitation of Apache 2.0, complicated and long. But the industry is standardizing on it.
 ** Lawyer land is complex ...
 = Appendix =

@@ Line 63: / Line 63: @@
 ** Steve: Slicer License has been carefully  crafted.
 ** Matt: Limitation of Apache 2.0, complicated and long. But the industry is standardizing on it.
 = Appendix =

← Older revision		Revision as of 14:43, 28 March 2017
Line 54:		Line 54:
	*** Steve: May it could be made available for open source project.		*** Steve: May it could be made available for open source project.

		+	* Remove Extensions/Testing
		+
		+	* private mailing list makes sense
		+
		+	* SPDX license:
		+	** Steve: Worth trying to request for its addition
		+	** Andras: What about avoiding to fragment the license ecosystem .. and standardizing ?
		+	** Steve: Slicer License has been carefully crafted.
		+	** Matt: Limitation of Apache 2.0, complicated and long. But the industry is standardizing on it.

	= Appendix =		= Appendix =

← Older revision		Revision as of 14:15, 28 March 2017
Line 29:		Line 29:

	* SSL error on windows: http://slicer-devel.65872.n3.nabble.com/SSL-error-in-latest-nightly-td4038361.html		* SSL error on windows: http://slicer-devel.65872.n3.nabble.com/SSL-error-in-latest-nightly-td4038361.html
		+
		+	* Slicer related bugs in ITK addressed for 4.11.1 release:
		+	** [https://issues.itk.org/jira/browse/ITK-3519 ITK-3519] When ThinPlateSplineTransform is read from file, ->ComputeWMatrix() is required to avoid a crash.
		+	** [https://issues.itk.org/jira/browse/ITK-3523 ITK-3523] incorrect dicom from encapsulated metadata
		+	** [https://issues.itk.org/jira/browse/ITK-3529 ITK-3529] Failed to build ITK Remote module using Release 4.11.0
		+	** [https://issues.itk.org/jira/browse/ITK-3498 ITK-3498] Support modules in find_package OPTIONAL_COMPONENTS (related to getting ITK-3529 in the release branch)

	= Conclusion =		= Conclusion =

← Older revision		Revision as of 14:14, 28 March 2017
Line 30:		Line 30:
	* SSL error on windows: http://slicer-devel.65872.n3.nabble.com/SSL-error-in-latest-nightly-td4038361.html		* SSL error on windows: http://slicer-devel.65872.n3.nabble.com/SSL-error-in-latest-nightly-td4038361.html

		+	= Conclusion =
		+
		+	* Talk with Jon from Intel:
		+	** ITK, Slicer, VTK .. popular tool.
		+	** Explore how Intel could have the biggest impact.
		+	** Explore area where we are headed to.
		+	** Bring Intel to contribute something meaningful.
		+	** How to move forward ? Collect feedback. Come with initial list of idea. Priority list.
		+	** From Andras: Identify a specific project and see how we can move forward.
		+	** From Matt (last week): Improve ITK threading geared toward registration.
		+	** From Steve:
		+	*** A lot of tool in house to look at executable and identify issue on a given arch. May something could be done in that directory.
		+	*** Jon: Easy to generate a lot of results from tool. But need to identify a use case
		+	*** Steve/Andrey: May be improve perf of BRAINSFit
		+	*** Andras: Slicer uses one processor most of the time .. learn about how to maximize use of processor.
		+	*** Jon: Profiling would allow to identify where we can optimize. Would it make sense to use Mkl ? First assumption is that we don t need MKL.
		+	*** Steve: May it could be made available for open source project.
		+
		+
		+	= Appendix =

	=== Exchange with Gitbook CEO ===		=== Exchange with Gitbook CEO ===

@@ Line 19: / Line 19: @@
 * Slicer module/extension template duplication: Does it still make sense to have the module and extension templates in [https://github.com/Slicer/Slicer/tree/master/Utilities/Templates Utilities/Templates] along with the complete example of extensions in [https://github.com/Slicer/Slicer/tree/master/Extensions/Testing Extensions/Testing] ?
 * Gitbook CEO replied to our inquiry about increasing the limit and asked "How many people to you foresee contributing to your docs ?"
 * Request for adding Slicer license as an official SPDX (Software Package Data Exchange) License:
@@ Line 27: / Line 27: @@
 *** (1) use the qualifier "'License :: OSI Approved :: Slicer License" in python packages (and similar references in other ecosystems),
 *** and (2) also [https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license potentially request] to have the Slicer listed as an option on Github (that said, we need at least a 1000 repos using the license on GitHub ... and we currently have [https://github.com/search?utf8=%E2%9C%93&q=3D+Slicer+filename%3ALICENSE&type=Code 110 reported]).

@@ Line 9: / Line 9: @@
 = To Discuss =
-* Creation of private list (slicer-admin@googlegroups.com) that will be associated to web resources managed by the core developers. These resources will for example include the [https://github.com/slicerbot slicerbot] Github user.
+* Creation of private list (slicer-admin@googlegroups.com) that will be associated to web resources managed by the core developers. These resources will for example include:
 * Automatic generation of API documentation. See https://github.com/Slicer/Slicer/pull/690

← Older revision		Revision as of 08:15, 28 March 2017
Line 8:		Line 8:

	= To Discuss =		= To Discuss =
		+
		+	* Creation of private list (slicer-admin@googlegroups.com) that will be associated to web resources managed by the core developers. These resources will for example include the [https://github.com/slicerbot slicerbot] Github user.

	* Automatic generation of API documentation. See https://github.com/Slicer/Slicer/pull/690		* Automatic generation of API documentation. See https://github.com/Slicer/Slicer/pull/690

← Older revision		Revision as of 05:59, 28 March 2017
Line 10:		Line 10:

	* Automatic generation of API documentation. See https://github.com/Slicer/Slicer/pull/690		* Automatic generation of API documentation. See https://github.com/Slicer/Slicer/pull/690
		+
		+	* Slicer module/extension template duplication: Does it still make sense to have the module and extension templates in [https://github.com/Slicer/Slicer/tree/master/Utilities/Templates Utilities/Templates] along with the complete example of extensions in [https://github.com/Slicer/Slicer/tree/master/Extensions/Testing Extensions/Testing] ?

	* Gitbook CEO replied to our inquiry about increasing the limit and asked "How many people to you foresee contributing to your docs ?"		* Gitbook CEO replied to our inquiry about increasing the limit and asked "How many people to you foresee contributing to your docs ?"