General Guidelines : DCO adherence

Mentioned DCO in legal stuff section.

Bug-AGL: [SPEC-3633]

Signed-off-by: Shankho Boron Ghosh <shankhoghosh123@gmail.com>
Change-Id: Ifbbae95196ce6db1b7d3ad32f9c46ac4c727dacd
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/documentation/+/25593
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Tested-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>

diff --git a/docs/5_How_To_Contribute/7_General_Guidelines.md b/docs/5_How_To_Contribute/7_General_Guidelines.md
index 1cb7d69..b72e912 100644 (file)
--- a/docs/5_How_To_Contribute/7_General_Guidelines.md
+++ b/docs/5_How_To_Contribute/7_General_Guidelines.md
@@ -152,7 +152,8 @@ We have tried to make it as easy as possible to make contributions. This applies
 to how we handle the legal aspects of contribution.
 
 We simply ask that when submitting a patch for review, the developer must
-include a sign-off statement in the commit message.
+include a sign-off statement in the commit message. This is done to ensure that
+the author of the change adhere to follow [**DCO**](https://developercertificate.org/).
 
 ```sh
 Signed-off-by: John Doe <john.doe@example.com>