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

Find homes for unowned areas of the project #41

Closed
jdumars opened this issue Jun 25, 2018 · 16 comments
Closed

Find homes for unowned areas of the project #41

jdumars opened this issue Jun 25, 2018 · 16 comments
Assignees
@spiffxp @parispittman
Labels
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. triage/needs-information Indicates an issue needs more information in order to work on it.
Milestone
May 2019

Comments

@jdumars
Copy link
Member

jdumars commented Jun 25, 2018

  • build system (make, bazel, godep, etc.)
  • util libraries
  • Github org/repo management (e.g., dealing with Github changes, consistency across repos, etc.)
  • Node controller
  • kube-controller-manager binary
  • hyperkube
@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 Sep 23, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 23, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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/test-infra repository.

@justaugustus
Copy link
Member

/reopen
/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot reopened this Nov 22, 2018
@k8s-ci-robot
Copy link
Contributor

@justaugustus: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Nov 22, 2018
@justaugustus
Copy link
Member

Sounds like a fair amount of these things could be owned by the to-be-formed Release Engineering subproject, under SIG Release.

@philips
Copy link
Contributor

philips commented Jan 16, 2019

@jdumars how do you think we should work through this list? I don't know where some of these things currently live or who initially created them.

My only hunch is we identify the people who created the thing and ask them what SIG it should belong to and then just start assigning SIGs to own them.

@timothysc timothysc added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. 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 timothysc added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Mar 11, 2019
@timothysc timothysc modified the milestone: May 2019 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

I believe @parispittman mentioned there was a spreadsheet on this one that we can follow up on during next meeting.

@timothysc timothysc added the triage/needs-information Indicates an issue needs more information in order to work on it. label Mar 13, 2019
@timothysc
Copy link
Member

re: Blog - Katlyn will help define policy and sig-docs will own as a sub-project.

@timothysc
Copy link
Member

TODO: Follow up on this issue if we should close it out and open new ones.

@spiffxp
Copy link
Member

spiffxp commented Apr 10, 2019

ref: kubernetes/community#3524 (comment) for the blog

@tpepper
Copy link
Member

tpepper commented Apr 10, 2019

  • build system (make, bazel, godep, etc.)

does feel like a natural thing to try to pull under SIG Release's nascent Release Engineering subproject.

@spiffxp
Copy link
Member

spiffxp commented Apr 10, 2019

@tpepper that was absolutely my intent in pushing for that (although godep is fuzzy and seems more like code org IMO)

@tpepper
Copy link
Member

tpepper commented Apr 11, 2019

Choice of common tool and processes around healthy deps management fall in a broad build/test/release/support flow so will have multiple stakeholder SIGs and WGs imho.

@timothysc
Copy link
Member

https://docs.google.com/spreadsheets/d/1Pmlj5nN_QJ3rRlc-HKOLfRdYY5qCWPMjnNPAdZZ22tg/edit#gid=0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spiffxp spiffxp

@parispittman parispittman

Labels
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. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Milestone
May 2019
Development

No branches or pull requests
9 participants
@philips @spiffxp @timothysc @justaugustus @jdumars @tpepper @parispittman @k8s-ci-robot @fejta-bot