Skip to content

Commit

Permalink
Use directories instead of file names for all MEP's
Browse files Browse the repository at this point in the history
  • Loading branch information
Josh Woodcock committed Oct 16, 2019
1 parent 307ea63 commit 4486abc
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions enhancements/README.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# Enhancements

The *minikube enhancement process (MEP)* is a way to propose, communicate, and coordinate on new efforts for the minikube project. You can read the full details in the (MEP proposal)[proposed/20190925-minikube-enhancement-process.md]
The *minikube enhancement process (MEP)* is a way to propose, communicate, and coordinate on new efforts for the minikube project. You can read the full details in the (MEP proposal)[implemented/20190925-minikube-enhancement-process/README.md]

MEP is based on a simplification of the [Kubernetes Enhancement Process](https://github.com/kubernetes/enhancements/blob/master/keps/0001-kubernetes-enhancement-proposal-process.md).

## Workflow

1. Copy `template.md` to `proposed/<date>-title.md` or `proposed/<date>-title/README.md` in case you need to include supporting documents. If you include supporting documents place them in the `proposed/<date>-title/` directory.
1. Copy `template.md` to `proposed/<date>-title/README.md`. Include supporting documents in the `proposed/<date>-title/` directory.
1. Send PR out for review, titled: `MEP: <title>`
1. Proposal will be discussed at the bi-weekly minikube office hours
1. After a 2-week review window, the proposal can be merged once there are 3 approving maintainers or reviewers. To keep proposals neutral, each reviewer must be independent and/or represent a different company.
Expand Down

0 comments on commit 4486abc

Please sign in to comment.