--- a/Sphinx/source/contributing.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/contributing.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -60,7 +60,7 @@
       REST API or HL7 messages, instead of reading them from some
       folder on the filesystem.
     + Have a look at the TODO file containing our `official roadmap
-      <https://bitbucket.org/sjodogne/orthanc/src/default/TODO>`__.
+      <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__.
 
   - Always remember that he **recommended way of contributing to the
     source code of Orthanc is by creating C/C++ plugins**. If the

--- a/Sphinx/source/developers/coding-style.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/developers/coding-style.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -12,7 +12,7 @@
 <https://en.wikipedia.org/wiki/Indent_style#Allman_style>`__", with
 some adaptations that are described below. A compliant Eclipse
 formatter is `available in the Orthanc distribution
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/EclipseCodingStyle.xml>`__.
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/EclipseCodingStyle.xml>`__.
 
 Licensing
 ---------

--- a/Sphinx/source/developers/creating-plugins.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/developers/creating-plugins.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -21,7 +21,7 @@
 
 * Sample code for plugins can be found `in the official Orthanc
   repository
-  <https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/>`__
+  <https://hg.orthanc-server.com/orthanc/file/default/Plugins/Samples/>`__
   (in the ``Plugins/Samples`` folder).
 
 * A tutorial showing how to implement a basic WADO server is
@@ -73,7 +73,7 @@
 that is part of the Orthanc source distribution:
 
 * `Plugins/Include/orthanc/OrthancCPlugin.h
-  <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/Plugins/Include/orthanc/OrthancCPlugin.h>`__
+  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/Plugins/Include/orthanc/OrthancCPlugin.h>`__
 
 `Online documentation <https://sdk.orthanc-server.com/>`__ for this C
 header is available, as generated by `Doxygen
@@ -87,8 +87,8 @@
 ``HAS_ORTHANC_EXCEPTION`` is set to ``0``:
 
 * `Plugins/Samples/Common/OrthanPluginCppWrapper.h
-  <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginCppWrapper.h>`__
+  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginCppWrapper.h>`__
 * `Plugins/Samples/Common/OrthanPluginCppWrapper.cpp
-  <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginCppWrapper.cpp>`__
+  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginCppWrapper.cpp>`__
 * `Plugins/Samples/Common/OrthanPluginException.h
-  <https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginException.h>`__
+  <https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/Plugins/Samples/Common/OrthancPluginException.h>`__

--- a/Sphinx/source/dicom-guide.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/dicom-guide.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -128,7 +128,7 @@
 <https://en.wikipedia.org/wiki/Medical_ultrasound>`__).
 
 `As written in its DICOM conformance statement
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/DicomConformanceStatement.txt>`__,
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/DicomConformanceStatement.txt>`__,
 the Orthanc software can receive, store and send any kind of DICOM
 images (i.e. all the standard transfer syntaxes are
 supported). Furthermore, Orthanc can :ref:`convert most uncompressed

--- a/Sphinx/source/faq/compiling-old.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/faq/compiling-old.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -7,7 +7,7 @@
 This page summarizes the GNU/Linux build instructions that were used
 **up to Orthanc 0.7.0 (inclusive)**.  Instructions for Orthanc above
 0.7.0 can be found directly `inside the source package
-<https://bitbucket.org/sjodogne/orthanc/src/default/LinuxCompilation.txt>`_.
+<https://hg.orthanc-server.com/orthanc/file/default/LinuxCompilation.txt>`_.
 
 Static linking
 --------------

--- a/Sphinx/source/faq/compiling.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/faq/compiling.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -7,7 +7,7 @@
 ---------------
 
 * Orthanc >= 0.7.1: See the `build instructions
-  <https://bitbucket.org/sjodogne/orthanc/src/default/LinuxCompilation.txt>`_
+  <https://hg.orthanc-server.com/orthanc/file/default/LinuxCompilation.txt>`_
   inside the source package.
 * Orthanc <= 0.7.0: See the :ref:`compiling-old`.
 
@@ -30,7 +30,7 @@
 -----------------------
 
 See the `build instructions for Windows
-<https://bitbucket.org/sjodogne/orthanc/src/default/INSTALL>`_ inside
+<https://hg.orthanc-server.com/orthanc/file/default/INSTALL>`_ inside
 the source package.
 
 Under OS X
@@ -39,7 +39,7 @@
 The mainline of Orthanc can compile under Apple OS X, with the XCode
 compiler, since June 24th, 2014. See the `build instructions for
 Darwin
-<https://bitbucket.org/sjodogne/orthanc/src/default/DarwinCompilation.txt>`_
+<https://hg.orthanc-server.com/orthanc/file/default/DarwinCompilation.txt>`_
 inside the source package.
 
 Performance warning
@@ -64,7 +64,7 @@
 the third-party dependencies directly inside the Orthanc
 executable. This is the meaning of the ``-DSTATIC_BUILD=ON`` option,
 as described in the `INSTALL
-<https://bitbucket.org/sjodogne/orthanc/src/default/INSTALL>`_ file of Orthanc.
+<https://hg.orthanc-server.com/orthanc/file/default/INSTALL>`_ file of Orthanc.
 
 Such a static linking is very desirable under Windows, since the
 Orthanc binaries do not depend on any external DLL, which results in a

--- a/Sphinx/source/faq/licensing.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/faq/licensing.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -274,7 +274,7 @@
   should be focused on one very specific issue or feature. Large
   architectural changes are reserved for the core development team of
   Orthanc, as we must follow our `long-term roadmap
-  <https://bitbucket.org/sjodogne/orthanc/src/default/TODO>`__.
+  <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__.
 
 * Unit testing is mandatory. Integration tests should be submitted to
   the `dedicated repository

--- a/Sphinx/source/faq/orthanc-ids.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/faq/orthanc-ids.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -41,7 +41,7 @@
 
 The actual implementation of the hashing is carried on by the
 `DicomInstanceHasher class
-<https://bitbucket.org/sjodogne/orthanc/src/default/Core/DicomFormat/DicomInstanceHasher.cpp>`_.
+<https://hg.orthanc-server.com/orthanc/file/default/Core/DicomFormat/DicomInstanceHasher.cpp>`_.
 
 
 The "Inexistent Tag" error

--- a/Sphinx/source/faq/orthanc-storage.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/faq/orthanc-storage.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -59,9 +59,9 @@
 database schema is kept as simple as possible, and can be found in the
 following two files of the source code of Orthanc:
 `PrepareDatabase.sql
-<https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/OrthancServer/Database/PrepareDatabase.sql>`__
+<https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/OrthancServer/Database/PrepareDatabase.sql>`__
 and `InstallTrackAttachmentsSize.sql
-<https://bitbucket.org/sjodogne/orthanc/src/Orthanc-1.6.0/OrthancServer/Database/InstallTrackAttachmentsSize.sql>`__.
+<https://hg.orthanc-server.com/orthanc/file/Orthanc-1.6.0/OrthancServer/Database/InstallTrackAttachmentsSize.sql>`__.
 
 
 Direct access

--- a/Sphinx/source/faq/rest-samples.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/faq/rest-samples.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -10,7 +10,7 @@
   dedicated section <rest-advanced>`.
 * Many working examples written in Python are `available in the source
   distribution
-  <https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Python/>`__.
+  <https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/Python/>`__.
 * If you cannot find an example for some feature in this manual or in
   the Python examples, please check the `publicly available
   integration tests

--- a/Sphinx/source/faq/supported-images.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/faq/supported-images.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -5,7 +5,7 @@
 
 Orthanc can **receive/store/send** any kind of standard DICOM files
 (cf. the `DICOM conformance statement
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/DicomConformanceStatement.txt>`__).
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/DicomConformanceStatement.txt>`__).
 Note that the ``UnknownSopClassAccepted`` :ref:`configuration option
 <configuration>` can be set to `true` if interfacing with modalities
 that are producing non-standard SOP classes.

--- a/Sphinx/source/faq/transcoding.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/faq/transcoding.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -13,7 +13,7 @@
 
 Adding support for transcoding is one of the features that is pending
 on `our roadmap
-<https://bitbucket.org/sjodogne/orthanc/src/default/TODO>`__, and for which 
+<https://hg.orthanc-server.com/orthanc/file/default/TODO>`__, and for which 
 we are looking for industrial sponsors.
 
 
@@ -108,7 +108,7 @@
 ``OrthancPluginRegisterOnStoredInstanceCallback()`` function). A
 sample Lua script that converts every incoming DICOM file to the
 JPEG2k transfer syntax is `part of the Orthanc sources
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Lua/AutomatedJpeg2kCompression.lua>`__.
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/Lua/AutomatedJpeg2kCompression.lua>`__.
 
 
 Finally, as a fourth solution, it is possible to **combine two Orthanc

--- a/Sphinx/source/faq/troubleshooting.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/faq/troubleshooting.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -106,7 +106,7 @@
   advantage of this patch, you need to statically link Orthanc against
   DCMTK by using the ``-DUSE_SYSTEM_DCMTK=OFF`` flag `when invoking
   CMake
-  <https://bitbucket.org/sjodogne/orthanc/src/default/LinuxCompilation.txt>`__.
+  <https://hg.orthanc-server.com/orthanc/file/default/LinuxCompilation.txt>`__.
 
 Checking DICOM file integrity
 -----------------------------

--- a/Sphinx/source/plugins/serve-folders.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/plugins/serve-folders.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -12,7 +12,7 @@
  
 The source code of this sample plugin is `available in the source
 distribution of Orthanc
-<https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/ServeFolders/>`__
+<https://hg.orthanc-server.com/orthanc/file/default/Plugins/Samples/ServeFolders/>`__
 (GPLv3+ license).
 
 

--- a/Sphinx/source/plugins/worklists-plugin.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/plugins/worklists-plugin.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -26,7 +26,7 @@
 
 The source code of this sample plugin is `available in the source
 distribution of Orthanc
-<https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/ModalityWorklists/>`__
+<https://hg.orthanc-server.com/orthanc/file/default/Plugins/Samples/ModalityWorklists/>`__
 (GPLv3+ license).
 
 
@@ -59,7 +59,7 @@
 
 The folder ``WorklistsDatabase`` of the `source distribution of
 Orthanc
-<https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/ModalityWorklists/>`__
+<https://hg.orthanc-server.com/orthanc/file/default/Plugins/Samples/ModalityWorklists/>`__
 contains a database of sample worklists, that comes from the DCMTK
 source distribution, as described in the `FAQ entry #37 of the DCMTK
 project <https://forum.dcmtk.org/viewtopic.php?t=84>`__.
@@ -73,7 +73,7 @@
 - Download `DCMTK utilities
   <https://dicom.offis.de/download/dcmtk/release/bin/>`__.
 - Download sample `worklist files
-  <https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/ModalityWorklists/>`__
+  <https://hg.orthanc-server.com/orthanc/file/default/Plugins/Samples/ModalityWorklists/>`__
   from the Orthanc source code and copy them in a dedicated folder.
 - Generate the :ref:`default configuration of Orthanc <configuration>`.
 - Enable the ModalityWorklist plugin in your configuration file by adding this section::
@@ -130,7 +130,7 @@
   
 - Start with an existing worklist file, some samples of which can be
   found in the `Orthanc source distribution
-  <https://bitbucket.org/sjodogne/orthanc/src/default/Plugins/Samples/ModalityWorklists/WorklistsDatabase/>`__
+  <https://hg.orthanc-server.com/orthanc/file/default/Plugins/Samples/ModalityWorklists/WorklistsDatabase/>`__
   (with ``.wl`` file extensions).
 - The worklist file is a DICOM file. Dump its content as a text file
   using ``dcmdump``::

--- a/Sphinx/source/users/lua.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/users/lua.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -13,7 +13,7 @@
 scripting.
 
 Many other examples are `available in the source distribution
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Lua/>`__.
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/Lua/>`__.
 
 
 Installing a Lua script
@@ -108,7 +108,7 @@
   protocol. This allows to inspect the content of the C-Find query,
   and possibly modify it if a patch is needed for some manufacturer. A
   `sample script is available
-  <https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Lua/IncomingFindRequestFilter.lua>`__.
+  <https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/Lua/IncomingFindRequestFilter.lua>`__.
 
 Some other **resource-related events** are available:
 
@@ -137,7 +137,7 @@
 SCP, several callbacks are successively invoked to specify which
 **transfer syntaxes** are accepted for the association. These
 callbacks are listed in `this sample script
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Lua/TransferSyntaxEnable.lua>`__.
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/Lua/TransferSyntaxEnable.lua>`__.
 
 *Note:* All of these callbacks are guaranteed to be **invoked in
 mutual exclusion**. This implies that Lua scripting in Orthanc does

--- a/Sphinx/source/users/replication.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/users/replication.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -71,7 +71,7 @@
 
 The most direct way to replicate an instance of Orthanc consists in
 using the `ImportDicomFiles
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/ImportDicomFiles/ImportDicomFiles.py>`_
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/ImportDicomFiles/ImportDicomFiles.py>`_
 script of the Orthanc distribution. For instance, the following
 command would recursively explore the content of the
 ``OrthancStorage`` folder (where Orthanc stores its DICOM files by
@@ -111,7 +111,7 @@
 -------------------
 
 If you cannot use the first method, you can use the `Replicate
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Python/Replicate.py>`_
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/Python/Replicate.py>`_
 script of the Orthanc distribution. This script will use the REST API
 of both the source and target instances of Orthanc. For instance::
 

--- a/Sphinx/source/users/rest.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/users/rest.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -57,7 +57,7 @@
     $ curl -X POST -H "Expect:" http://localhost:8042/instances --data-binary @CT.X.1.2.276.0.7230010.dcm
 
 The code distribution of Orthanc contains a `sample Python script
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/ImportDicomFiles/ImportDicomFiles.py>`__
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/ImportDicomFiles/ImportDicomFiles.py>`__
 that recursively upload the content of some folder into Orthanc using
 the REST API::
 
@@ -598,7 +598,7 @@
    The list of the resources to be sent are given as a JSON array. In
    this case, a single DICOM connection is used. `Sample code is
    available
-   <https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Python/HighPerformanceAutoRouting.py>`__.
+   <https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/Python/HighPerformanceAutoRouting.py>`__.
 
    Note that the list of resources to be sent can include the
    :ref:`Orthanc identifiers <orthanc-ids>` of entire patients,
@@ -922,7 +922,7 @@
     $ curl 'http://localhost:8042/changes?limit=100&since=922'
 
 A `sample code in the source distribution
-<https://bitbucket.org/sjodogne/orthanc/src/default/Resources/Samples/Python/ChangesLoop.py>`__
+<https://hg.orthanc-server.com/orthanc/file/default/Resources/Samples/Python/ChangesLoop.py>`__
 shows how to use this Changes API to implement a polling loop.
 
 

--- a/Sphinx/source/users/support.rst	Mon Mar 30 20:03:51 2020 +0200
+++ b/Sphinx/source/users/support.rst	Mon Mar 30 20:14:52 2020 +0200
@@ -25,12 +25,12 @@
    <https://groups.google.com/forum/#!forum/orthanc-users>`__.
 7. Check out the ``Pending changes in the mainline`` section of the
    `NEWS file
-   <https://bitbucket.org/sjodogne/orthanc/src/default/NEWS>`__, as
+   <https://hg.orthanc-server.com/orthanc/file/default/NEWS>`__, as
    your issue might already be solved in the mainline of Orthanc (i.e.
    in the cutting-edge version of Orthanc since the last stable
    official release).
 8. Carefully read the `TODO file
-   <https://bitbucket.org/sjodogne/orthanc/src/default/TODO>`__ that
+   <https://hg.orthanc-server.com/orthanc/file/default/TODO>`__ that
    contains our roadmap, as you might be requesting a feature that is
    currently pending in our backlog (i.e. not implemented yet).
 9. Have a look for the issue in the `official bug tracker