Skip to content
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

Merged
merged 2 commits into from
Jan 31, 2019

Conversation

brendandburns
Copy link
Contributor

@bgrant0607 @spiffxp @smarterclayton

As discussed in steering committee...

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jan 30, 2019
@cblecker
Copy link
Member

/uncc @parispittman @castrojo
/cc @kubernetes/steering-committee

@k8s-ci-robot k8s-ci-robot requested review from a team and removed request for castrojo and parispittman January 31, 2019 00:36
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An example

Copy link
Contributor Author

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
Copy link
Member

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.

Copy link
Contributor Author

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)
Copy link
Member

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@brendandburns
Copy link
Contributor Author

Thanks for the review!

Comments addressed, please re-check.

@bgrant0607
Copy link
Member

Thanks!
/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 31, 2019
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2019
@k8s-ci-robot k8s-ci-robot merged commit e123c62 into kubernetes:master Jan 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants