Devcon(nect) Improvement Proposals (DIPs) are intended for collaborative community input on what should be changed (subtracted, added or modified) for the upcoming Devcon(nect).
While we are excited to have a more formal process to hear ideas from the community (roughly inspired by the more decentralized PEP, BIP and EIP processes), this is an experiment, and it should be understood that approval of proposals ultimately lies solely with the Devcon(nect) team. DIPs focus on collaboration in the ecosystem, so please review DIP-0 and try to collaborate on other proposals before submitting your new DIP. We're excited to see all of your great ideas!
You can also see the DIPs on the Devcon website.
- Post your idea in the Devcon Forum, publicize it, discuss it there, and gather feedback.
- Once you have feedback and some interest in the idea, proceed with the below steps.
- Review DIP-0. If you have questions or need help with Github, please just ask us — we can help you!
- Fork the repository by clicking "Fork" at the top right.
- Add your DIP to your fork of the repository.
- Submit a Pull Request to this repository
After submitting editors will go through this checklist - it is encouraged that you already went through these points yourself.
- Draft - a DIP that is undergoing rapid iteration and changes.
- Accepted - The Devcon(nect) Organisers have Accepted your DIP.
- Postponed - The DIP won’t be possible for the following edition.
- Not implemented - The DIP won’t be implemented.
- Changes Requested - The DIP needs modifications conditional to its validation.