Adapt the text about the DCO
@@ -82,14 +82,14 @@ Any contribution without threshold on these topics renders a user as official Ga
contributions are tracked using the git history. However, the use of personal data is regulated in Europe and one
should have the authorisation of users to be cited with their personal information for publications (their full name
is mandatory, and if any their affiliation and their ORCID number). For this reason, we propose to use the
-`Developer Certificate of Origin` (DCO, see the file ``DeveloperCertificate.rst``) for each commit. Its acceptation by
-contributors will permit to:
+`Developer Certificate of Origin` (DCO, see the text in `here <https://developercertificate.org/>`_) for each commit.
+Its acceptation by contributors will permit to:
- certify that a user wrote or otherwise has the right to submit a code under our open source licence,
- allow our project to use their personal data for the contributions' record (ie for releases).
-The file ``README.md`` will contain a `Contributing` section explaining that the project follows this DCO, as well
-as a link to this PIG.
+The file ``README.md`` will contain a `Contributing` section explaining that the project follows this DCO that will be
+given in a new ``CONTRIBUTING.md`` file, as well as a link to this PIG.
.. important::
For practical reasons, the developers strongly recommend that the contributors use always the same GitHub account
