From 2dcb094d7d98385d9f11630961e1927bb793bd27 Mon Sep 17 00:00:00 2001 From: Antoine Riard Date: Thu, 13 Jul 2023 17:19:58 +0100 Subject: [PATCH 1/4] Add code of conduct minimal neutral guarantees --- docs/code_of_conduct.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/code_of_conduct.md b/docs/code_of_conduct.md index 364aaa84f..33f22bb2c 100644 --- a/docs/code_of_conduct.md +++ b/docs/code_of_conduct.md @@ -20,6 +20,9 @@ Private or public harassment of any kind will not be tolerated. Since harassment Additionally, spam and other content which disrupts or prevents LDK contributors from working on LDK is not acceptable. +In case of a concrete issue that raises a deadlock about the application of the code of conduct, 2 additional members should be selected by consensus of the code of conduct team from the community of +active LDK contributors to join the team in its decision-making process to adjudicate the case. The decision of the majority of the 5 members is binding. + ## The Code of Conduct Team A small team of LDK contributors has volunteered to enforce the LDK Code of Conduct. If you feel like a community member has engaged in inappropriate behavior, please don't hesitate to contact one of the following LDK contributors via email or on Discord: @@ -27,6 +30,12 @@ A small team of LDK contributors has volunteered to enforce the LDK Code of Cond * Val Wallace - vwallace on protonmail.com * Devrandom - devrandom99 on proton.me +The Code of Conduct team should be renew every 2 years with a transparent nomination process opened to the whole community of active LDK contributors. + +The next nomination should happen in December 2024. Current Code of conduct team members can be reconducted in their roles. + +Nomination process should be defined in its ulterior document. + ## The Code of Conduct Team’s Responsibilities Team members are tasked with responding to reports within 24 hours. They will review each incident and determine, to the best of their ability: From f50298464ddfb8b46bb82232db1a6f65a8aca535 Mon Sep 17 00:00:00 2001 From: Antoine Riard Date: Fri, 14 Jul 2023 03:29:02 +0100 Subject: [PATCH 2/4] Request code of conduct members 50 commits / 2y exp --- docs/code_of_conduct.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/code_of_conduct.md b/docs/code_of_conduct.md index 33f22bb2c..8d483f56f 100644 --- a/docs/code_of_conduct.md +++ b/docs/code_of_conduct.md @@ -34,6 +34,8 @@ The Code of Conduct team should be renew every 2 years with a transparent nomina The next nomination should happen in December 2024. Current Code of conduct team members can be reconducted in their roles. +Code of conduct team members should have realized at least 50 code commits in the main LDK git tree and the first commit should have been merged more than 2 years at the date of nomination. + Nomination process should be defined in its ulterior document. ## The Code of Conduct Team’s Responsibilities From fa82902e9a69368bc8d90b336834560f8d9a3ba6 Mon Sep 17 00:00:00 2001 From: Antoine Riard Date: Fri, 14 Jul 2023 03:33:34 +0100 Subject: [PATCH 3/4] Remove the formality and extend to 3y --- docs/code_of_conduct.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/code_of_conduct.md b/docs/code_of_conduct.md index 8d483f56f..8e5b932eb 100644 --- a/docs/code_of_conduct.md +++ b/docs/code_of_conduct.md @@ -30,14 +30,12 @@ A small team of LDK contributors has volunteered to enforce the LDK Code of Cond * Val Wallace - vwallace on protonmail.com * Devrandom - devrandom99 on proton.me -The Code of Conduct team should be renew every 2 years with a transparent nomination process opened to the whole community of active LDK contributors. +The Code of Conduct team should be renew every 3 years with a transparent nomination process opened to the whole community of active LDK contributors. -The next nomination should happen in December 2024. Current Code of conduct team members can be reconducted in their roles. +The next nomination should happen in December 2025. Current Code of conduct team members can be reconducted in their roles. Code of conduct team members should have realized at least 50 code commits in the main LDK git tree and the first commit should have been merged more than 2 years at the date of nomination. -Nomination process should be defined in its ulterior document. - ## The Code of Conduct Team’s Responsibilities Team members are tasked with responding to reports within 24 hours. They will review each incident and determine, to the best of their ability: From 244e42188e14bfdd57ef2e135b338e0e7dc2bc6d Mon Sep 17 00:00:00 2001 From: Antoine Riard Date: Wed, 26 Jul 2023 00:12:16 +0100 Subject: [PATCH 4/4] Define deadlock, staggered approach and PoW for active contributors --- docs/code_of_conduct.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/docs/code_of_conduct.md b/docs/code_of_conduct.md index 8e5b932eb..483016e28 100644 --- a/docs/code_of_conduct.md +++ b/docs/code_of_conduct.md @@ -20,8 +20,10 @@ Private or public harassment of any kind will not be tolerated. Since harassment Additionally, spam and other content which disrupts or prevents LDK contributors from working on LDK is not acceptable. -In case of a concrete issue that raises a deadlock about the application of the code of conduct, 2 additional members should be selected by consensus of the code of conduct team from the community of -active LDK contributors to join the team in its decision-making process to adjudicate the case. The decision of the majority of the 5 members is binding. +Deadlock can arise about the application fo the code of conduct to a concrete issue, where a deadlock is defined as lack of unanimity between the Code of Conduct team on the decision to be taken. + +In that case, 2 additional members should be selected by consensus of the code of conduct team from the community of active LDK contributors to join the team in its decision-making process to adjudicate +the issue. The decision of the majority of 5 members is binding. ## The Code of Conduct Team @@ -30,12 +32,15 @@ A small team of LDK contributors has volunteered to enforce the LDK Code of Cond * Val Wallace - vwallace on protonmail.com * Devrandom - devrandom99 on proton.me -The Code of Conduct team should be renew every 3 years with a transparent nomination process opened to the whole community of active LDK contributors. +The Code of Conduct team should be renewed every 3 years with a transparent nomination process open to the whole community of active LDK contributors. An active LDK contributor is someone with 10 commits during the 2 years +preceeding the nomination. -The next nomination should happen in December 2025. Current Code of conduct team members can be reconducted in their roles. +The next nomination should happen in December 2025. 2 new additional members should be added to the Code of Conduct team to favor a staggered approach where elder members can provide experience to newer members. Current Code of conduct team members can be reconducted in their roles. Code of conduct team members should have realized at least 50 code commits in the main LDK git tree and the first commit should have been merged more than 2 years at the date of nomination. +In case of a current Code of conduct team stepping down on its own initiative, the vacant place should be fulfilled according to the transparent nomination process defined above. + ## The Code of Conduct Team’s Responsibilities Team members are tasked with responding to reports within 24 hours. They will review each incident and determine, to the best of their ability: