Mercurial > hg > orthanc-book

comparison Sphinx/source/faq/licensing.rst @ 203:b79ef7808f16

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
note about plugins
author Sebastien Jodogne <s.jodogne@gmail.com>
date Tue, 12 Feb 2019 16:20:52 +0100
parents 1e9cb6e1afb0
children 76c76af97a2a
comparison
equal deleted inserted replaced
202:1e9cb6e1afb0 203:b79ef7808f16
73 +-----------------------------------------------------+--------------------------------------------------------------------------------------------+ 73 +-----------------------------------------------------+--------------------------------------------------------------------------------------------+
74 | | Mode of distribution of the third-party system, or of the third-party plugin/script | 74 | | Mode of distribution of the third-party system, or of the third-party plugin/script |
75 +-----------------------------------------------------+---------------+-------+--------+--------------+------------------------+-------------------+ 75 +-----------------------------------------------------+---------------+-------+--------+--------------+------------------------+-------------------+
76 | Usage of the Orthanc ecosystem | Permissive | GPLv3 | AGPLv3 | Internal use | Proprietary software | Proprietary cloud | 76 | Usage of the Orthanc ecosystem | Permissive | GPLv3 | AGPLv3 | Internal use | Proprietary software | Proprietary cloud |
77 | | (MIT, BSD, | | | | distributed to clients | platform | 77 | | (MIT, BSD, | | | | distributed to clients | platform |
78 | | Apache2...) | | | | | | 78 | | Apache...) | | | | | |
79 +=====================================================+===============+=======+========+==============+========================+===================+ 79 +=====================================================+===============+=======+========+==============+========================+===================+
80 | Using Orthanc as such, even if some AGPL-licensed | N/A | N/A | N/A | Yes | Yes | Yes | 80 | Using Orthanc as such, even if some AGPL-licensed | N/A | N/A | N/A | Yes | Yes | Yes |
81 | plugin is installed | | | | | | | 81 | plugin is installed | | | | | | |
82 +-----------------------------------------------------+---------------+-------+--------+--------------+------------------------+-------------------+ 82 +-----------------------------------------------------+---------------+-------+--------+--------------+------------------------+-------------------+
83 | Calling Orthanc from a third-party application | Yes | Yes | Yes | Yes | Yes | Yes | 83 | Calling Orthanc from a third-party application | Yes | Yes | Yes | Yes | Yes | Yes |
122 122
123 * If you reuse code from Orthanc or one of its associated plugins, you 123 * If you reuse code from Orthanc or one of its associated plugins, you
124 must mention the copyright of the Orthanc project. 124 must mention the copyright of the Orthanc project.
125 125
126 * An Orthanc plugin cannot be licensed under a permissive license 126 * An Orthanc plugin cannot be licensed under a permissive license
127 (MIT, BSD, Apache2...) because it must interface with the Orthanc 127 (MIT, BSD, Apache...) because it cannot run independently of the
128 SDK that is licensed under GPLv3. Check out the `license 128 Orthanc SDK, which implies that the plugin and the Orthanc core form
129 compatibility matrix on Wikipedia 129 a single combined program, which in turn means that the plugin
130 should be licensed under GPLv3 by `copyleft
131 <https://en.wikipedia.org/wiki/Copyleft>`__ contamination. Check out
132 the `license compatibility matrix on Wikipedia
130 <https://en.wikipedia.org/wiki/License_compatibility#Compatibility_of_FOSS_licenses>`__. 133 <https://en.wikipedia.org/wiki/License_compatibility#Compatibility_of_FOSS_licenses>`__.
134 Here is the corresponding entry about this topic in the `GPL FAQ
135 <https://www.gnu.org/licenses/gpl-faq.en.html#GPLPlugins>`__: *"If
136 the main program dynamically links plug-ins, and they make function
137 calls to each other and share data structures, we believe they form
138 a single combined program, which must be treated as an extension of
139 both the main program and the plug-ins. [...] If the main program
140 and the plugins are a single combined program then this means you
141 must license the plug-in under the GPL or a GPL-compatible free
142 software license and distribute it with source code in a
143 GPL-compliant way."*
131 144
132 * If you deal with medical applications in Europe, note that Osimis 145 * If you deal with medical applications in Europe, note that Osimis
133 sells **CE-approved** versions of a Web viewer plugin. 146 sells **CE-approved** versions of a Web viewer plugin.
134 147
135 * You are kindly invited to cite the `reference paper about Orthanc 148 * You are kindly invited to cite the `reference paper about Orthanc
162 Orthanc ecosystem. External contributors can distribute such 175 Orthanc ecosystem. External contributors can distribute such
163 contributed code on whatever platform they prefer, in a way that is 176 contributed code on whatever platform they prefer, in a way that is
164 fully uncoupled from the Orthanc project, and keep the intellectual 177 fully uncoupled from the Orthanc project, and keep the intellectual
165 property of their developments. Such contributors are however kindly 178 property of their developments. Such contributors are however kindly
166 invited to index their contributions in the `dedicated repository on 179 invited to index their contributions in the `dedicated repository on
167 GitHub <https://github.com/jodogne/OrthancContributed>`__. 180 GitHub <https://github.com/jodogne/OrthancContributed>`__, and
181 contributed plugins should also be indexed in the :ref:`Orthanc Book
182 <plugins-contributed>`.
168 183
169 * **Internal code** refers to source code that only makes sense if 184 * **Internal code** refers to source code that only makes sense if
170 embedded within the Orthanc core or within one of the official 185 embedded within the Orthanc core or within one of the official
171 plugins. This includes new features and bugfixes. The way to 186 plugins. This includes new features and bugfixes. The way to
172 contribute to the internal code of the Orthanc ecosystem is 187 contribute to the internal code of the Orthanc ecosystem is