Developer Meetings/20170314 - Revision history

JChris.FillionR: /* Conclusion */

2017-03-21T07:05:16Z

Conclusion

2017-03-14T15:06:30Z

Conclusion

2017-03-14T14:37:47Z

Conclusion

2017-03-14T14:28:26Z

2017-03-14T14:27:06Z

2017-03-14T14:26:16Z

2017-03-14T14:18:30Z

2017-03-14T14:07:20Z

To Discuss

2017-03-14T14:04:58Z

To Discuss

2017-03-14T13:49:02Z

@@ Line 44: / Line 44: @@
 ** very limiting in formatting option
 ** possible to copy image directly
 * RST
 ** flexible
 ** readthedocs

@@ Line 37: / Line 37: @@
 * Generate documentation from source code
 * Gitbook:
 ** different repo: advantage: can give access to more people
-** very limiting
+** very limiting in formatting option

← Older revision		Revision as of 14:37, 14 March 2017
Line 40:		Line 40:
	* Gitbook:		* Gitbook:
	** different repo: advantage: can give access to more people		** different repo: advantage: can give access to more people
		+	** very limiting

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

	* Generate documentation from source code		* Generate documentation from source code
		+
		+	* Gitbook:
		+	** different repo: advantage: can give access to more people

← Older revision		Revision as of 14:27, 14 March 2017
Line 35:		Line 35:
	* Re-generate the listing to get baseline for manual maintenance		* Re-generate the listing to get baseline for manual maintenance
	* Module name or extension have spaces		* Module name or extension have spaces
		+
		+	* Generate documentation from source code

← Older revision		Revision as of 14:26, 14 March 2017
Line 31:		Line 31:
	* Automatic generation of subpage		* Automatic generation of subpage
	* List of broken extension: Do not belong to the wiki: Write a test listing broken extensions, could be added to the developer tools		* List of broken extension: Do not belong to the wiki: Write a test listing broken extensions, could be added to the developer tools
		+	* One button, install all extensions, generate report
		+
		+	* Re-generate the listing to get baseline for manual maintenance
		+	* Module name or extension have spaces

← Older revision		Revision as of 14:18, 14 March 2017
Line 22:		Line 22:

	Discuss the [http://massmail.spl.harvard.edu/public-archives/slicer-devel/2017/041633.html hosting of doxygen files].		Discuss the [http://massmail.spl.harvard.edu/public-archives/slicer-devel/2017/041633.html hosting of doxygen files].
		+
		+
		+
		+	= Conclusion =
		+
		+	* Difficult to find information as it appears multiple time on the same page
		+	* Middle column should be manually organized
		+	* Automatic generation of subpage
		+	* List of broken extension: Do not belong to the wiki: Write a test listing broken extensions, could be added to the developer tools

← Older revision		Revision as of 14:07, 14 March 2017
Line 21:		Line 21:
	* Step 2: Creation of consolidated listing of modules and extensions by downloading the metadata generated in the previous step and downloading the associated list of extension description files.		* Step 2: Creation of consolidated listing of modules and extensions by downloading the metadata generated in the previous step and downloading the associated list of extension description files.

−	Discuss the hosting of doxygen files.	+	Discuss the [http://massmail.spl.harvard.edu/public-archives/slicer-devel/2017/041633.html hosting of doxygen files].

← Older revision		Revision as of 14:04, 14 March 2017
Line 20:		Line 20:

	* Step 2: Creation of consolidated listing of modules and extensions by downloading the metadata generated in the previous step and downloading the associated list of extension description files.		* Step 2: Creation of consolidated listing of modules and extensions by downloading the metadata generated in the previous step and downloading the associated list of extension description files.
		+
		+	Discuss the hosting of doxygen files.

← Older revision		Revision as of 13:49, 14 March 2017
Line 8:		Line 8:

	= To Discuss =		= To Discuss =
−	* Maintenance of module and extension documentation. See http://slicer-devel.65872.n3.nabble.com/Module-list-in-documentation-not-updated-tt4038225.html	+
		+	Maintenance of module and extension documentation. See http://slicer-devel.65872.n3.nabble.com/Module-list-in-documentation-not-updated-tt4038225.html
		+
		+	Currently, the script [https://github.com/Slicer/slicer-wiki-scripts/blob/master/slicer_wiki_extension_module_listing.py slicer_wiki_extension_module_listing.py] is used to automatically create the listing of Slicer modules and extensions available on the Slicer wiki user documentation.
		+
		+	The creation of the listing is a two-step process:
		+
		+	* Step 1: On each factory (Linux, MacOSX, Windows):
		+	** the list of modules built in every extension is generated
		+	** Slicer is started to find out which modules can be loaded successfully into Slicer, the list of modules (as associated metadata) is then published into a github repository: https://github.com/Slicer/slicer-packages-metadata
		+
		+	* Step 2: Creation of consolidated listing of modules and extensions by downloading the metadata generated in the previous step and downloading the associated list of extension description files.