comparison Sphinx/source/contributing.rst @ 771:b1147fe83eda

contributing
author Sebastien Jodogne <s.jodogne@gmail.com>
date Fri, 10 Sep 2021 15:53:28 +0200
parents 37512473ffe9
children c55ab0604d10
comparison
equal deleted inserted replaced
770:9978fb958ee2 771:b1147fe83eda
96 `GNUmed <https://en.wikipedia.org/wiki/GNUmed>`__... 96 `GNUmed <https://en.wikipedia.org/wiki/GNUmed>`__...
97 97
98 98
99 * **Coding tasks**: 99 * **Coding tasks**:
100 100
101 - Have a look at the TODO file containing our `official roadmap
102 <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__.
101 - The Orthanc project will happily accept patches in the core of 103 - The Orthanc project will happily accept patches in the core of
102 Orthanc and in its associated official plugins. Please read the 104 Orthanc and in its associated official plugins. Please read the
103 :ref:`dedicated FAQ entry <cla>`. 105 :ref:`dedicated FAQ entry <cla>`.
104 - Interface Orthanc with other software (e.g. 3D Slicer, 106 - Interface Orthanc with other software (e.g. 3D Slicer,
105 Matlab/Octave, Python, Horos, dicompyler...). Check the `already 107 Matlab/Octave, Python, Horos, dicompyler...). Check the `already
150 be done as a :ref:`Python plugin <python-plugin>` by wrapping 152 be done as a :ref:`Python plugin <python-plugin>` by wrapping
151 the C-FIND and C-MOVE callbacks in the Python API. 153 the C-FIND and C-MOVE callbacks in the Python API.
152 + Get involved in the call for ideas by Salim Kanoun about a 154 + Get involved in the call for ideas by Salim Kanoun about a
153 `DICOM router built on the top of Orthanc 155 `DICOM router built on the top of Orthanc
154 <https://groups.google.com/g/orthanc-users/c/tx7E1RQuKIY/m/_GsrRZljBgAJ>`__. 156 <https://groups.google.com/g/orthanc-users/c/tx7E1RQuKIY/m/_GsrRZljBgAJ>`__.
155 + Have a look at the TODO file containing our `official roadmap
156 <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__.
157 157
158 - Always remember that he **recommended way of contributing to the 158 - Always remember that he **recommended way of contributing to the
159 source code of Orthanc is by creating C/C++/Python plugins, or by 159 source code of Orthanc is by creating C/C++/Python plugins, or by
160 creating external software that use the REST API**. If the current 160 creating external software that use the REST API**. If the current
161 plugin SDK is insufficient for you to develop some feature as a 161 plugin SDK is insufficient for you to develop some feature as a