Merge pull request #1531 from jbeda/kep-update

Automatic merge from submit-queue.

Move KEPs to top level directory

contributors/design-proposals/architecture/OWNERS

@@ -1,6 +1,8 @@
 reviewers:
   - sig-architecture-leads
+  - jbeda
 approvers:
   - sig-architecture-leads
+  - jbeda
 labels:
   - sig/architecture

keps/0000-kep-template.md

@@ -58,7 +58,6 @@ See the KEP process for details on each of these items.
 A table of contents is helpful for quickly jumping to sections of a KEP and for highlighting any additional information provided beyond the standard KEP template.
 [Tools for generating][] a table of contents from markdown are available.
 
-
 * [Table of Contents](#table-of-contents)
 * [Summary](#summary)
 * [Motivation](#motivation)
@@ -69,13 +68,12 @@ A table of contents is helpful for quickly jumping to sections of a KEP and for
       * [Story 1](#story-1)
       * [Story 2](#story-2)
     * [Implementation Details/Notes/Constraints [optional]](#implementation-detailsnotesconstraints-optional)
-    * [Security Considerations](#security-considerations)
+    * [Risks and Mitigations](#risks-and-mitigations)
 * [Graduation Criteria](#graduation-criteria)
 * [Implementation History](#implementation-history)
 * [Drawbacks [optional]](#drawbacks-optional)
 * [Alternatives [optional]](#alternatives-optional)
 
-
 [Tools for generating]: https://github.com/ekalinin/github-markdown-toc
 
 ## Summary
@@ -125,9 +123,11 @@ What are some important details that didn't come across above.
 Go in to as much detail as necessary here.
 This might be a good place to talk about core concepts and how they releate.
 
-### Security Considerations
+### Risks and Mitigations
 
-Make sure that you consider the impact of this feature from the point of view of Security.
+What are the risks of this proposal and how do we mitigate.
+Think broadly.
+For example, consider both security security and how this will impact the larger kubernetes ecosystem.
 
 ## Graduation Criteria
 

keps/OWNERS

@@ -0,0 +1,8 @@
+reviewers:
+  - sig-architecture-leads
+  - jbeda
+approvers:
+  - sig-architecture-leads
+  - jbeda
+labels:
+  - sig/architecture

keps/README.md

@@ -0,0 +1,19 @@
+# Kubernetes Enhancement Proposals (KEPs)
+
+This directory contains both the template and process for KEPs.
+
+This process is still in an _alpha_ state and is opt-in for those that want to provide feedback for the process.
+
+## Directory structure
+
+Most KEPs will be sponsored out of a specific SIG.  Those can be incubated inside of a subdirectory here for that SIG.  SIGs can add those directories and OWNERs files on an as needed basis.
+
+Any KEPs that cross many SIG boundaries can be created at the root of the KEP directory.
+
+## KEP numbering
+
+The next dense number KEP will be 2.
+
+To assign a number create a commit that both renames the KEP file and updates this file.
+
+In process KEPs can use a date based numbering scheme. See [KEP-1](1-kubernetes-enhancement-proposal-process.md) for details of this process.