From f26f6b3216e70a1e23af61db8f35da6c27134fdb Mon Sep 17 00:00:00 2001 From: Martyn Welch <martyn.welch@collabora.com> Date: Thu, 11 Feb 2021 14:05:05 +0000 Subject: [PATCH] Add checking policies to contribution checklist Whilst we call out specific policies in the contribution checklist, we should make sure that any contributions made to Apertis do not violate any of Apertis' policies. Explicitly add this to the contribution checklist. Signed-off-by: Martyn Welch <martyn.welch@collabora.com> --- content/policies/contribution_checklist.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/policies/contribution_checklist.md b/content/policies/contribution_checklist.md index a6f6b2958..fee48bf25 100644 --- a/content/policies/contribution_checklist.md +++ b/content/policies/contribution_checklist.md @@ -85,6 +85,13 @@ out per contribution type: by any proposed changes. Ensure that such value can be expected before starting development. +- `Contributor` **Ensure proposed changes comply with all existing relevant + policies**: The Apertis maintainers will be evaluating whether the proposed + changes comply with the full range of policies which govern the Apertis + project. Now is a good time, before significant effort is expended, to check + that the proposed changes align with the Apertis projects policies to guide + development and avoid disappointment or wasted effort. + ## Concept Design - `Contributor` **Survey the state of art**: The project strives to adapt and @@ -239,6 +246,9 @@ out per contribution type: taken to evaluate that platform specific changes are made in a way that other platforms are not negatively impacted. +- `Maintainer` **Ensure adherence to Apertis policies**: Changes to Apertis + should only be accepted if they adhere to all the relevant Apertis policies. + ## Code - `Maintainer` **Check coding conventions**: -- GitLab