The app-autoscaler-ci repo is also included in the ARI working group charter:

@silvestre can you amend this PR to also remove that repo from the charter?

Per RFC-0007, the process to remove it is as follows:

A Working Group wants to cease maintaining a repository that it currently owns.

• The Working Group MUST approve the removal of the repository from the set of repositories that it owns.
• The TOC MUST approve the removal of the repository from the Working Group.
• In addition, the TOC MUST decide whether to archive the repository or to arrange for another Working Group to own it instead (possibly a newly formed one, if appropriate and if supported by community contributors).
• Note: In this case, it is unlikely that either the TOC or the CFF staff should own this repository, as it was already owned by some Working Group in the CF community.

In my role as lead for the ARI Working Group, I approve removing cloudfoundry/app-autoscaler-ci from the charter and archiving both cloudfoundry/app-autoscaler-ci and cloudfoundry/app-autoscaler-ui.

Now we need approval from @cloudfoundry/toc.

In addition, remove cloudfoundry/app-autoscaler-ci from the ARI working group charter.

Done.

For completeness sake, I also removed the already archived app-autoscaler repo (also merged into app-autoscaler-release) from the charter:

@Gerg and @cloudfoundry/toc: Would you please also approve removing cloudfoundry/app-autoscaler from the ARI WG charter?

@emalm for PRs like this, do we need unanimous TOC approval? or majority?

@Gerg Should be the same as any other TOC decision: generally we want TOC consensus, which concretely manifests as at least approvals from a quorum of TOC members without any objections (within a reasonable time period).