This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
Restructuring the Keptn Enhancement Proposals Repo & Workflow #9082
oleg-nenashev
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
How do future KEPs get raised? As Issues? If so I'm a fan. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all. I would like to change how our KEPs are stored. Right now we have a bunch of open KEP pull requests that include incomplete or never-started ideas. Let's admit most of them will never be completed, but at the same time they still include the valuable knowledge are we would like to preserve in the project. The current approach also confuses users that see a lot of open never-ever KEPs with unclear status. Especially things like GitOps Operator and Authorization support that are highly anticipated but nobody actively works on.
I would like to change the approach to KEP management, and basically adopt what we did in Jenkins instead of the OpenTelemetry pattern. See this repo for the listing.
NOTE: The KEP decision making process is outside the scope of this discussion for now, I focus only on the structure
Suggested changes
References
Beta Was this translation helpful? Give feedback.
All reactions