forked from openshift/enhancements
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
59f181e
commit aece257
Showing
2 changed files
with
14 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,39 +1,34 @@ | ||
# OKD Enhancement Proposals | ||
|
||
An OKD Enhancement Proposal is a way to propose, communicate, and coordinate on | ||
new efforts for the OKD project. | ||
An OKD Enhancement Proposal is a way to propose, communicate, and coordinate on new efforts for the OKD project. | ||
|
||
It is inspired from our experience with the Kubernetes Enhancement process where | ||
many of our community participants collaborate each day. | ||
It is inspired from our experience with the Kubernetes Enhancement process where many of our community participants collaborate each day. | ||
|
||
This process is evolving, but is mandatory for all enhancements beginning with | ||
release-4.3. | ||
This process is evolving, but is mandatory for all enhancements beginning with release-4.3. | ||
|
||
## Quick start | ||
|
||
1. Socialize an idea with others. Make sure others think the work is worth | ||
doing, and are willing to review design and code changes required. | ||
2. Follow the process outlined in the [enhancement | ||
template](template.md). | ||
1. Socialize an idea with others. Make sure others think the work is worth doing, and are willing to review design and code changes required. | ||
2. Follow the process outlined in the [enhancement template](template.md). | ||
|
||
## FAQs | ||
|
||
### Do I have to use the process? | ||
|
||
If the enhancement has broad scope, yes. It helps everyone track why, when, | ||
how, and by whom work is done. | ||
If the enhancement has broad scope, yes. It helps everyone track why, when, how, and by whom work is done. | ||
|
||
### Why would I want to use the process? | ||
|
||
Provide a mechanism to communicate design and implementation strategies across | ||
the OKD community. | ||
Provide a mechanism to communicate design and implementation strategies across the OKD community. | ||
|
||
### Do I put design in a particular directory? | ||
|
||
If it has broad impact, place it in the root of this directory. If it's | ||
localized to a particular domain, find the appropriate directory. | ||
If it has broad impact, place it in the root of this directory. If it's localized to a particular domain, find the appropriate directory. | ||
|
||
### Do I have to use the Oxford comma? | ||
|
||
Yes. OKD is an open, inclusive, and diverse community, and there is absolutely no room for ambiguous clauses. | ||
|
||
### My FAQ isn't answered here! | ||
|
||
Open an issue and ask or even better open a PR with a question and proposed | ||
answer. | ||
Open an issue and ask or even better open a PR with a question and proposed answer. |