@@ -10,17 +10,6 @@ Enhancements provides the basis of a community roadmap. Enhancements may be
1010filed by anyone, but require approval from a maintainer to accept the
1111enhancement into the project.
1212
13- ## Quick start
14-
15- 1 . Create an [ Issue] [ issue ] and select "Enhancement Request".
16- 2 . Follow the instructions in the enhancement request template and submit the
17- Issue.
18- 3 . (depending on size of change) Start a [ draft Gateway Enhancement Proposal
19- (GEP)] [ gep ]
20-
21- [ issue ] : https://github.com/kubernetes-sigs/gateway-api/issues/new/choose
22- [ gep ] : /geps/overview
23-
2413## What is Considered an Enhancement?
2514
2615An enhancement is generally anything that:
@@ -49,6 +38,20 @@ Create an enhancement once you have:
4938- Enhancements may take several releases to complete.
5039- A prototype in your own fork (optional)
5140
41+ ## How to Create a New Enhancement
42+
43+ Once you've circulated your idea and received feedback from the maintainers
44+ that creating a [ Gateway Enhancement Proposal (GEP)] [ gep ] is a good next step:
45+
46+ - create an [ Issue] [ issue ] and select "Enhancement Request"
47+ - follow the instructions in the enhancement request template and submit the
48+ Issue.
49+ - create an initial pull request to add your GEP. Follow the directions in the
50+ [ GEP documentation] [ gep ] .
51+
52+ [ issue ] : https://github.com/kubernetes-sigs/gateway-api/issues/new/choose
53+ [ gep ] : /geps/overview
54+
5255## Why are Enhancements Tracked
5356
5457As the project evolves, it's important that the community understands how the
0 commit comments