-
Notifications
You must be signed in to change notification settings - Fork 228
Inactive users to be deleted #1359
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.
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
beyhan
added a commit
that referenced
this pull request
Nov 6, 2025
According to the rules for inactivity defined in [RFC-0025](https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0025-define-criteria-and-removal-process-for-inactive-members.md), the following users should be removed from ARI approvers/reviewers/bots: @mrosecrance @mvach @Cryogenics-CI @joefitzgerald According to the [revocation policy in the RFC](https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0025-define-criteria-and-removal-process-for-inactive-members.md#remove-the-membership-to-the-cloud-foundry-github-organization), users have two weeks to refute this revocation, if they wish by commenting on this pull-request and open a new pull-request to be re-added as approver after this one is merged. Inactivity was detected by a github action, see #1359
stephanme
added a commit
that referenced
this pull request
Nov 17, 2025
…ithub.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0025-define-criteria-and-removal-process-for-inactive-members.md), the following users should be removed from ARI approvers/reviewers/bots: @KesavanKing @pivotalgeorge @xiujiao @pyogesh2 According to the [revocation policy in the RFC](https://github.com/cloudfoundry/community/blob/main/toc/rfc/rfc-0025-define-criteria-and-removal-process-for-inactive-members.md#remove-the-membership-to-the-cloud-foundry-github-organization), users have two weeks to refute this revocation, if they wish by commenting on this pull-request and open a new pull-request to be re-added as approver after this one is merged. Inactivity was detected by a github action, see #1359
rkoster
approved these changes
Nov 18, 2025
beyhan
approved these changes
Nov 18, 2025
cweibel
approved these changes
Nov 18, 2025
stephanme
approved these changes
Nov 18, 2025
stephanme
added a commit
that referenced
this pull request
Nov 18, 2025
- radito3 was removed by #1359 - temp-multiapps-admins is a manually maintained team
stephanme
added a commit
that referenced
this pull request
Nov 18, 2025
- radito3 was removed by #1359 - temp-multiapps-admins is a manually maintained team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the rules for inactivity defined in RFC-0025 following users will be deleted:
@jbooherl
@bgandon
@radito3
@ohkyle
@weresch
@cunnie
@max-soe
According to the revocation policy in the RFC, users have two weeks to refute this revocation, if they wish by commenting on this pull-request and open a new pull-request to be re-added as contributor after this one is merged.
As alternative, if you are active in a working group please check the promotion rules and if you are eligible and wish apply for a role in that working group.
Warning:
Inactive users of Working Group "toc" are:
@thelinuxfoundation
Inactive users of Working Group "App Runtime Interfaces" are:
@KesavanKing
@pivotalgeorge
@cf-frontend
@xiujiao
@pyogesh2
Inactive users of Working Group "Paketo" are:
@sophiewigmore
@emmjohnson
@joshuatcasey
@accrazed
Inactive users of Working Group "Foundational Infrastructure" are:
@joefitzgerald
@Cryogenics-CI
@mvach
@mrosecrance
Inactive users of Working Group "Vulnerability Management" are:
@thomasthal
Inactive users of Working Group "App Runtime Platform" are:
@svcboteos
@shrisha-c
@vlast3k
@Cryogenics-CI
@fhambrec
@stefanlay
Inactive users of Working Group "Service Management" are:
@cf-gitbot