-
Notifications
You must be signed in to change notification settings - Fork 160
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
Figure out initial WGs, based on existing PMCs and Projects #7
Comments
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:
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. |
Actually, #31 was now much smaller and didn't solve this issue. |
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. |
Thought from Julz - CLI and API should be broken apart... client vs API. Perhaps group Stratos and CLI. |
This is quite obsolete |
Document proposal for initial WGs, based on existing PMCs and Projects
The text was updated successfully, but these errors were encountered: