Difference between revisions of "Developer Meetings/20170328"
From Slicer Wiki
| Line 13: | Line 13: | ||
** https://spdx.org/spdx-license-list/request-new-license | ** https://spdx.org/spdx-license-list/request-new-license | ||
** https://spdx.org/licenses/ | ** 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 [https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license 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 [https://github.com/search?utf8=%E2%9C%93&q=3D+Slicer+filename%3ALICENSE&type=Code 110 reported]). | + | ** 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 [https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license 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 [https://github.com/search?utf8=%E2%9C%93&q=3D+Slicer+filename%3ALICENSE&type=Code 110 reported]). | ||
Revision as of 05:50, 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
- Automatic generation of API documentation. See https://github.com/Slicer/Slicer/pull/690
- 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).
