-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
The K8s community SIG-diagram in this repository are outdated and need to be updated #8192
Comments
@LiangquanLi930: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/area community-management |
The new contributor orientation doc has the updated diagram for K8S Community Structure. Maybe utilise the diagram on the doc to replace for the old one, rather than create a new diagram from scratch. |
I can work on the diagram if still needs any help. |
/assign |
I am a new contributer and i would like to design a new image, Can you please send me some guide or resources helping me in creating a new image |
Anyone looking at this should also see the discussion on #8198 Which also discusses tooling. |
Describe the issue
SIG-diagram.png and SIG-diagram.svg were created 3 years ago and are now outdated. The SIG structure of this community has changed since then.
SIGs usability, service-catalog, WGs multitenancy, api-expression,reliability,iot-edge, UGs big-data, vmware-users have been archived.
Missing SIG etcd, WGs batch, device-management, etcd-operator, lts, serving.
It will nice if someone volunteers to create a fresh SIG-diagram of this community.
/sig contributor-experience
/help
The text was updated successfully, but these errors were encountered: