Community: Perform survey of KEPs and identify those needing update to directory format

[justaugustus]

Work item for https://github.com/kubernetes/features/issues/617

/kind feature
/sig pm
/milestone v1.13
/assign @calebamiles

[fejta-bot]

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

[nikhita]

/remove-lifecycle stale

[fejta-bot]

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

[fejta-bot]

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

[nikhita]

@justaugustus :wave: Just wanted to bump this again, and check what's remaining here and if this can be closed?

[fejta-bot]

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]

@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]

/remove-lifecycle rotten
/reopen

[k8s-ci-robot]

@justaugustus: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

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]

/priority important-longterm
/milestone keps-beta

[k8s-ci-robot]

@justaugustus: The provided milestone is not valid for this repository. Milestones in this repository: [August, Next]

Use /milestone clear to clear the milestone.

In response to this:

/priority important-longterm
/milestone keps-beta

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.

[fejta-bot]

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

[savitharaghunathan]

Hi @justaugustus/ @calebamiles, I am a part of sig-contribex-triage team and wanted to check if either of you have any updates on this issue? Thanks! :)

[fejta-bot]

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

[mrbobbytables]

/remove-lifecycle rotten
Hoping to tackle this between the 1.18 and 1.19 release next year.
/assign

[fejta-bot]

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

[mrbobbytables]

/remove-lifecycle stale

The ongoing discussion for this is happening in this PR to update 617
https://github.com/kubernetes/enhancements/pull/1545

[justaugustus]

/remove-sig pm
/sig architecture
/area enhancements
/assign
/unassign @calebamiles

[fejta-bot]

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

[mrbobbytables]

/remove-lifecycle stale
This has become the standard, do we want to leave this open till all of them are converted?

[justaugustus]

/unassign @mrbobbytables @justaugustus
/assign @kikisdeliveryservice
ref: https://kubernetes.slack.com/archives/C2C40FMNF/p1601408420103200?thread_ts=1601403539.085300&cid=C2C40FMNF

[mrbobbytables]

@justaugustus @kikisdeliveryservice @LappleApple
Do you think we should move this issue from here to k/enhancements?

[LappleApple]

It's in progress as part of the 1.20 release team work, so I don't think so...

[jeremyrickard]

/retitle Perform survey of KEPs and identify those needing update to directory format

[fejta-bot]

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-contributor-experience at kubernetes/community.
/lifecycle stale

[kikisdeliveryservice]

/remove-lifecycle-stale

[kikisdeliveryservice]

I feel that this is mostly done and tracked by the issue here: https://github.com/kubernetes/enhancements/issues/2220

I can formally go thru the sub-dirs to get status but on a quick perusal this is very close to done.

[mrbobbytables]

I think this is safe to close, the activity has been happening in k/enhancements.

[mrbobbytables]

I went through the subdirs, everything is good 🎉
/pony party
/close

[k8s-ci-robot]

@mrbobbytables:

In response to this:

I went through the subdirs, everything is good 🎉
/pony party
/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.

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

I went through the subdirs, everything is good 🎉
/pony party
/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.