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.

Sign up for GitHub

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

Jump to bottom

Document what working groups are, and how to form and disband #27

Closed
bgrant0607 opened this issue Mar 29, 2018 · 15 comments
Closed

Document what working groups are, and how to form and disband #27

bgrant0607 opened this issue Mar 29, 2018 · 15 comments
Assignees
@jbeda @spiffxp @jdumars @michelleN @brendandburns @derekwaynecarr
Labels
committee/steering Denotes an issue or PR intended to be handled by the steering committee. 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
May 2019

Comments

@bgrant0607
Copy link
Member

bgrant0607 commented Mar 29, 2018 •
edited by pwittrock
Loading

  • Update docs to describe relationship with SIGs
@cblecker cblecker mentioned this issue Mar 29, 2018
Merged
@jdumars jdumars self-assigned this Jun 24, 2018
@jdumars jdumars added the committee/steering Denotes an issue or PR intended to be handled by the steering committee. label Jun 24, 2018
@jdumars
Copy link
Member

jdumars commented Jun 24, 2018

WIP: https://docs.google.com/document/d/1AlI89KijzO9_KAqUX_pbumgld1LN0tte2FMdjLw83wY/edit

Please comment.

@jdumars jdumars mentioned this issue Jun 24, 2018
Closed
@jdumars
Copy link
Member

jdumars commented Jun 27, 2018

Corollary is to get this merged for more clarification on how WGs fit into the ecosystem:

kubernetes/community#2173

@spiffxp
Copy link
Member

spiffxp commented Jul 18, 2018

/assign @philips @derekwaynecarr @spiffxp

Discussed during 2018-07-18 meeting, the four of us will work to review and push into a PR to be merged by next steering meeting

@spiffxp
Copy link
Member

spiffxp commented Jul 18, 2018

/unassign @philips
/assign @jbeda
got my wires crossed

@k8s-ci-robot k8s-ci-robot assigned jbeda and unassigned philips Jul 18, 2018
@jdumars
Copy link
Member

jdumars commented Jul 19, 2018 •
edited
Loading

As a follow-up, we probably need to fix existing incorrectly classified WGs, etc. per this: https://groups.google.com/a/kubernetes.io/d/msg/steering/zEY93Swa_Ss/C0ziwjkGCQAJ&sa=D&ust=1532010011381000&usg=AFQjCNGbTyXk1IeMristsoaqKIo5t-OFiA

@jdumars
Copy link
Member

jdumars commented Jul 24, 2018

Discussed 20180718: https://youtu.be/I6BwkOA9dn4?t=42m56s

@spiffxp
Copy link
Member

spiffxp commented Jul 27, 2018

Merged kubernetes/community#2173

@spiffxp
Copy link
Member

spiffxp commented Aug 1, 2018

/assign @brendandburns

@spiffxp
Copy link
Member

spiffxp commented Aug 15, 2018

This remains undone, I can tackle PR'ing this later this week

@derekwaynecarr
Copy link
Member

@spiffxp please send note when pr is opened and would love to review.

@spiffxp
Copy link
Member

spiffxp commented Sep 26, 2018

ref: kubernetes/community#2702

We appear to have hit a difference of opinion from @brendandburns

@spiffxp spiffxp mentioned this issue Sep 26, 2018
Closed
@spiffxp
Copy link
Member

spiffxp commented Oct 18, 2018

ref: kubernetes/community#2814
ref: kubernetes/community#1994

I'm re-titling this because it seems like scope has grown beyond just creating a working group.

@spiffxp spiffxp changed the title Document how working groups should be formed Document what working groups are, and how to form and disband Oct 18, 2018
@spiffxp spiffxp mentioned this issue Oct 18, 2018
Closed
@spiffxp
Copy link
Member

spiffxp commented Nov 30, 2018

OK, what's keeping this open? AFAICT it's:

@philips
Copy link
Contributor

philips commented Dec 5, 2018

I believe #2766 was addressed @spiffxp so I closed it.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 5, 2019
@timothysc timothysc added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 5, 2019
@timothysc timothysc added this to the April 2019 milestone Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jbeda jbeda

@spiffxp spiffxp

@jdumars jdumars

@michelleN michelleN

@brendandburns brendandburns

@derekwaynecarr derekwaynecarr

Labels
committee/steering Denotes an issue or PR intended to be handled by the steering committee. 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
Milestone
May 2019
Development

No branches or pull requests