DIP Editor - Responsibilities & Criteria

Dijets Improvement Proposals Framework requires a DIP Editor to support and enforce the administrative and editorial aspects of the overall DIPs process. This document is a module (DIP0m9) of the genesis DIP0.

DIP Editor


The DIP Editor enforces the administrative and editorial aspects of the overall DIPs process and framework. This includes:

  • Maintain and manage the DIPS Directory
  • Provide feedback and hold discussions (eg: helping vet proposal ideas) where necessary within the DIPs section of Dijets Forum.
  • DIPs processing.
  • Manage and organise DIPs and Sub-proposal Preambles.
  • Onboard and vet new DIP Editors when required.
  • Enforcing the proper DIPs process with responsibilities including but not limited to:
    • Confirm that the title accurately describes the content of the proposal.
    • Assign formal number labels to the proposed DIPs.
    • Change DIP statuses.
    • Correct DIP domain and index categories and placement.
    • Correspond with the DIP authoring DGC Member.
    • Review the DIP for obvious issues and defects (completeness, format, spelling, grammar, structure) and that it follows the template guide. DIP Editors are allowed to correct aforementioned problems themselves, but are not required to do so and can send comments to the authoring members so they can improve the proposal themselves.
    • Work and communicate with Governance Facilitators on coordinating governance and mandate votes in relation to DIPs and the corresponding voting cycles.

Selection Criteria

DGC Members should note the following criteria when selecting a DIP Editor:

  • Complete understanding of the DIPs Framework.
  • The Core Team will provide any assistance required by the DIP Editor once onboarded but prospective candidates must be fully familiar with Dijets Ecosystem, DIPs framework and how it operates.
  • Dijets Council can elect a DIP Editor amongst themselves or decide on electing individuals from the wider community after the governance program’s maturity. Selecting individuals for an Editor role from the community could depend upon some of the following criteria:
    • Frequency and quality of any past forum posts.
    • Attendance and general contribution in discussions on Qowalts and Dijets Forum.
    • Articles written about Dijets Ecosystem and/or its domains.
    • Guides, videos or informational literature about Dijets Ecosystem and/or its governance.
  • Technical Familiarity with the inner workings of Dijets Protocol (bonus but not a requirement)
  • Experience with Github and its basic features
    • Merging, editing, closing Pull Requests
    • Addressing issues
    • Adding tags / labels
  • Experience with Markdown language
    • DIPs are written in Markdown, so editors will need to be familiar with the language. An online editing tool Marko is available to help with drafting proposals in markdown.


Once a person has been onboarded to the DIP Editor role, they will be invited to join Dijets Inc. organisation on Github and subscribe to watching the DIP repository. They will also become a Moderator on Dijets Forum and Qowalts. Much of the correspondence regarding DIPs will be handled through GitHub as well as through Qowalts and Dijets Forum.


A DIP Editor should be considered for removal if they are:

  • Absent from their duties for a prolonged period.
  • Inadequately performing their defined duties.
  • Displaying biased or malicious behaviour.
  • Expressing unwillingness to continue in their role as DIP Editor.

The removal process begins once the council has agreed on the reasoning for removal. This process must be communicated publicly via the forums in order to provide complete transparency. The DIP Editor will then have the assigned authorities, HAL scores, and incentives removed from their profile:

1 Like