DAO Improvement Requests

##Introduction

DAO Improvement Requests(DIR) are a way to standarise the evolution process of the DAO framework code. They allow anyone who has an idea of 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 as many sections as the author wants but should contains at least the following three.

1. 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.
2. Problem Description Where the Problem that the DIR is addressing is described in detail.
3. Proposed Solution Where the author outlines his solution to the problem and the

##The Lifetime of a DAO Improvement Request

1. The author creates an issue where he outlines his idea as described in the last section.
2. 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.
3. If the request is rejected due to the discussion then the issue is tagged with the DIR-Rejected label.
4. If on the other hand work on the issue is to begin then the issue 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.
5. When all PRs are finished and merged to develop and accepted by all then the issue is tagged with the DIR-Implemented label.
6. 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