Difference between revisions of "Developer Meetings/20140429"
From Slicer Wiki
m |
|||
| Line 6: | Line 6: | ||
** http://slicer-devel.65872.n3.nabble.com/How-to-solve-wget-error-certificate-common-name-c-ssl-fastly-net-doesn-t-match-requested-host-name-p-tc4031491.html | ** http://slicer-devel.65872.n3.nabble.com/How-to-solve-wget-error-certificate-common-name-c-ssl-fastly-net-doesn-t-match-requested-host-name-p-tc4031491.html | ||
* Move [https://github.com/TubeTK/TubeTK-ParameterSerializer ParameterSerializer] repository to the [https://github.com/Slicer Slicer GitHub Organization]. | * Move [https://github.com/TubeTK/TubeTK-ParameterSerializer ParameterSerializer] repository to the [https://github.com/Slicer Slicer GitHub Organization]. | ||
| + | |||
| + | |||
| + | == Conclusion == | ||
| + | |||
| + | * Support of fiducial/markups in lightbox: This is on Nicole todo list. | ||
| + | * Wget: From Csaba: after installing openssl-dev, compilation of wget worked | ||
| + | * A repository named "ParameterSerializer" will be created. | ||
| + | * VTK6: Will integrate changes tomorrow. By default VTK5 will still be enabled. In the coming days, we will (1) send an email addressed to extension maintainer and (2) setup a dashboard to have Slicer and extensions built against VTK6. That should allow extension maintainers to address issues. | ||
Revision as of 18:40, 29 April 2014
Home < Developer Meetings < 20140429To discuss
- 4.4 Roadmap
- wget certificate error
- SimpleITK utilizes ez_setup.py to get setuptools
- http://slicer-devel.65872.n3.nabble.com/How-to-solve-wget-error-certificate-common-name-c-ssl-fastly-net-doesn-t-match-requested-host-name-p-tc4031491.html
- Move ParameterSerializer repository to the Slicer GitHub Organization.
Conclusion
- Support of fiducial/markups in lightbox: This is on Nicole todo list.
- Wget: From Csaba: after installing openssl-dev, compilation of wget worked
- A repository named "ParameterSerializer" will be created.
- VTK6: Will integrate changes tomorrow. By default VTK5 will still be enabled. In the coming days, we will (1) send an email addressed to extension maintainer and (2) setup a dashboard to have Slicer and extensions built against VTK6. That should allow extension maintainers to address issues.
