Remove Inactive Users FI WG

[beyhan]

According to the rules for inactivity defined in RFC-0025, 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, 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?

[yharish991]

@beyhan, our team at Broadcom maintains the https://github.com/cloudfoundry/disaster-recovery-acceptance-tests repository. While we don't contribute frequently, we would like to retain access for future purposes.

We use @tas-operability-bot to automate dependency bumps, so we would also like to maintain access for this account.

[nouseforaname]

Hi @beyhan ,

I know I've been inactive for a while after I left Broadcom. I'm currently working on a new cpi for stackit cloud and will soon start creating PRs again.
I don't want to obstruct anything though and could also just request to rejoin down the road. Leaving the decision up to you.

[ichandrabhatta]

Hi @beyhan ,
Can I keep my access please. Github id - @ichandrabhatta. Have been busy with other areas of TAS but like to keep the access for future use.
Thank you very much

[beyhan]

Hi @yharish991, @nouseforaname, @ichandrabhatta,
I would suggest to proceed with this pr and merge it. Afterwards you can just create a pr to get re-added to the same roles as you had by referencing this pr. I will take care to get that one merged. By that you won't be bothered by the automation for the next one year. I think the ask is fair.

[rkoster]

@yharish991 on:

@beyhan, our team at Broadcom maintains the https://github.com/cloudfoundry/disaster-recovery-acceptance-tests repository. While we don't contribute frequently, we would like to retain access for future purposes.

We use @tas-operability-bot to automate dependency bumps, so we would also like to maintain access for this account.

I see no activity from the bot on that repo. Dependency bumps seem to be done by Dependabot.

[beyhan]

please open prs do be re-added as discussed @yharish991, @nouseforaname, @ichandrabhatta