# Developer Advisory Board: Internal Operating Procedures **URL:** \ **Category:** Internal Operating Procedures\ **Tags:** season-5\ **Created:** [January 11, 2024, 4:52pm UTC](https://gov.optimism.io/t/developer-advisory-board-internal-operating-procedures/7343 "2024-01-11T16:52:36Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![brockelmore](https://dub1.discourse-cdn.com/bc41dd/user_avatar/gov.optimism.io/brockelmore/32/8006_2.png) [@brockelmore](https://gov.optimism.io/u/brockelmore)\ **Post date:** [January 11, 2024, 4:52pm UTC](https://gov.optimism.io/t/developer-advisory-board-internal-operating-procedures/7343/1 "2024-01-11T16:52:36Z")
The Developer Advisory Board has agreed upon our internal operating procedures. We share these procedures with the Optimism community to provide transparency on how decisions are made with regards to our mandate. To read more about our mandate, see the [introduction here](https://gov.optimism.io/t/developer-advisory-board/6892). In short, we, the board, will assess technical aspects of Delegate Mission Requests, Mission Applications, and completion of technical milestones. This document details the decision making process for those assessments. Members of the board can be reached in the Optimism discord in channel #developer-advisory-board under the Commissions & Councils tag Alternatively, you can reach the board at [developeradvisoryboard@optimism.io](mailto:developeradvisoryboard@optimism.io). ## Internal Procedures The internal procedures in this document govern the activities of the Developer Advisory Board (DAB). The document sets forth the processes the DAB will follow in order to assess and approve Delegate Mission Requests, Mission Applications under Intent #1, and technical milestone completion. Apart from the strict mandate of assessment and approvals, the DAB aims to provide general technical advisory to the Grants Council. This will be on an “as able” basis, and may extend to Delegate Mission Requests generation, Mission Applications outside intent #1, and more. There are effectively 3 work periods for the DAB: Delegate Mission Request Assessment, Mission Application Assessment for voting cycle #20, and Mission Application Assessment for voting cycle #22. The Developer Advisory Board will have a meeting every 3 weeks. An agenda will be sent out prior to the call, and minutes will be published. Grants Council members are encouraged to join. Much of the internal board communication may occur on telegram. ## Delegate Mission Request Assessment Procedure Each board member is to review all Delegate Mission Requests (DMRs) under Intent #1. The ultimate goal is to come to consensus on technical viability, provide feedback, and approve or deny a DMR. ### DMR Assessment Cycle Procedure The Cycle Procedure is set forth in detail in sections that follow. - The DMR Assessment Period will last approximately one month, ending on February 7, 2024 - During the DMR Assessment Period, the DAB will have one objective: approval or denial for each Delegate Mission Requests under Intent #1. ### Mission Application Assessment Procedure For Mission Applications, the Developer Advisory Board will review and work with the Grants Council on the technical merits of the applications, as well as communicate with applicants to provide feedback. should strive to communicate with applicants to provide feedback. - The Review & Feedback Period will last three weeks. The Review & Feedback Period will end: - The Review & Feedback Period has three objectives: (1) Review; (2) Applicant feedback; (3) Grants Council Advising. - **Objective 1 - Review** - **Objective 2 - Applicant Feedback** - **Object 3 - Grants Council Advising** ### Milestone Assessment Procedure Milestones for accepted Mission Applications require assessment as to their completion. This completion can determine whether the applicant receives payments or not. - The Milestone Assessment Period has one objective: (1) Review work-product; - **Objective 1 - Review Work-product** - Prior to milestone-based disbursement - At least 3 members of the board must review the work product and evaluate if the milestone has been reached - If this is functionality benchmark: - Does the provided work-product meet the criteria of the milestone? (Does the code run?) - If this is a specification document: - Does the specification meet the original goals? - A “no” to either of the evaluation criteria above should be brought to the Board Lead and they will bring it to the Grants Council for further deliberation - A “yes” should be communicated to signal the board’s approval - Contention or questions around completion will be brought to the Grants Council for further deliberation ## Final Developer Advisory Board Communications A summary of the Developer Advisory Board’s work and recommendations will be posted on the forum after the Delegate Mission Request process and each Mission Application process. Delegate Mission Request refusals (if applicable), Application recommendations and justification summaries, should be expected to be part of this summary. As some work will be ad-hoc advisory, that work may not appear in this summary. DAB meeting minutes will also be linked in this post.