devDAO Community Role Structure

Summary

This proposal outlines a tiered role structure for the devDAO. Abstract

Creating a tiered role system for devDAO community members to grow into when contributing code to the development of Kwenta. The tiered role system will allow for systematic growth and engagement as well as an unambiguous path to distribute tickets by skill level.

Motivation

To facilitate future growth and engagement within the devDAO, a tiered role structure is proposed. Currently, devDAO community members can only reach Bounty Hunter status by getting a single ticket merged into the code base. Once the devDAO is tasked with solving advanced tickets, a system should be in place to make sure the right community devs/roles are being contacted in order to solve aforementioned tickets.

Specification

Full details here: https://kips.kwenta.io/kips/kip-15/