Updating the Concourse WG charter to enable automated user management

[taylorsilva]

• Tagged the "Roles & Technical Assets" block as YAML so CFF automation can pick it up
• Updated the list of repositories that are archived and sorted the existing list
• Added our bots to the bots section

TODO's and Questions before merging

• Update team auth - It is my understanding that all existing teams will be removed and only CFF managed teams will remain in the org. We will need to ensure our CI auth is updated to point to the new teams: https://github.com/concourse/ci/tree/master/teams
• What is the naming format for CFF generated teams? Is it still the format defined here: https://github.com/cloudfoundry/community/blob/e9bd3cb51f8e7a5b0259088ba0efcfb777fac01d/toc/rfc/rfc-0014-github-teams-and-access.md
  • Name of the groups would then be:
    • wg-concourse-leads
    • wg-concourse-bots
    • wg-concourse-core-[approvers/reviewers]
• We have these bots in our org, do we still need them?
  • https://github.com/vmwclabot
  • https://github.com/vmwghbot

[taylorsilva]

@beyhan I'm mostly looking for confirmation that the team names are what I expect them to be. Once that item is cleared and I merge concourse/ci#430, this PR can then be merged.

[beyhan]

@taylorsilva to my knowledge yes, but @stephanme could you please confirm this.

[stephanme]

In addition, I have to add the concourse github org to the managed orgs in python coding and to orgs.yml.

Ideally, this PR and the changes to orgs.yml + python coding are merged atomically after reviewing the resulting orgs.out.yml (= the input file for peribolos which does the heavy lifting).

I will prepare the changes in the org automation.

[stephanme]

The team names will be:

• wg-concourse (includes all leads and approvers)
• wg-concourse-leads
• wg-concourse-bots
• wg-concourse-core-[approvers/reviewers]

(final prove is the output file of the org automation)

[stephanme]

The PR validation fails now because the concourse org is not yet onboarded as "managed org".

I prepared the necessary changes in #1545 and copied the the yaml block of the Concourse WG charter.

Next steps:

• I'm currently validating a workflow (Dump Github Organization Settings) in the cloudfoundry org because it didn't run for very long time.
• You need to install the "CF Foundation Community Automation" github app in your org and grant it the following permissions to all repos (these are the permissions granted in the cloudfoundry org):
  • Read access to metadata
  • Read and write access to administration, checks, code, commit statuses, environments, issues, members, organization administration, organization user blocking, and pull requests
  • Admin access to organization projects and repository projects
• I will adapt the Dump Github Organization Settings workflow to export the concourse org and run it. It creates a PR that contains the repo list needed for orgs.yaml. If it succeeds we also know that the github app is properly configured and authorization works.
• I will manually run the org automation Python program and copy the resulting org and branchprotection output for concourse into Add concourse github org to org automation #1545 for a final review.
• Finally, you and TOC approves Add concourse github org to org automation #1545, it gets merged and we will see what happens. Expectation is that the teams are created, repo access is managed by those teams and that the branchprotection is configured for all repos.
• Cleanup: archive unmanaged repos (repos in the concourse org that are not listed in your WG charter), delete any direct repo access (bypassing the teams created by the org automation).