From 6390e28a5a6b311e97370d86725bd98e24e22ce2 Mon Sep 17 00:00:00 2001 From: Abhilash Shetty <95069770+abhilashshetty04@users.noreply.github.com> Date: Tue, 12 Jul 2022 15:27:43 +0530 Subject: [PATCH] Update contibuter docs to mention that DCO signoff is mandatory (#365) Signed-off-by: Abhilash Shetty --- CONTRIBUTING.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b098bf5f..3edec321 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -33,10 +33,14 @@ OpenEBS is an Apache 2.0 Licensed project and all your commits should be signed * Raise a new [Pull Request](https://github.com/openebs/jiva/pulls). * If your PR is not getting reviewed or you need a specific person to review it, please reach out to the OpenEBS Contributors. See [OpenEBS Community](https://github.com/openebs/openebs/tree/HEAD/community). +--- + ## Sign your work We use the Developer Certificate of Origin (DCO) as an additional safeguard for the OpenEBS project. This is a well established and widely used mechanism to assure that contributors have confirmed their right to license their contribution under the project's license. Please read [dcofile](https://github.com/openebs/openebs/blob/HEAD/contribute/developer-certificate-of-origin). If you can certify it, then just add a line to every git commit message: +Please certify it by just adding a line to every git commit message. Any PR with Commits which does not have DCO Signoff will not be accepted: + ```` Signed-off-by: Random J Developer ```` @@ -46,5 +50,6 @@ If you set your `user.name` and `user.email` in git config, you can sign your co You can also use git [aliases](https://git-scm.com/book/tr/v2/Git-Basics-Git-Aliases) like `git config --global alias.ci 'commit -s'`. Now you can commit with `git ci` and the commit will be signed. +--- ### Make your changes and build them