search

kubernetes / community

Kubernetes community content
Apache License 2.0
12.02k stars 5.17k forks source link

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

Open lavalamp opened 6 years ago

lavalamp commented 6 years ago

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?

lavalamp commented 6 years ago

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

cblecker commented 6 years ago

/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

fejta-bot commented 6 years ago

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

justaugustus commented 6 years ago

/remove-lifecycle stale

spiffxp commented 6 years ago

/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.

justaugustus commented 6 years ago

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

fejta-bot commented 5 years ago

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

idealhack commented 5 years ago

/remove-lifecycle stale

nikhita commented 5 years ago

/kind bug /priority important-soon

xref https://github.com/kubernetes/steering/issues/36

spiffxp commented 5 years ago

/assign ref: https://github.com/kubernetes/community/issues/1808 for owners management

spiffxp commented 5 years ago

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

fejta-bot commented 5 years ago

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

McCoyAle commented 5 years ago

/remove-lifecycle stale /lifecycle frozen

Due to important long term label.

mrbobbytables commented 4 years ago

/committee steering This is similar to https://github.com/kubernetes/community/issues/4125 - should this be rolled into the annual sig/wg checks?

liggitt commented 2 years ago

/assign (from 12/6 Steering public meeting)

dims commented 2 years ago

see new tool for ensuring urls are still valid ( https://github.com/kubernetes/community/issues/4125#issuecomment-1000412060 )

dims commented 2 years ago

related https://github.com/kubernetes/community/issues/6307

parispittman commented 2 years ago

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 commented 1 year ago

/assign @palnabarun