<commit_before># 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]

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. Send PR out for review, titled: `Proposal: <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.
1. In your PR that implements the enhancement, move the proposal to the `implemented/` folder.<commit_msg>Change 'Proposal' to 'MEP' in enhancements instructions<commit_after># 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]

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. 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.
1. In your PR that implements the enhancement, move the proposal to the `implemented/` folder.
{'fraction_non_alphanumeric': 0.0824295010845987, 'fraction_numerical': 0.01648590021691974, 'mean_word_length': 5.02088772845953, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1512651', 'n_tokens_mistral': 669, 'n_tokens_neox': 619, 'n_words': 281}