Latest revision as of 15:20, 4 April 2017

To Discuss

Discourse
- In the short term, unlikely we will be able to setup that up at Kitware
- Steve will check if we can host discourse side by side with the Slicer wiki on Digital Ocean instances

Jupyter notebook integration
- Since python env in Slicer is not standard, look like there is less interest into having IPython integration ?
- Having loose coupling and pushing/pulling data from/to is a way forward

@@ Line 9: / Line 9: @@
 = To Discuss =
-* Jon, Rick and Prashant from Intel will be attending the meeting to talk with Slicer community about our unique computational challenges and how they could help.
+* Review PRs
+* discuss status of upcoming migrations
+** Qt5
+** Python 3
+** VTK OpenGL2 backend
+* Update on discourse and user/dev documentation
+* Update on Jupyter notebook integration
+= Conclusion =
+* Qt5
+** packaging
+** create a slice web widget working with QWebView
+* Python3
+* VTK
+** Should move forward in the coming weeks
+* Discourse
+** In the short term, unlikely we will be able to setup that up at Kitware
+** Steve will check if we can host discourse side by side with the Slicer wiki on Digital Ocean instances
+* user/dev doc
+** gitbook CEO contacted. Mentioned we would need to support 1000 contributors. Suggested him to join our hangout.
+** mailing list users (as of April 4th 2017): user: 1090, devel: 581
+** Missing redirect https://www.slicer.org/doc/html/ to apidocs.slicer.org/master
+** Would need dump of wiki: https://github.com/peterjc/mediawiki_to_git_md
+** Moving FAQ to devel doc is ok. It will be quite easy to update and create PR from GitHub
+* Jupyter notebook integration
+** Since python env in Slicer is not standard, look like there is less interest into having IPython integration ?
+** Having loose coupling and pushing/pulling data from/to is a way forward