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

Subprojects in sigs.yaml will be instantly out of date #1913

Open
lavalamp opened this issue Mar 8, 2018 · 19 comments
Open

Subprojects in sigs.yaml will be instantly out of date #1913

lavalamp opened this issue Mar 8, 2018 · 19 comments
Assignees
@spiffxp @liggitt @palnabarun
Labels
area/github-management Issues or PRs related to GitHub Management subproject committee/steering Denotes an issue or PR intended to be handled by the steering committee. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Projects
ContribEx: github-management subproject committee-steering
Milestone
v1.27

Comments

@lavalamp
Copy link
Member

lavalamp commented Mar 8, 2018

Anytime anyone moves a directory, the entry in sigs.yaml will suddenly be wrong.

Wouldn't it make more sense for OWNERS files to instead declare the owning sig and subproject, and then we generate sigs.yaml from that?
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 8, 2018
@lavalamp
Copy link
Member Author

lavalamp commented Mar 8, 2018 •
edited

Not sure who to tag-- maybe @spiffxp ? @cblecker?

@cblecker
Copy link
Member

cblecker commented Mar 8, 2018

/sig contributor-experience

yeah, there are some updates that are going to have to be made to the generator to accommodate the new structures in https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance-template-short.md

@k8s-ci-robot k8s-ci-robot added sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 8, 2018
@lavalamp lavalamp mentioned this issue Mar 8, 2018
Merged
@bgrant0607 bgrant0607 mentioned this issue Apr 20, 2018
Closed
@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 Jun 6, 2018
@justaugustus
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 7, 2018
@spiffxp
Copy link
Member

spiffxp commented Aug 3, 2018

/area github-management

Yeah I agree until there's a single source of truth this is going to be perpetually stale. It started in sigs.yaml because it's easier to try and change everything in one place while getting started.

@k8s-ci-robot k8s-ci-robot added the area/github-management Issues or PRs related to GitHub Management subproject label Aug 3, 2018
@justaugustus justaugustus mentioned this issue Sep 30, 2018
Closed
@justaugustus
Copy link
Member

@lavalamp @spiffxp -- I have a PR up that allows you to specify subproject by repo, instead of specifically with an OWNERS file.

@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 Dec 29, 2018
@idealhack
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 31, 2018
@nikhita
Copy link
Member

nikhita commented Mar 18, 2019

/kind bug
/priority important-soon

xref kubernetes/steering#36

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Mar 18, 2019
@nikhita nikhita added this to To do in ContribEx: github-management subproject via automation Mar 19, 2019
@nikhita nikhita moved this from Backlog to Blocked in ContribEx: github-management subproject Mar 20, 2019
@spiffxp
Copy link
Member

spiffxp commented May 15, 2019

/assign
ref: #1808 for owners management

@spiffxp spiffxp moved this from Blocked to Backlog in ContribEx: github-management subproject Jul 24, 2019
@spiffxp
Copy link
Member

spiffxp commented Jul 24, 2019

/remove-priority important-soon
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jul 24, 2019
@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 Oct 22, 2019
@McCoyAle
Copy link

McCoyAle commented Nov 7, 2019

/remove-lifecycle stale
/lifecycle frozen

Due to important long term label.

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 7, 2019
@mrbobbytables mrbobbytables added this to the Next milestone Mar 10, 2020
@mrbobbytables
Copy link
Member

/committee steering
This is similar to #4125 - should this be rolled into the annual sig/wg checks?

@k8s-ci-robot k8s-ci-robot added the committee/steering Denotes an issue or PR intended to be handled by the steering committee. label Oct 7, 2020
@ehashman ehashman mentioned this issue Sep 14, 2021
Closed
@justaugustus justaugustus added this to Inbox (unprioritized) in committee-steering Nov 9, 2021
@liggitt
Copy link
Member

liggitt commented Dec 6, 2021 •
edited

/assign
(from 12/6 Steering public meeting)

@justaugustus justaugustus moved this from Inbox (unprioritized) to Backlog (prioritized) in committee-steering Dec 6, 2021
@mrbobbytables mrbobbytables mentioned this issue Dec 12, 2021
Closed
@dims
Copy link
Member

dims commented Dec 23, 2021

see new tool for ensuring urls are still valid ( #4125 (comment) )

@dims
Copy link
Member

dims commented Dec 23, 2021

related #6307

@dims dims mentioned this issue Dec 23, 2021
Open
@parispittman
Copy link
Contributor

with the annual report checks and the new tool above that dims linked, @lavalamp do you think we are in a better place now and ok to close this?

@mrbobbytables
Copy link
Member

/assign @palnabarun

@mrbobbytables mrbobbytables modified the milestones: Next, v1.27 Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spiffxp spiffxp

@liggitt liggitt

@palnabarun palnabarun

Labels
area/github-management Issues or PRs related to GitHub Management subproject committee/steering Denotes an issue or PR intended to be handled by the steering committee. kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience.
Projects
ContribEx: github-management subproject
  
To Triage
[SIG ContribEx] Overview
Status: No status
committee-steering
  
Backlog (prioritized)
Milestone
v1.27
Development

No branches or pull requests