From b7ebe67c5917e4ebcc3baa790f69b1a493b4149e Mon Sep 17 00:00:00 2001 From: Lance Ball Date: Mon, 3 Jul 2023 14:46:48 -0400 Subject: [PATCH 1/2] docs: add a simple inactivity measure and process for removal The ROLES.md document was recently updated to more accurately reflect how the Knative organization should work with regards to a "contribution ladder" and methods of moving up and down that latter based on project contributions. What was not addressed in those changes was how to handle stepping away from the project or being removed for some reason. This change is meant to address that omission. The text is taken from the CNCF contribution ladder template located here: https://github.com/cncf/project-template/blob/main/CONTRIBUTOR_LADDER.md#inactivity When members step away from the project or step away from leadership roles, they should be removed from teams that have elevated priviledges (writers, reviewers, admin, etc). When members choose to leave the project entirely due to changing employment of life events, they should be removed from the knative and knative-sandbox When members fail to contribute for a period of one year, they may be involuntarily removed from the knative and knative-sandbox GitHub organizations. Signed-off-by: Lance Ball --- ROLES.md | 20 ++++++++++++++++++++ peribolos/knative-extensions.yaml | 2 +- peribolos/knative.yaml | 2 +- 3 files changed, 22 insertions(+), 2 deletions(-) diff --git a/ROLES.md b/ROLES.md index 34402234..9a08c516 100644 --- a/ROLES.md +++ b/ROLES.md @@ -276,6 +276,26 @@ The following apply to the area / component for which one would be a lead. - Mentoring and guiding approvers, members, and new contributors. +## Stepping Down/Emeritus Process +If and when contributors' commitment levels change, contributors can consider stepping down (moving down the contributor ladder) or moving to emeritus status (completely stepping away from the project). + +Once a member has decided to move to emeritus or step down the contributor ladder, their entries in Peribolos should be removed or modified according to the specific change. Members moving to emiritus status should be removed from the Knative GitHub organization in Peribolos through a PR submitted by the member or a member of the Steering Committee. + +## Inactivity +It is important for contributors to be and stay active to set an example and show commitment to the project. Inactivity is harmful to the project as it may lead to unexpected delays, contributor attrition, and a lost of trust in the project. + +* Inactivity is measured by: + * Periods of no contributions for longer than 12 months + * Periods of no communication for longer than 12 months +* Consequences of being inactive include: + * Involuntary Removal or demotion + +## Involuntary Removal or Demotion + +Removal or demotion of a contributor happens when responsibilities and requirements aren't being met. This may include repeated patterns of inactivity, extended period of inactivity, a period of failing to meet the requirements of your role, and/or a violation of the Code of Conduct. This process is important because it protects the community and its deliverables while also opens up opportunities for new contributors to step in. + +Involuntary removal or demotion is handled through a vote by a current Steering Committee members, requiring 4 of 5 votes (80%) in favor of removal. + # Notes Within this section "manager" refers to a Member who is a Working Group Lead or diff --git a/peribolos/knative-extensions.yaml b/peribolos/knative-extensions.yaml index 9bfbde4d..7b9c3f17 100644 --- a/peribolos/knative-extensions.yaml +++ b/peribolos/knative-extensions.yaml @@ -824,7 +824,7 @@ orgs: members: - nak3 - skonto - - psschwei + - psschwei privacy: closed Serving WG Leads: description: The Working Group leads for Serving diff --git a/peribolos/knative.yaml b/peribolos/knative.yaml index dcdce771..f06adede 100644 --- a/peribolos/knative.yaml +++ b/peribolos/knative.yaml @@ -668,7 +668,7 @@ orgs: members: - nak3 - skonto - - psschwei + - psschwei privacy: closed Serving WG Leads: description: The Working Group leads for Serving From cbdd3defb40490a60d2f187f0f7356d9c88def46 Mon Sep 17 00:00:00 2001 From: Carlos Santana Date: Fri, 6 Oct 2023 11:09:46 -0400 Subject: [PATCH 2/2] Update ROLES.md Co-authored-by: Ali Ok --- ROLES.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ROLES.md b/ROLES.md index 9a08c516..90af466b 100644 --- a/ROLES.md +++ b/ROLES.md @@ -292,7 +292,9 @@ It is important for contributors to be and stay active to set an example and sho ## Involuntary Removal or Demotion -Removal or demotion of a contributor happens when responsibilities and requirements aren't being met. This may include repeated patterns of inactivity, extended period of inactivity, a period of failing to meet the requirements of your role, and/or a violation of the Code of Conduct. This process is important because it protects the community and its deliverables while also opens up opportunities for new contributors to step in. +Removal or demotion of a contributor happens when responsibilities and requirements aren't being met. This may include repeated patterns of inactivity, extended period of inactivity, a period of failing to meet the requirements of your role. This process is important because it protects the community and its deliverables while also opens up opportunities for new contributors to step in. + +Similarly, a disciplinary action such as a violation of the Code of Conduct, will result in a removal or demotion of a contributor. Involuntary removal or demotion is handled through a vote by a current Steering Committee members, requiring 4 of 5 votes (80%) in favor of removal.