comparison Sphinx/source/faq/proprietary.rst @ 0:901e8961f46e

initial commit
author Sebastien Jodogne <s.jodogne@gmail.com>
date Fri, 22 Apr 2016 12:57:38 +0200
parents
children 011b01ccf52d
comparison
equal deleted inserted replaced
-1:000000000000 0:901e8961f46e
1 .. _proprietary:
2
3 Software X from vendor Y is not compatible with Orthanc
4 =======================================================
5
6 First of all, make sure to read at least the following sections from
7 the :ref:`faq`:
8
9 * :ref:`troubleshooting`
10 * :ref:`dicom`
11
12 Orthanc is `free and open-source software (FOSS)
13 <https://en.wikipedia.org/wiki/Free_and_open-source_software>`_. FOSS
14 protects the digital freedoms of its users, and is freely available to
15 each and every user, for any use. As a backbone application for
16 medical imaging, the Orthanc project continuously tries and ensures
17 best possible compatibility with other FOSS software. To put it in
18 other words, we **provide free support for interfacing Orthanc with
19 other free and open-source software**. Feel free to discuss
20 interoperability problems of Orthanc with other FOSS tools on `our
21 discussion group
22 <https://groups.google.com/forum/#!forum/orthanc-users>`_, or to
23 introduce `bug reports
24 <https://bitbucket.org/sjodogne/orthanc/issues?status=new&status=open>`_
25 detailing how to reproduce your problem.
26
27 Independently of FOSS, there exist many proprietary systems for
28 medical imaging. Note that proprietary systems might either be paying
29 or come gratis (also known as freeware). In either case, they restrict
30 the freedoms of their users and, as a consequence, the Orthanc project
31 does not have access to a valid license for each software X from any
32 vendor Y. This implies that we **do not provide free support for
33 proprietary software (including freeware)**.
34
35 If you encounter difficulties while interfacing Orthanc with some
36 proprietary software, **contact the commercial support of your
37 supplier**. As Orthanc is free and open-source, the support team of
38 your supplier can download Orthanc, and can help you solve your
39 problem. If some fix is needed in our source code, the Orthanc project
40 will happily integrate it within in the Orthanc mainline, provided the
41 **patch is explicitly put in the public domain by your vendor**. We
42 remind the vendors that, if they distribute a patched version of
43 Orthanc to some of their clients as the result of a commercial
44 support, the `GPL license
45 <https://en.wikipedia.org/wiki/GNU_General_Public_License>`_ of
46 Orthanc requires them to **publicly release the source code of this
47 derived version of Orthanc**.
48
49 Finally, if you need to complement the commercial services of your
50 official supplier, please note that you can also contact a company
51 that provides **commercial support on the top of Orthanc**. Currently,
52 `Osimis <http://osimis.io/>`_ is the only company ensuring such
53 corporate services, but others might show up in the future. A `contact
54 form <http://www.orthanc-server.com/orthanc-pro.php>`_ is available on
55 the official Web page of Orthanc.