From dd621d0fadf912c10df24dccfaf85479d6dc4056 Mon Sep 17 00:00:00 2001 From: Philippe Coval <philippe.coval.ext@huawei.com> Date: Fri, 16 Sep 2022 13:16:54 +0200 Subject: [PATCH] contributing: Update policy repo to fallback to OSTC Relate-to: https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/787 Relate-to: https://git.ostc-eu.org/oss-compliance/ip-policy/-/issues/18 Relate-to: https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/merge_requests/311 Forwarded: https://gitlab.eclipse.org/eclipse/oniro-core/docs/-/merge_requests/20 Signed-off-by: Philippe Coval <philippe.coval.ext@huawei.com> --- CONTRIBUTING.md | 2 +- contributing/reuse.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5290791..52230c3 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 ba567f7..b0c5b7c 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. -- GitLab