From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail-a.sr.ht; dkim=pass header.d=johnnyrichard.com header.i=@johnnyrichard.com Received: from out-189.mta0.migadu.com (out-189.mta0.migadu.com [IPv6:2001:41d0:1004:224b::bd]) by mail-a.sr.ht (Postfix) with ESMTPS id 55E9B20274 for <~johnnyrichard/olang-devel@lists.sr.ht>; Thu, 22 Feb 2024 17:40:59 +0000 (UTC) X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=johnnyrichard.com; s=key1; t=1708623658; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=A81iRvLQ8jHsrN1YJZHT7Y51tsgL3ctLBnN5a/V5qOE=; b=VzM5hQI12m9CGMp0+zuLI8a+f4q4i7UXc8CDzKIR7EoDAD30z9WjiTOalUfSsKhXvKl4kC 0MSUVZmnrxlk8fl2rd8IPUFaOYHbSpD6iDO1TTICh3rL94bfY7qJ5/EKGuRYfukF9raItX rdqqcYlxKCwut4asWaKpcEuna04QTCgVPg5jPiKD1qYrlr4lEAwUzMzkRDMfuOBdptvDfM 8r8tYqpQZjqpJhm+J2t86fM2E+zVTloI3F8pb7bnr1XMemVv2sb7gmGaGuh+IOc2tzyYr9 iYSODG8qQxPHfr9IiSPkxglt35iPS78+BfDGSRSLyLTAEdC3t79jNA/CAlbIbA== From: Johnny Richard To: ~johnnyrichard/olang-devel@lists.sr.ht Cc: Johnny Richard Subject: [PATCH olang] docs: add DCO information on hacking page Date: Thu, 22 Feb 2024 19:38:03 +0100 Message-ID: <20240222184005.77441-1-johnny@johnnyrichard.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT X-TUID: x5pgQBRKM05G All contributions must be signed off by the author. There is a link to the Developer Certificate of Origin version 1.1. Signed-off-by: Johnny Richard --- I'm adding a link to the DCO document. I'm not sure if this document will survive for a long time. Let me know if I should attach the DCO text to our documentation. docs/pages/hacking.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/pages/hacking.md b/docs/pages/hacking.md index 7ebd4b3..ef88791 100644 --- a/docs/pages/hacking.md +++ b/docs/pages/hacking.md @@ -68,7 +68,11 @@ make check Submitting a patch ------------------ -Before submit a patch, ensure your code follows our coding style and is +All contributors are required to "sign-off" their commits (using git commit -s) +to indicate that they have agreed to the [Developer Certificate of +Origin](https://developercertificate.org/). + +Before submit the patch, ensure the code follows our coding style and is well-tested. After that, you\'re good to follow the steps bellow. ### Step 1: Commit your changes -- 2.43.2