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.

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

Inactive users to be deleted #1042

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Jan 6, 2025

According to the rules for inactivity defined in RFC-0025 following users will be deleted:
@MerricdeLauney
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 "Service Management" are:
@cf-gitbot
@anoopjb
@swati1102
@rsampaio
@abh1kg
Inactive users of Working Group "Foundational Infrastructure" are:
@ShilpaChandrashekara
@colins
Inactive users of Working Group "CF on K8s" are:
@akrishna90
@matt-royal
@clintyoshimura
@eirinici
Inactive users of Working Group "Paketo" are:
@joshuatcasey
@accrazed
Inactive users of Working Group "App Runtime Interfaces" are:
@cf-frontend
Inactive users of Working Group "App Runtime Platform" are:
@reneighbor

@beyhan
Copy link
Member

beyhan commented Jan 7, 2025

Hi @pivotal-marcela-campo, @georgethebeatle, @davewalter, @Birdrock, @loewenstein-sap, @ForestEckhardt, @dmikusa,

could you please check on the warning above which reports inactive users in your WG.

@beyhan beyhan added the toc label Jan 7, 2025
@beyhan beyhan requested review from a team, rkoster, beyhan, stephanme, ameowlia and ChrisMcGowan and removed request for a team January 7, 2025 12:30
@loewenstein-sap
Copy link
Contributor

Inactive users of Working Group "Paketo" are:
@joshuatcasey
@accrazed

@beyhan They are both listed in https://github.com/cloudfoundry/community/blob/main/toc/working-groups/paketo.md and https://github.com/paketo-buildpacks/community/blob/main/TEAMS.md - what s the criterion for inactivity? If it is the lack of activity in the cloudfoundry org, then it might be just because they are Paketo contributors and their activity would need to be traced in the paketo org...

@ForestEckhardt & @dmikusa WDYT?

@georgethebeatle
Copy link
Member

Hi @pivotal-marcela-campo, @georgethebeatle, @davewalter, @Birdrock, @loewenstein-sap, @ForestEckhardt, @dmikusa,

could you please check on the warning above which reports inactive users in your WG.

I opened a PR to remove the inactive users from the cf-on-k8s working group.

@beyhan
Copy link
Member

beyhan commented Jan 8, 2025

Inactive users of Working Group "Paketo" are:
@joshuatcasey
@accrazed

@beyhan They are both listed in https://github.com/cloudfoundry/community/blob/main/toc/working-groups/paketo.md and https://github.com/paketo-buildpacks/community/blob/main/TEAMS.md - what s the criterion for inactivity? If it is the lack of activity in the cloudfoundry org, then it might be just because they are Paketo contributors and their activity would need to be traced in the paketo org...

@ForestEckhardt & @dmikusa WDYT?

Hi @loewenstein-sap,

yes, the activity is checked based on the cloudfoundry org for users listed in https://github.com/cloudfoundry/community/blob/main/toc/working-groups/paketo.md. We still have an open action item to extend the TOC automation for multiple Github orgs but not yet implemented. That means, you can ignore this for now until we have extended the automation and then you could decide whether you want to join with the Paketo org. Sorry, for the false positive alert :-).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

3 participants