Remove Inactive Users FI WG #1271
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
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: @joefitzgerald @Spimtav @xtremerui @colins 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 #1237
Merged
Contributor
|
I refute this revocation. Please see this issue for additional context. |
Member
|
@beyhan please exclude @joefitzgerald from this list so that he stays with CF. Maybe some PR or maintainer work helps, e.g. https://github.com/cloudfoundry/go-uaa/pulls |
Member
Author
this is discussed in #810 |
Based on discussion in #810 (comment)
Member
Author
|
Based on the discussion in #810 I added @joefitzgerald back. |
Member
|
Hi I'm (colins) still a member of the Integrated Databases (Mysql / Postgres) team. |
Member
Author
|
I'm sorry for the delayed answer but I added you back @colins. |
rkoster
approved these changes
Sep 22, 2025
github-project-automation
bot
moved this to Done
in Foundational Infrastructure Working Group
beyhan
added a commit
that referenced
this pull request
Oct 1, 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: @bgandon @max-soe @ichandrabhatta @yharish991 @nouseforaname @pivotalgeorge @tas-operability-bot @cunnie 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. Please also state a reason why you would like to be re-added. Inactivity was detected by a github action, see #1318 I took @joefitzgerald and @colins out based on the discussions in #1271 @yharish991 could you please state a reason why you and @tas-operability-bot should presered the role?
beyhan
added a commit
that referenced
this pull request
Oct 1, 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: @bgandon @max-soe @ichandrabhatta @yharish991 @nouseforaname @pivotalgeorge @tas-operability-bot @cunnie 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. Please also state a reason why you would like to be re-added. Inactivity was detected by a github action, see #1318 I took @joefitzgerald and @colins out based on the discussions in #1271 @yharish991 could you please state a reason why you and @tas-operability-bot should presered the role?
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, the following users should be removed from ARI approvers/reviewers/bots:
@joefitzgerald
@Spimtav
@xtremerui
@colins
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 approver after this one is merged.
Inactivity was detected by a github action, see #1270