summaryrefslogtreecommitdiff
path: root/DECISIONS.md
diff options
context:
space:
mode:
authorDaniel Silverstone <dsilvers@digital-scurf.org>2023-10-14 21:37:59 +0100
committerDaniel Silverstone <dsilvers@digital-scurf.org>2023-10-14 21:37:59 +0100
commit5b0c2e62f6b4016ee42033bae68cbc451f857f59 (patch)
tree92bed35f1b3bf106c431094c79efa8fa726594a0 /DECISIONS.md
parentdc61ff8bbf2f7d41256fe09b3524dbe1c8561725 (diff)
downloadsubplot-5b0c2e62f6b4016ee42033bae68cbc451f857f59.tar.gz
DECISIONS: Record DCO decision
Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>
Diffstat (limited to 'DECISIONS.md')
-rw-r--r--DECISIONS.md31
1 files changed, 31 insertions, 0 deletions
diff --git a/DECISIONS.md b/DECISIONS.md
index 4780b5e..b192fdc 100644
--- a/DECISIONS.md
+++ b/DECISIONS.md
@@ -13,6 +13,37 @@ Each decision should have its own heading. Newest decision should come
first. Updated or overturned decisions should have their section
updated to note their status, without moving them.
+## Adopting a Developer Certificate of Origin
+
+Date: 2023-10-07
+
+What: The subplot project is adopting the use of DCO.
+
+Why: To reduce the chance that, in the future when others might wish
+to contribute to Subplot, anyone might claim that we have changes
+which are not permitted, but without incurring the potential additional
+complications associated with CLAs or the like.
+
+Who: Daniel, Lars
+
+Detail: A Developer Certificate of Origin is a statement saying that
+the contributor has the right to make a contribution and to assign
+permission to the project to thence redistribute it under the project
+licence. You can read more at: <https://developercertificate.org/>
+and at <https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin>
+
+This decision was taken during a Subplot project meeting and the
+current scope of the decision is to document our use of DCO 1.1 in
+the contribution guidelines, and to add to our merge request review
+process a human-driven validation of the following of the DCO.
+
+We leave open the possibility of enforcing DCO in some programmatic
+way in the future.
+
+We assert that the presence of a `Signed-off-by` footer in each git
+commit in a merge request is the mechanism by which a developer signals
+that the commit meets the assertions in the DCO 1.1.
+
## Breaking changes in Subplot
Date: 2023-08-27