Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Add criteria and define a removal process for inactive users #707

Merged
merged 4 commits into from
Nov 21, 2023
Merged

[RFC] Add criteria and define a removal process for inactive users #707

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6dad2aa
[RFC] Add criteria for inactive users
beyhan Oct 25, 2023
ad26695
Add section for the criteria and the process
beyhan Oct 25, 2023
d64e89f
Add a section for the initial cleanup
beyhan Oct 31, 2023
157a57d
Define contribution and address comments about implementation
beyhan Nov 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions toc/rfc/rfc-draft-define-criteria-and-removal-process-for-inactive-members.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Meta
[meta]: #meta
- Name: Define Criteria and Process to Remove Inactive Cloud Foundry Github Members
- Start Date: 2023-10-25
- Author(s): @beyhan
- Status: Draft <!-- Acceptable values: Draft, Approved, On Hold, Superseded -->
- RFC Pull Request: (fill in with PR link after you submit it)

## Summary

Define criteria for the Cloud Foundry Github organization which can be used to identify inactive members. Additionally, define a process how to remove the inactive members.

## Problem

Currently, there are no criteria to identify inactive members in the Cloud Foundry Github organization. Therefore we have many members in the Cloud Foundry organization, who are not actively contributing anymore. This has many downsides for the foundation like:
* We don't know how many active members we have
* A potential change of the Github plan which costs depends on the number of Github organization members will generate higher costs
* Security risk because some of the inactive members could have access to resources belonging the Cloud Foundry Github organization


## Proposal

### Criteria for Inactive Members

The period to analyze should be the last 12 months and following criteria should be use to identify inactive users:
* No contributions to the Cloud Foundry Github organization repositories
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Contribution = merged commit, PR, issue, commenting on PR/issue, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. Should we clarify it more concrete?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's be more concrete.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

* No participations in working group activities
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want the same rules for reviewers and approvers? Or is a dedicated WG role treated as "participation in WG activities"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My intention was to describe any activity which can be executed as CFF contributor. It should be independent of the WG role. Regarding the period in the past which should be taken in the account I think having the same is ok.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can make it explicit that this RFC is not about working group reviewers or approvers?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done


### Remove the membership to the Cloud Foundry Github Organization

If the inactivity criteria are fulfilled for a member they should be removed from the Cloud Foundry Github organization. Any automation, approver or TOC member may submit a PR to remove the member from the Cloud Foundry Github organization. The person whose membership is being removed must be given two weeks to refute the removal. The working group lead to which the member belongs or TOC in case the member doesn't belong to any working group must make the final decision to remove the membership by merging the PR.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The initial cleanup will have to handle several hundreds inactive users. I guess we want to allow bulk PRs that remove many members at once, at least for the initial cleanup.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! I added a new section about this. Is it ok like this?