Difference between revisions of "Developer Meetings/20150901"
From Slicer Wiki
(→Update) |
m (Text replacement - "slicerWiki/index.php" to "wiki") |
||
| (5 intermediate revisions by one other user not shown) | |||
| Line 9: | Line 9: | ||
* Steve | * Steve | ||
** working on Q3DCExtension with Bea and Francois for SlicerCMF | ** working on Q3DCExtension with Bea and Francois for SlicerCMF | ||
| − | ** working on CommonGL for new volume renderer and editor effects | + | ** working on [https://github.com/pieper/CommonGL CommonGL] for new volume renderer and editor effects |
| + | *** One of the goal: Multivolume compositing | ||
= To Discuss= | = To Discuss= | ||
| Line 15: | Line 16: | ||
* Update description of extension to better explain the differences between the extension categories: | * Update description of extension to better explain the differences between the extension categories: | ||
| − | ** http://wiki.slicer.org/ | + | ** http://wiki.slicer.org/wiki/Documentation/Nightly/Developers/FAQ#What_is_an_extension_.3F |
** https://github.com/Slicer/ExtensionsIndex/pull/1065#issuecomment-135397565 | ** https://github.com/Slicer/ExtensionsIndex/pull/1065#issuecomment-135397565 | ||
= Conclusion = | = Conclusion = | ||
| + | |||
| + | == Extension license == | ||
| + | * Should we "allow" extension bundling GPL source code to be built on the factory and distributed with Slicer ? | ||
| + | ** Potentially yes, we could distribute code distributed under non academic license (aka reciprocal public license). That said, we would have to update the infrastructure to clearly notify the user. | ||
| + | |||
| + | * It is not clear what is the default license associated with extension. | ||
| + | ** Todo: Update template to explicitly default to the Slicer license. The Slicer license would be copied into each template folder. Description would be updated with the following text "Unless specified differently, the extension code is distributed under 3D Slicer BSD style license" | ||
| + | ** Ideally, we could also extend the description file spec to include a "license" identifier. | ||
| + | |||
| + | * What about closed source ? | ||
| + | ** These will not be distributed by the Slicer extension manager. A solution would be setup a dedicated extension server. | ||
| + | |||
| + | == DMCTK update == | ||
| + | |||
| + | * Segmentation object support have been integrated into DCMTK master. | ||
| + | |||
| + | * Next snapshot of DCMTK will most likely be done in September. Snapshot is somewhat arbitrary, we will choose a version in the coming days. | ||
| + | |||
| + | * Regarding the private dic, Andriy will double check the embedded dict feature works as expected and create a Slicer pull request with a chosen DCMTK version. | ||
Latest revision as of 17:04, 21 November 2019
Home < Developer Meetings < 20150901To join the hangout, open this page and click on "Join hangout"
Update
- Jc:
- Max made some good progress regarding the crash on exit issue experienced on Linux when building against Python >= 2.7.4.
- The problem wasn't specific to miniconda. Few fixes have been pushed to commontk/PythonQt
- Version of python built in Slicer will soon be updated from Python 2.7.3 to 2.7.10.
- On my list: (1) finalize work related to slicer/conda experiment, (2) fix remaining packaging issues, (3) Integration of PRs Use SimpleITK's SuperBuild for additional dependencies., Move to itkmghio
- Max made some good progress regarding the crash on exit issue experienced on Linux when building against Python >= 2.7.4.
- Steve
- working on Q3DCExtension with Bea and Francois for SlicerCMF
- working on CommonGL for new volume renderer and editor effects
- One of the goal: Multivolume compositing
To Discuss
- Confirm/refine Slicer 4.5 release plan discussed in previous meeting.
- Update description of extension to better explain the differences between the extension categories:
Conclusion
Extension license
- Should we "allow" extension bundling GPL source code to be built on the factory and distributed with Slicer ?
- Potentially yes, we could distribute code distributed under non academic license (aka reciprocal public license). That said, we would have to update the infrastructure to clearly notify the user.
- It is not clear what is the default license associated with extension.
- Todo: Update template to explicitly default to the Slicer license. The Slicer license would be copied into each template folder. Description would be updated with the following text "Unless specified differently, the extension code is distributed under 3D Slicer BSD style license"
- Ideally, we could also extend the description file spec to include a "license" identifier.
- What about closed source ?
- These will not be distributed by the Slicer extension manager. A solution would be setup a dedicated extension server.
DMCTK update
- Segmentation object support have been integrated into DCMTK master.
- Next snapshot of DCMTK will most likely be done in September. Snapshot is somewhat arbitrary, we will choose a version in the coming days.
- Regarding the private dic, Andriy will double check the embedded dict feature works as expected and create a Slicer pull request with a chosen DCMTK version.
