diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5290791ec06bc7b2ea2061f053ce5d247a870205..52230c335461bd9cbee1f8f8eb0f619c5f1c232b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -127,7 +127,7 @@ Make sure all of your submitted new files have a licensing statement in the head ### Substantial Contributions -Therefore, if your contribution is only a patch directly applied to an existing file, then you are not required to do anything. If your contribution is an entire new project, or a substantial, copyrighted contribution, you **MUST** make sure that you do that following the [IP Policy](https://booting.oniroproject.org/distro/governance/ip-policy) and that you comply with REUSE standard to include the licensing information where they are required. +Therefore, if your contribution is only a patch directly applied to an existing file, then you are not required to do anything. If your contribution is an entire new project, or a substantial, copyrighted contribution, you **MUST** make sure that you do that following the [IP Policy](https://git.ostc-eu.org/oss-compliance/ip-policy/) and that you comply with REUSE standard to include the licensing information where they are required. # DCO sign-off diff --git a/contributing/reuse.rst b/contributing/reuse.rst index ba567f72f0be23e74f2dfc968444f49b25f20092..b0c5b7cf868069d9274ff318eeb4c9f3ce3ba651 100644 --- a/contributing/reuse.rst +++ b/contributing/reuse.rst @@ -45,4 +45,4 @@ Make sure all of your submitted new files have a licensing statement in the head Substantial Contributions ------------------------- -Therefore, if your contribution is only a patch directly applied to an existing file, then you are not required to do anything. If your contribution is an entire new project, or a substantial, copyrighted contribution, you **MUST** make sure that you do that following the `IP Policy <https://booting.oniroproject.org/distro/governance/ip-policy>`_ and that you comply with REUSE standard to include the licensing information where they are required. +Therefore, if your contribution is only a patch directly applied to an existing file, then you are not required to do anything. If your contribution is an entire new project, or a substantial, copyrighted contribution, you **MUST** make sure that you do that following the `IP Policy <https://git.ostc-eu.org/oss-compliance/ip-policy/>`_ and that you comply with REUSE standard to include the licensing information where they are required.