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.

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

Refine existing KEP Documentation #2088

Closed
justaugustus opened this issue Sep 29, 2018 · 21 comments
Closed

Refine existing KEP Documentation #2088

justaugustus opened this issue Sep 29, 2018 · 21 comments
Assignees
Labels
area/enhancements Issues or PRs related to the Enhancements subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Milestone

Comments

@justaugustus
Copy link
Member

  • Define KEP DACI (who is responsible for KEPs, both in process and execution)
  • Glossary of terms (enhancement, KEP, feature, etc.)
    • KEP Workflow
    • KEP states
      • Entry / exit criteria

Work item for #617

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

@justaugustus
Copy link
Member Author

/assign @jdumars

@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

@nikhita
Copy link
Member

nikhita commented Dec 28, 2018

/remove-lifecycle stale

@lachie83
Copy link
Member

Created #898 to define KEP DACI

@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

@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

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

/remove-lifecycle rotten
/lifecycle frozen
/reopen

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/lifecycle frozen
/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.

@k8s-ci-robot k8s-ci-robot reopened this Jan 21, 2020
@justaugustus
Copy link
Member Author

/remove-sig pm
/sig architecture
/area enhancements
/unassign @jdumars

@mrbobbytables
Copy link
Member

/assign @LappleApple
For some additional eyes

I think this can be closed? or at least brought up again in k/enhancements. I don't think it'll get traction/visibility over here.

@lasomethingsomething
Copy link
Contributor

@mrbobbytables I'm not 100% sure -- we've circled this issue a few times recently but haven't come to a definitive yes/no. Should we try in Slack one more time? Would be great if we could determine and resolve there and not have to discuss at a meeting. :)

@justaugustus
Copy link
Member Author

I think this can be closed? or at least brought up again in k/enhancements. I don't think it'll get traction/visibility over here.

@mrbobbytables -- can you forklift the issue over to k/e? I think you're the only one of us with access to do so.

@mrbobbytables
Copy link
Member

I can move it over there 👍

@mrbobbytables mrbobbytables transferred this issue from kubernetes/community Oct 8, 2020
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 8, 2020
@k8s-ci-robot
Copy link
Contributor

@justaugustus: The label(s) sig/pm cannot be applied, because the repository doesn't have them

In response to this:

  • Define KEP DACI (who is responsible for KEPs, both in process and execution)
  • Glossary of terms (enhancement, KEP, feature, etc.)
  • KEP Workflow
  • KEP states
    • Entry / exit criteria

Work item for #617

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

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
Copy link
Contributor

@justaugustus: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21]

Use /milestone clear to clear the milestone.

In response to this:

  • Define KEP DACI (who is responsible for KEPs, both in process and execution)
  • Glossary of terms (enhancement, KEP, feature, etc.)
  • KEP Workflow
  • KEP states
    • Entry / exit criteria

Work item for #617

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

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 added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Oct 8, 2020
@mrbobbytables mrbobbytables added the tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team label Oct 8, 2020
@mrbobbytables
Copy link
Member

/sig architecture

@k8s-ci-robot k8s-ci-robot added sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 8, 2020
@justaugustus justaugustus added this to the keps-beta milestone Oct 8, 2020
@lasomethingsomething
Copy link
Contributor

/area enhancements

@k8s-ci-robot k8s-ci-robot added the area/enhancements Issues or PRs related to the Enhancements subproject label Nov 12, 2020
@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-contributor-experience at kubernetes/community.
/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 Feb 11, 2021
@kikisdeliveryservice
Copy link
Member

Closing this as it's superceded by our Glossary Card:
#2517

and also addressed by: #898

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/enhancements Issues or PRs related to the Enhancements subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Projects
None yet
Development

No branches or pull requests

9 participants