Figure out initial WGs, based on existing PMCs and Projects about community

[loewenstein]

Should we get to a list of WGs here or directly on a PR?

As a general question, should we try the most basic mapping, which is either PMC ~ WG or project ~ WG? The former might be too coarse grained and too close to "we just renamed PMC to WG. The latter might be too fine grained.

I could see the following, but don't have a list of projects at hand currently:

• Application Runtime (or Container Scheduling)
  • Garden
  • Diego
  • Eirini
  • Windows container
• Security
  • UAA
• Networking
  • Gorouter
  • cf-k8s-networking
• Release Engineering/Integration
  • cf-deployment
  • cf-for-k8s
• API
  • capi
  • cf cli?

There's already some open questions like mTLS, which is done in cf-k8s-networking, but a Security WG would probably want to be involved, although UAA project members don't seem to be the ones particularly interested.

[loewenstein]

Actually, #31 was now much smaller and didn't solve this issue.

[chipchilders]

We need to create a rough straw proposal, perhaps just using the example from above, in order to help people understand the ideas being expressed. Should also have a clear statement that this is a rough idea and the initial TOC will need to work with the community to set the full initial schedule.

[chipchilders]

Thought from Julz - CLI and API should be broken apart... client vs API. Perhaps group Stratos and CLI.

[loewenstein]

This is quite obsolete