-
Notifications
You must be signed in to change notification settings - Fork 498
DAO Improvement Requests
##Introduction
DAO Improvement Requests (DIRs) are a way to standardize the evolution process of the DAO framework. They allow anyone who has a suggestion for how to improve the DAO framework to go ahead and write a detailed explanation of the feature they think should be implemented.
##Contents of a DAO Improvement Request
A DAO Improvement Request can contain anything the author wants but should contains at least the following three sections.
- Changelog At the very beginning of the document there should be a changelog to track changes to the DIR as feedback from the community starts to get incorporated. This changelog is a just a simple list including the date of the change and a short summary of what changed.
- Problem Description Where the Problem that the DIR is addressing is described in detail.
- Proposed Solution Where the author outlines his solution to the problem and the
For inspiration and ideas on how to structure a DAO Improvement Request one can always have a look at how this is already being done in the Python Language with Python Enchancement Proposals or in Bitcoin with Bitcoin Improvement Proposals.
##The Lifetime of a DAO Improvement Request
- The author creates an issue where he outlines his idea as described in the last section.
- This idea is tagged with the DIR-Draft label. Discussion begins in the comments of the issue about whether this is viable, useful and if the problem it solves is a valid one.
- If the request is rejected due to the discussion then the issue is tagged with the DIR-Rejected label.
- If on the other hand work on the issue is to be accepted then it is tagged with the DIR-InProgress label. At the same time the target DAO version for deployment of this enhancement is decided and the DIR is added to a version milestone. Also a link to the PR/PRs that are working on the issue are added to keep track of the implementation's progress. All changes to the original post that describes the proposal have to be added to the Changelog so that reviewers can keep track of them.
- When all PRs are finished and merged to develop and accepted by all then the issue is tagged with the DIR-Implemented label.
- When the DAO upgrades to a new version that contains the implemented solution to the DIR the issue is tagged with the final state label: DIR-Deployed.
An example DAO Improvement Request can be seen here where both the problem and its solution are described along with a link to a PR that implements it.
- Table of Contents
- Wiki Home
- View The DAO on the Ethereum Wallet
- DAO v1.0 Verification and JSON
- DAO Deployment
- The DAO Accounting
- Proposal Creation
- Token Creation and Transfer
- Proposal Voting and Executing
- DAO Splits
- Why Stalking Solo Splitters Makes No Sense
- Turn the Ethereum Wallet into a Mist Browser to Vote
- Proposal Framework Explanation
- PFOffer Workflow
- DAO-Improvement-Requests