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

Document process for User Groups formation #92

Closed
nikhita opened this issue Feb 27, 2019 · 18 comments
Closed

Document process for User Groups formation #92

nikhita opened this issue Feb 27, 2019 · 18 comments
Assignees
Labels
committee/steering Denotes an issue or PR intended to be handled by the steering committee. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@nikhita
Copy link
Member

nikhita commented Feb 27, 2019

Ref: kubernetes/community#3299 (comment)

User Groups were added as a community group in kubernetes/community#3174. Given that we are also adding a usergroups field to sigs.yaml (kubernetes/community#3298), it would be good to have processes defined and documented for formation of User Groups.

The doc should go here: https://github.com/kubernetes/community/tree/master/committee-steering/governance

/committee steering

@k8s-ci-robot k8s-ci-robot added the committee/steering Denotes an issue or PR intended to be handled by the steering committee. label Feb 27, 2019
@timothysc timothysc added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Mar 11, 2019
@timothysc timothysc added this to the April 2019 milestone Mar 11, 2019
@timothysc
Copy link
Member

Is there anything else we need todo here?

@timothysc timothysc self-assigned this Mar 11, 2019
@timothysc timothysc added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Mar 11, 2019
@nikhita
Copy link
Member Author

nikhita commented Mar 12, 2019

Is there anything else we need todo here?

Yes, we need a governance doc for User Groups - just like we have for SIGs and WGs in https://github.com/kubernetes/community/tree/master/committee-steering/governance.

Basically, a doc outlining the different roles in a User Group (leads, chairs?), creation and retirement process.

@nikhita
Copy link
Member Author

nikhita commented Mar 12, 2019

Oh, I just noticed the help wanted label on this.

I'm happy to help move this forward given that we are in the process of adding a new user group (kubernetes/community#3304) but I think the doc needs to come from steering and I'm not sure how anyone non-steering can help? 🤔

@timothysc timothysc assigned pwittrock and unassigned timothysc Mar 13, 2019
@timothysc timothysc removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Mar 13, 2019
@timothysc
Copy link
Member

@pwittrock - thx for helping out here.

@timothysc
Copy link
Member

@jbeda - could you outline your thoughts here?

@jbeda
Copy link
Contributor

jbeda commented Mar 13, 2019

Haha -- not sure I can own this but I do see a certain level of overlap here between User Groups (from a governance point of view) and geographic based meetups. There is a community with leaders and standards. In return they get to use the Kubernetes name.

We should perhaps look to join the streams here and leverage any work that is being done around CNCF chartered meetups.

@parispittman @idvoretskyi Do you have thoughts/details?

@jberkus
Copy link
Contributor

jberkus commented Mar 19, 2019

@jbeda: CNCF uses Meetup.com for meetup groups. They really don't provide any support, or do any work, aside from that, except for periodic pizza sponsorship. Meetup.com is not an adaptable or customizable platform, so it wouldn't be suitable for UGs.

@idvoretskyi
Copy link
Member

@jberkus we do provide much wider support for the Meetup groups except for the periodic pizza sponsorship (we may chat about that independently from this case if you have any concerns), but in general you are right - meetup.com is not a platform that was designed for UG use cases.

@timothysc timothysc added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Mar 27, 2019
@timothysc
Copy link
Member

AI: @pwittrock will send out an email soliciting folks from the community to help draft a document and timeout in a couple of weeks if no one steps up.

@pwittrock
Copy link
Member

@daminisatya will lead and I will support.

@surajnarwade
Copy link

surajnarwade commented Mar 29, 2019

@timothysc, @pwittrock , @dims
I would like to help also :)

@oicheryl
Copy link

I'd also like to be in the loop as I run the CNCF End User Community (https://www.cncf.io/people/end-user-community/) and the groups under it.

@daminisatya
Copy link
Contributor

Hello All!

@pwittrock Helped me get started and I'm actively working on defining the structure for UGs governance ( done with defining creation and deletion of UGs) Will keep you posted on this thread! ✨

@pwittrock
Copy link
Member

FYI, we have a draft out that will be published in the next day or 2

@daminisatya
Copy link
Contributor

Some last-minute hiccup and will be opening a PR by Tuesday morning (PST) 😄

@d-nishi
Copy link

d-nishi commented Apr 19, 2019

@daminisatya -- can you keep me linked to this thread please? Cheers!

@daminisatya
Copy link
Contributor

@d-nishi You can check the PR, I referenced here!

@michelleN
Copy link

documentation PR merged. Thanks @daminisatya

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
committee/steering Denotes an issue or PR intended to be handled by the steering committee. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests