Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vdk: add VDK enhancement proposal (VEP) spec template #727

Merged
merged 3 commits into from
Mar 22, 2022

Conversation

antoniivanov
Copy link
Collaborator

@antoniivanov antoniivanov commented Feb 22, 2022

As we are implementing more complex features we need a clear and easy
process to make feature proposals.

Overall the goals of the VDK Enhancement Proposal specs are:

  • To help future (and current) contributors understand what is being done and why is it being done this way
  • To help provide a better quality product by having peer review so that potential problems and inconsistencies are caught early.
  • To help contributors develop their ideas into working solutions faster and easier by following a template on what questions they need to answer.

Here we are adding a spec template. It is heavily influenced by VMware
development best practices and Kubernetes
KEPs

and Python PEPs.

You can see an example at #730

Signed-off-by: Antoni Ivanov [email protected]

@antoniivanov antoniivanov force-pushed the person/aivanov/vdk-vep branch 6 times, most recently from 672e8c2 to 90fdd91 Compare February 24, 2022 17:47
@antoniivanov antoniivanov force-pushed the person/aivanov/vdk-vep branch from c893e39 to eb4e964 Compare March 7, 2022 15:43
As we are implementing more complex features we need a clear and easy
process to make feature proposals.

Here we are adding a spec template. It is heaviy influenced by VMware
development best practices and [Kubernetes
KEPs](github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template)
and [Python PEPs](https://www.python.org/dev/peps).

Signed-off-by: Antoni Ivanov <[email protected]>
@antoniivanov antoniivanov force-pushed the person/aivanov/vdk-vep branch from eb4e964 to 6fd8fa4 Compare March 11, 2022 17:34
@antoniivanov
Copy link
Collaborator Author

I will merge this now. Please feel free to make comments. I will address them in subsequent PR.

@antoniivanov antoniivanov enabled auto-merge (squash) March 22, 2022 14:02
@antoniivanov antoniivanov merged commit e56867f into main Mar 22, 2022
@antoniivanov antoniivanov deleted the person/aivanov/vdk-vep branch March 22, 2022 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants