Difference between revisions of "Developer Meetings/20170328"
From Slicer Wiki
| 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 | ||
Revision as of 08:15, 28 March 2017
Home < Developer Meetings < 20170328
 |
If you would like to list your topic here, create a wiki account and edit this page You can join the hangout using http://bit.ly/slicer-hangout-kw. |
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 slicerbot Github user.
- 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 Utilities/Templates along with the complete example of extensions in 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:
- https://spdx.org/spdx-license-list/request-new-license
- https://spdx.org/licenses/
- Rational: Then, we could
- (1) use the qualifier "'License :: OSI Approved :: Slicer License" in python packages (and similar references in other ecosystems),
- and (2) also 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 110 reported).
