Mercurial > hg > orthanc-book

comparison Sphinx/source/developers/repositories.rst @ 968:4ce37a89b212

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Submitting contributions
author Sebastien Jodogne <s.jodogne@gmail.com>
date Wed, 16 Aug 2023 21:23:10 +0200
parents 41bae819d80b
children 46e2941b57dd
comparison
equal deleted inserted replaced
967:2df3597eacc8 968:4ce37a89b212
198 your contributions, but be aware of the fact that we are quite 198 your contributions, but be aware of the fact that we are quite
199 strict, and that the review process might take time. This is why the 199 strict, and that the review process might take time. This is why the
200 recommended way of contributing to Orthanc is always by 200 recommended way of contributing to Orthanc is always by
201 :ref:`creating contributed plugins <creating-plugins>`. 201 :ref:`creating contributed plugins <creating-plugins>`.
202 202
203 * Importantly, before any contribution can be accepted into the 203 * Importantly, before any contribution with significant intellectual
204 Orthanc repositories, its author must sign a :ref:`CLA <cla>`. This 204 property (i.e. if the contribution go beyond a simple patch) can be
205 allows the University Hospital of Liège, the Osimis company and 205 accepted into the Orthanc repositories, its author must sign a
206 UCLouvain university to act as the official guardians of the whole 206 :ref:`CLA <cla>`. This allows the University Hospital of Liège, the
207 Orthanc ecosystem. Another advantage of creating plugins is that 207 Osimis company, and UCLouvain university to act as the official
208 signing a CLA is not needed. Make sure to carefully read our 208 guardians of the whole Orthanc ecosystem. Note that another
209 :ref:`FAQ about the licensing of submitted code <submitting_code>`. 209 advantage of creating plugins over submitting core to the core
210 project is that signing a CLA is never needed. Make sure to
211 carefully read our :ref:`FAQ about the licensing of submitted code
212 <submitting_code>`.
210 213
211 214
212 .. _hg-patch: 215 .. _hg-patch:
213 216
214 Simple patch (import/export) 217 Simple patch (import/export)
295 $ hg clone https://hg.orthanc-server.com/orthanc/ 298 $ hg clone https://hg.orthanc-server.com/orthanc/
296 $ cd /tmp/orthanc 299 $ cd /tmp/orthanc
297 $ hg unbundle /tmp/contribution.bundle 300 $ hg unbundle /tmp/contribution.bundle
298 $ hg up -c default 301 $ hg up -c default
299 $ hg merge my-user/my-fix 302 $ hg merge my-user/my-fix
303
304
305 .. _hg-submitting:
306
307 Submitting contributions
308 ........................
309
310 Contributed patches and bundles must be sent by e-mail, either to
311 `Sébastien Jodogne <mailto:sebastien.jodogne@uclouvain.be>`__
312 (UCLouvain) or to `Alain Mazy <mailto:am@orthanc.team>`__ (Orthanc
313 Team).
300 314
301 315
302 Issue tracker 316 Issue tracker
303 ------------- 317 -------------
304 318