DIP#: <--# assigned by DIP Editor -->
Title: <DIP title>
Author(s): <Name of the authoring DGC Member>
Domain: <Ecosystems' Domains it impacts>
Status: <-- assigned by DIP Editor -->
Date Proposed: <yyyy-mm-dd>
Date Ratified: <yyyy-mm-dd>
Dependencies: <List of dependent DIPs>
Replaces: <List of DIP(s) it is replacing>
License: <added by DIP Author>
- A list of supporting materials referenced by this DIP.
- A description of what the Dijets Improvement Proposal (DIP) is focused on. Suggest 30 words max.
- A description of what the Dijets Improvement Proposal (DIP) is focused on. Suggest 100 words max.
- A description of the purpose of each module contained within the DIP. Suggest 30 words max per component.
- A short description of the motivation behind the proposed technical solution.
Details of the proposed technical solution. The specification should be detailed enough to allow devs to begin its implementation as well as testing. The specification for technical DIPs must include the following modules:
- The final code that can be used directly in the mandate vote to accept or reject the DIP.
- For the implementation or testing of the proposed code.
-
The purpose of this section is to proactively document any security-relevant design information, decisions, potential failure modes, implementation details, and the relevant discussions related to the proposed change(s). This section helps to optimise the DIP process by providing proactive guidance on security considerations when proposing a change that could affect Dijets.
-
Backwards compatibility
- Recommended licenses for developed code:
- MIT: Expat/MIT/X11 license
- BSD-2-Clause: OSI-approved BSD 2-clause license
- BSD-3-Clause: OSI-approved BSD 3-clause license
- CC0-1.0: Creative Commons CC0 1.0 Universal
- GNU-All-Permissive: GNU All-Permissive License
- Apache-2.0: Apache License, version 2.0