A VDK Enhancement Proposal (VEP) is a way to propose, communicate and coordinate on new efforts for the Versatile Data Kit project.
- To help users and contributors understand what is being done and why is it being done this way and reduce "tribal knowledge" in our community.
- 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 having a common structure for proposing changes with important topics to cover.
- It is good idea to socialize an idea with some other contributors of VDK first. You can send your idea to VDK mailing list, slack, mail, etc.
- Follow the process outlined in the VEP template
- It is strongly recommended to build the VEP incrementally (with multiple PRs). As you research and discover new things the proposal would naturally evolve. It is very good idea the first PR should focus only on describing the motivation and the goals and so there's agreement and alignment on those before continuing.
The VEP process, as proposed, is largely based on the Kubernetes KEP process which itsef was essentially stolen from the Rust RFC process which itself resembles the Python PEP process.