Skip to content

Commit 6dad2aa

Browse files
committed
[RFC] Add criteria for inactive users
1 parent c8a5057 commit 6dad2aa

File tree

1 file changed

+27
-0
lines changed

1 file changed

+27
-0
lines changed
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Meta
2+
[meta]: #meta
3+
- Name: Define Criteria for Inactive Github Members
4+
- Start Date: 2023-10-25
5+
- Author(s): @beyhan
6+
- Status: Draft <!-- Acceptable values: Draft, Approved, On Hold, Superseded -->
7+
- RFC Pull Request: (fill in with PR link after you submit it)
8+
9+
## Summary
10+
11+
Define criteria for the Cloud Foundry Github organization which can be used to identify inactive members.
12+
13+
## Problem
14+
15+
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:
16+
* We don't know how many active members we have
17+
* A potential change of the Github plan which costs depends on the number of Github organization members will generate higher costs
18+
* Security risk because some of the inactive members could have access to resources belonging the Cloud Foundry Github organization
19+
20+
21+
## Proposal
22+
23+
Following criteria should be use to identify inactive users:
24+
* No contributions to the Cloud Foundry Github organization repositories for a period of 12 months
25+
* No participations in any working group activities
26+
27+
If the criteria for inactivity 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 revocation. 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 revoke the role by merging the PR.

0 commit comments

Comments
 (0)