Inactive users to be deleted #1318
Open
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
|
I would like to keep my membership and @tas-operability-bot's membership |
|
I would like to keep my membership, please. |
1 similar comment
|
I would like to keep my membership, please. |
|
I would also like to keep my membership, please. |
stephanme
added a commit
that referenced
this pull request
Sep 30, 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: @haochenhu233 @weresch @itsouvalas @chinigo @radito3 @pivotalgeorge 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 #1318
|
I would also like to keep my membership, thanks. |
|
@colins, @joefitzgerald, @itsouvalas, @yharish991 this PR is not removing any of you. This is just an information for the WG leads and they will decide what to do. |
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?
|
@beyhan indeed, the suggested file change didn't have any of us mentioned... it's just that the wording was somewhat misleading... that's all. Thanks for bringing it up though |
cweibel
approved these changes
Oct 7, 2025
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:
@xtremerui
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 Platform" are:
@vlast3k
@stefanlay
@svcboteos
Inactive users of Working Group "Paketo" are:
@accrazed
@emmjohnson
@sophiewigmore
@joshuatcasey
Inactive users of Working Group "App Runtime Interfaces" are:
@haochenhu233
@weresch
@itsouvalas
@cf-frontend
@chinigo
@radito3
@pivotalgeorge
Inactive users of Working Group "Vulnerability Management" are:
@thomasthal
Inactive users of Working Group "Foundational Infrastructure" are:
@bgandon
@max-soe
@ichandrabhatta
@yharish991
@nouseforaname
@pivotalgeorge
@colins
@tas-operability-bot
@cunnie
@joefitzgerald
Inactive users of Working Group "Service Management" are:
@cf-gitbot