AELIP 43 has been proposed and now passed the Council vote. DevDAO will allow community members with the relevant skills to actively contribute and be compensated for the on-going maintenance & development of Aelin Protocol.
DevDAO will allow community members with the relevant skills to actively contribute and be compensated for the on-going maintenance & development of Aelin Protocol. The DevDAO will be comprised of 4 distinct roles:
Community PM is in charge of managing the DevDAO
Bounty Hunters are individuals who take on entry-level tickets.
Community Devs routinely take on intermediate and advanced tickets.
Auditors are trusted Community Devs who verify code submitted by other Community Devs alongside CCs.
The DevDAO process will be managed and overseen by an elected Community PM, who will create tickets, manage who takes them, liaise with CCs, and arrange compensation.
More people being involved in the Development of Aelin should increase productivity and further decentralize the protocol. If Core Contributors are working on a large project and several small issues arise, this can take valuable time and attention away from a larger project, allowing community based Developers to take bounties for this work will help the overall process to become more efficient.
DevDAO could also act as an on-ramp for currently dormant community talent to become more integrated with the Aelin community.
Existing Core Contributors would identify issues or jobs which need outsourcing and create a bounty alongside the Community PM who will summarize and post the Bounty to Discord.
Bounty Hunters or Community Devs would pick up the open bounty and complete the necessary work.
Upon completion Auditors (Community Dev independent of the work and a Core Contributor) would verify the work, help with an AELIP or external audit if necessary.
If successful the work would be integrated by Core Contributors.
At this stage compensation is paid to the Bounty Hunter or Community Dev by the Community PM.
For a bounty to be paid out to a Bounty Hunter or Community Dev a Bounty must be assigned, completed, and then audited by a CC and Community Dev not responsible for the code.
The amount and form of compensation will vary based on bounties and community standing. We expect most bounties will be compensated in AELIN, this would of course be stated on each bounty as it’s posted.
Bounty Hunters can earn whatever a bounty is worth, whereas Community Devs have the chance to become eligible for recurring compensation in addition to normal bounty rewards after a proven track record of high quality repeat tickets.
The DevDAO interface will be managed in Discord by the Community PM. It will have its own dedicated section of the server with several channels making onboarding and workflow simple and accessible. If you’re interested please come by and introduce yourself, you could be contributing to Aelin within minutes!
AELIP 43 has been proposed and now passed the Council vote. DevDAO will allow community members with the relevant skills to actively contribute and be compensated for the on-going maintenance & development of Aelin Protocol.
DevDAO will allow community members with the relevant skills to actively contribute and be compensated for the on-going maintenance & development of Aelin Protocol. The DevDAO will be comprised of 4 distinct roles:
Community PM is in charge of managing the DevDAO
Bounty Hunters are individuals who take on entry-level tickets.
Community Devs routinely take on intermediate and advanced tickets.
Auditors are trusted Community Devs who verify code submitted by other Community Devs alongside CCs.
The DevDAO process will be managed and overseen by an elected Community PM, who will create tickets, manage who takes them, liaise with CCs, and arrange compensation.
More people being involved in the Development of Aelin should increase productivity and further decentralize the protocol. If Core Contributors are working on a large project and several small issues arise, this can take valuable time and attention away from a larger project, allowing community based Developers to take bounties for this work will help the overall process to become more efficient.
DevDAO could also act as an on-ramp for currently dormant community talent to become more integrated with the Aelin community.
Existing Core Contributors would identify issues or jobs which need outsourcing and create a bounty alongside the Community PM who will summarize and post the Bounty to Discord.
Bounty Hunters or Community Devs would pick up the open bounty and complete the necessary work.
Upon completion Auditors (Community Dev independent of the work and a Core Contributor) would verify the work, help with an AELIP or external audit if necessary.
If successful the work would be integrated by Core Contributors.
At this stage compensation is paid to the Bounty Hunter or Community Dev by the Community PM.
For a bounty to be paid out to a Bounty Hunter or Community Dev a Bounty must be assigned, completed, and then audited by a CC and Community Dev not responsible for the code.
The amount and form of compensation will vary based on bounties and community standing. We expect most bounties will be compensated in AELIN, this would of course be stated on each bounty as it’s posted.
Bounty Hunters can earn whatever a bounty is worth, whereas Community Devs have the chance to become eligible for recurring compensation in addition to normal bounty rewards after a proven track record of high quality repeat tickets.
The DevDAO interface will be managed in Discord by the Community PM. It will have its own dedicated section of the server with several channels making onboarding and workflow simple and accessible. If you’re interested please come by and introduce yourself, you could be contributing to Aelin within minutes!
A protocol focused on community capital
A protocol focused on community capital
Share Dialog
Share Dialog
Subscribe to Aelin News
Subscribe to Aelin News
<100 subscribers
<100 subscribers
No activity yet