-
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
Add a description of user groups. #3174
Conversation
/uncc @parispittman @castrojo |
governance.md
Outdated
Some topics have long term relevance to large groups of Kubernetes users, but | ||
do not have clear deliverables or ownership of parts of the Kubernetes | ||
code base. As such they are neither good fits for SIGs or Working Groups. | ||
Examples of such a topic might be continuous delivery to Kubernetes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An example
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
|
||
User groups function as a centralized resource to facilitate communication | ||
and discovery of information related to the topic of the user group. User | ||
groups should not undertake to produce any deliverable, instead they should |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've thought in the past that it would be useful for such groups to convey requirements or friction for their use case to the relevant SIGs. That could be as simple as filing bugs or SIG presentations, but I could see cases where docs might be useful. These don't necessarily need to live within the project, though.
So, perhaps encourage engagement with SIGs for issues that don't rise to the level of requiring a WG.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some text that tries to capture this.
governance.md
Outdated
they shouldn't take ownership of anything in the Kubernetes process, as | ||
that is a role for SIGs. | ||
|
||
User groups are documented in [sigs.yaml](sigs.yaml) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in order to facilitate discoverability and engagement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
Thanks for the review! Comments addressed, please re-check. |
Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bgrant0607, brendandburns The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@bgrant0607 @spiffxp @smarterclayton
As discussed in steering committee...