Developer Advisory Board - S7 Internal Operation Procedures

Elected Representatives 💼 Internal Operating Procedures
1

The Internal Operating Procedures in this document govern the activities of the Season 7 Developer Advisory Board. This document sets forth the processes the Developer Advisory Board will follow in fulfilling the Charter. This structure is supported by this governance approved budget.

If ever a discrepancy arises between a Charter and the Internal Operating Procedures (IOPs), the Charters always take precedence and supersede the IOPs.

Communications

  • To get in touch with a member of the Developer Advisory Board, please add a comment on the Communication Thread on the forum.
  • Office hours will be held on an ongoing basis to specifically support grant applicants. Times will posted at the bottom of Missions and on the governance calendar.

Cycle & Workflow Management

The Developer Advisory Board serves a number of separate roles, each with its own workflow.

1) Governance Missions

  • The Grants council will provide a list of applications they would like feedback on at least 7 days before the end of each voting cycle.
  • DAB Ops Lead will organize the requests in a spreadsheet, which will be shared with the DAB. DAB Members will have 24 hours to proactively claim applications to review. After 24 hours, Ops Lead will randomly assign the remaining applications such that each application has 1 reviewer.
  • Feedback will be provided directly in Charmverse on the application, in the following format:
    • On behalf of the Developer Advisory Board, I’d like to share the following feedback:
      • Technical Feasibility:
      • Alignment with Mission:
      • Team Qualification:
      • Budget Appropriateness:
      • Other Notes:
  • If the application is non-technical, the DAB member has the option to simply note that they have reviewed the application and that it is outside of their purview.

2) Foundation Missions

  • TBD. The Foundation is finalizing their exact process and needs, and this document will be updated when details are confirmed (by late Feb).

3) Audit Request Missions

  • TBD. This process is moving over from the Grants Council to the DAB. We have a rough outline, but will update this post with the final process by late February.

4) Protocol Upgrades

  • When a new upgrade is posted to the forums, it will be shared with the DAB. Each DAB member will express their feedback internally, along with their perspective on whether they feel comfortable supporting it.
  • If there are disagreements within the group, a call will be set up to share opinions and ensure that each member’s opinion is understood and clarified.
  • Within 96 hours, the DAB Lead will post the group’s perspective on the forum post.
  • Any individual member is free to leave an additional comment with their perspective if they would like to provide more detail than the DAB’s post.

Internal Consensus and Voting

  • The Audit Review Team (2 people) and Foundation Mission Team (2 people) will make their funding decisions based on unanimous agreement. If the two members are not able to agree and a decision has to be made, the DAB Lead will act as a tie breaking vote.
  • Bonus Rewards will be allocated based on the formula and tracked activities in this spreadsheet. Bonus Reward entries are added for activities that go above and beyond the DAB’s expected actions, and are rewarded (between 1-3 points) based on the specific activity’s impact on the OP Ecosystem. Entries will be determined by the Lead. The Lead cannot allocate any bonus rewards to themselves.
6 Likes