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

Make KEPS transparent #1673

Closed
jberkus opened this issue Apr 8, 2020 · 13 comments
Closed

Make KEPS transparent #1673

jberkus opened this issue Apr 8, 2020 · 13 comments
Assignees
@justaugustus
Labels
area/enhancements Issues or PRs related to the Enhancements subproject lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. 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
keps-beta

Comments

@jberkus
Copy link
Contributor

jberkus commented Apr 8, 2020

Enhancement Description

  • One-line enhancement description (can be used as a release note): Make KEPS transparent so that all involved contributors can easily determine contents and status of currently active KEPS.
  • Kubernetes Enhancement Proposal: N/A
  • Primary contact (assignee): TBD
  • Responsible SIGs: SIG-PM
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y) TBD
    • Beta release target (x.y) TBD
    • Stable release target (x.y) TBD

Currently it is challenging for any contributor not deeply involved with this repository to find useful information about current KEPS. Since we've passed through the phase of figuring out a basic structure of KEPS, it's perhaps time to look at how to make them an easy-to-use tool.

Rather than specific technology goals, I define "transparency" as having some easy way to answer the following questions, all of which currently require either prior knowledge or substantial research to answer:

  1. SIG Lead: what are the current active KEPs in my SIG, what are their statuses, and which ones are making/missing timelines?
  2. New contributor: I'd like to work on proposed feature X. What KEPS in any SIG touch on, or even subsume, this feature?
  3. Reviewer: How do I find issues and PRs that are blocking any current KEPs so that I can move them along?
  4. ContribEx: How do I find the latest KEPs so that I can promote them for review/commentary?
  5. Release Team: Which KEPs have deliverables for this release, and what is the status of those deliverables?

All of these questions should become the matter of a few clicks in a sufficiently automated system. Making them answerable requires solving two major problems:

  1. Deploying a web app or other technology that surfaces KEPs in a multi-dimensional, searchable way.
  2. Making it easy and speedy enough to update KEPs -- fully automated with some information -- so that the information in them is reasonably up-to-date.
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 8, 2020
@jberkus
Copy link
Contributor Author

jberkus commented Apr 8, 2020

/sig pm
/assign @justaugustus

@k8s-ci-robot k8s-ci-robot added sig/pm and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 8, 2020
@justaugustus justaugustus added this to the keps-beta milestone Apr 8, 2020
@christopherhein
Copy link
Member

I'd hope some of these can be answered by the work on the contributor site. Based on the subsections on the side it looks like it could be? https://stupefied-goodall-e282f7.netlify.com/

KEP: https://github.com/kubernetes/enhancements/blob/master/keps/sig-contributor-experience/0005-contributor-site.md
Project: https://github.com/kubernetes-sigs/contributor-site

Is that right @mrbobbytables, @castrojo?

@mrbobbytables
Copy link
Member

Right now it's somewhat TBD whether they will be a part of the contributor site, or on their own with something similar to our release docs:
ref: kubernetes-sigs/release-notes#140
ref: https://deploy-preview-140--kubernetes-sigs-release-notes.netlify.com/

There has been a long history involved with trying to surface them better, but there has been numerous issues (#617 (comment)).

With some of the changes planned for KEPs (ref: #1545) this should become easier in the future.

@jberkus
Copy link
Contributor Author

jberkus commented Apr 13, 2020

@christopherhein that's a good example of the opposite of what I'm talking about.

Take that sample site, and try to answer the 5 questions I pose above using it.

@justaugustus justaugustus added area/enhancements Issues or PRs related to the Enhancements subproject and removed sig/pm labels Apr 16, 2020
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 16, 2020
@justaugustus justaugustus added the sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. label Apr 16, 2020
@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 16, 2020
@palnabarun palnabarun 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 May 3, 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-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 Aug 1, 2020
@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 Aug 31, 2020
@palnabarun
Copy link
Member

/remove-lifecycle rotten

@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 Sep 1, 2020
Closed
4 tasks
@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 Nov 30, 2020
@jberkus
Copy link
Contributor Author

jberkus commented Dec 2, 2020

/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 2, 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 Mar 2, 2021
@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-contributor-experience at kubernetes/community.
/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 Apr 1, 2021
@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-contributor-experience at kubernetes/community.
/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-contributor-experience at kubernetes/community.
/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.

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

@justaugustus justaugustus

Labels
area/enhancements Issues or PRs related to the Enhancements subproject lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. 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
Milestone
keps-beta
Development

No branches or pull requests
7 participants
@jberkus @christopherhein @justaugustus @mrbobbytables @palnabarun @k8s-ci-robot @fejta-bot