BanklessDAO
BanklessDAO
/
Developers Guild
Developers Guild
/
🏗️
Dev Guild Projects
/
👶🏻
Dev First Quest
/
📔
Original Proposal
📔

Original Proposal

Table of Contents
Proposal Overview
Program Champion: jordaniza Program Name: Dev Guild, First Quest Program Justification: (see "problems" Below Program Terms: Per Season of 54000$BANK to be paid out to L2 Coordinator (24000$BANK) + 5000$BANK to 6 admins, across 2 cohorts
Authors: behold, hashedmae, KenMan, jordaniza, TheRG
Date Created: 10/24/2021
Date Posted: 10/29/2021
Vote: Link
💡
Suggestion for next steps: review with the wider guild for final commentary, if approved, decide on a timeline for the first implementation + elect the 3 guest pass administrators and the single L2 coordinator for the genesis cohort
Summary
The development guild currently has a high number of people wanted to become involved and we are struggling to onboard them effectively.
We are looking to create a DEV FIRST QUEST workflow, that encompasses 2 cohorts over a season, run by:
  • A team of 3 administrators, selected from the previous cohort of new Devs, to handle day-to-day operations
  • A single L2 Coordinator from Bankless, to be responsible for strategic oversight of the programme
Background
  • Lots of people wanting to get involved in Bankless as devs, but hard to onboard:
    • People have a wide range of skillsets
    • The existing contributor team has limited spare capacity to dedicate to 1-to-1s
    • There will naturally be some folks who lose interest over time
    • There will be some folks who would need a lot of extra handholding
  • Dev onboarding is a process, it takes time versus other forms of contributions, so there is an argument to have a dedicated dev onboarding workflow.
An Ideal First Quest...
...gives the new entrant a benefit
  • New devs can earn BANK from contributory activities - scribing, documentation, issue identification.
  • New devs can also learn about the current technologies and how the DAO works, without having to ask.
  • Should point the new devs to an obvious place where they can contribute.
 
...gives the dev guild a benefit
  • New devs provide a fresh pair of eyes and perspective on our current projects, they can spot areas where things are opaque and highlight them to established members.
  • There are areas in current projects, related to setup, onboarding and documentation, where someone with general experience but limited project understanding, can add value.
 
...is self sustaining and decentralised
  • Just creating another page on notion is not enough, it will get outdated as soon as it is written, instead, this should be a continuously evolving programme that is maintained and overseen by its graduates.
  • Instead of requiring yet more time investment by already stretched Bankless key drivers, from conception, this should be maintained and run by new entrants.
Broad Structure
Each month, a new cohort is created. A cohort:
  • Has a moderation team from the previous cohort
  • Has a single L2 or L1 who is assigned to the moderation team in an oversight role.
A cohort is an arbitary window, giving a structured end date to the first quest for new devs. Devs can join at any time, progress is rolled over between cohorts, and a dev is eligible to graduate a cohort once all first quest tasks have been completed.
💡
More details on the roles of the moderation team and the detailed quest tasks are in the appendices
Costs
Per Cohort funding of 5000 $BANK to a maximum of 3 Contributors, plus 2000 $BANK per week for the coordinator. TBC if there is an additional allowance for the genesis cohort.
Bankless Brand Usage
  • Use of the bankless dev guild discord, with a dedicated channel
 
Appendix 1: The Role of the FQ L2 Representative vs the Admins
Ideally, first quest is a continuous process, run by devs and iterated upon by people with fresh eyes. Despite that, we still need to ensure a barometer of quality is met. Proposal is to have an L2 ultimately responsible for the long term success of the first quest project (along with the project champion for the first few cohorts).
Expected Hours
  • 1 - 2 additional hours per week
First Quest Expected Tasks for the L2 Rep
  • Manage the admins:
    • Source alternative admins if a cohort admin is unable to meet minimum commitment levels (as determined by the talent coordinator)
    • Verify that admins are being responsive in answering to new joiners in onboarding
    • Verify that admins are meeting minimum commitment levels to justify salaries for first quest
    • Handle escalations from cohort admins, for issues they cannot solve
  • Review proposed changes to first quest project, along with the admin team
  • Monitor statistics and survey results to see how well the first quest is performing, across seasons and cohorts
What the L2 Rep is NOT expected to do (and the Admins are)
  • Be reviewing completion of first quest tasks for new devs (remit of the cohort admins)
  • Handle the majority of the onboarding questions from new devs
  • Implement changes to the first quest, as recommended by new devs and admins (the devs and admins should be taking these on as tasks, once agreed by the TC and admins)
What the L2 Rep can choose to do, at their discretion
  • Answer day-to-day questions from new joiners as part of onboarding
  • Propose changes to the first quest
Primary Roles of the Admins
  • Field day to day queries and be the "warm, welcoming face" of the guild
  • Check that first quest items have actually been completed, when necessary
  • Implement improvements to the first quest project and infrastructure over the course of a cohort
How Admins are Selected
  • At the end of a cohort, graduates can put themselves forward to become an admin
  • The talent coordinator (or equivalent) will approve the nominations
  • The dev guild + current cohort will vote to see who is made admin for the next cohort
Appendix 2: Details of First Quest Tasks
💡
Some of these will have $BANK associated
Orientation
Familiarizing themselves with the dev guild, the new joiner is required to:
  • Complete the contributor survey
  • Introduce themselves in the discord, with a brief explanation of their skills
  • Collect 4 POAPs for attending Dev guild weekly calls and/or focused discussions
  • (Only required if the new joiner prefers to join in an administrative/PM/Managerial role) Collect the scribe bounty for at least one of the weekly calls and/or focused discussions
Project Shortlist
Having understood a bit more about the bankless dev guild, the new dev should start exploring the work we are currently doing, to understand where they might be able to offer value.
  • (Only required if the new joiner prefers to join in an engineering role) Build locally at least 1 project from the bankless project list
  • Attend at least 1 standup for a bankless project
Contribution
Seeing what we have going on, and actually building the project, the new dev should start to see areas where they can offer value:
  • Identify an issue (feature or bug) that needs work, on one of the projects, and create it on github with a full breakdown of the problem
  • Make at least 1 commit to either a project README or a project's notion page, to improve documentation (getting setup, architecture overview, etc)
Review
Closing off the first quest, the new dev should be in a great position to help bankless dev guild improve its onboarding process!
  • Make at least 1 commit to the notion for the onboarding/first quest project/new joiners guide, to help improve the process for the next cohort
  • Complete the onboarding survey, so we can see the areas of difficulty and strength across cohorts.
 
At this stage, the first quest is complete. The final stage is to attend the monthly cohort call with the new recruits, where devs can share ideas with other new joiners and established members, to decide where to go from here. Graduates can then put themselves forward to be on the moderation team for next month's cohort.
BanklessDAO
BanklessDAO
/
Developers Guild
Developers Guild
/
🏗️
Dev Guild Projects
/
👶🏻
Dev First Quest
/
📔
Original Proposal
📔

Original Proposal

Table of Contents
Proposal Overview
Program Champion: jordaniza Program Name: Dev Guild, First Quest Program Justification: (see "problems" Below Program Terms: Per Season of 54000$BANK to be paid out to L2 Coordinator (24000$BANK) + 5000$BANK to 6 admins, across 2 cohorts
Authors: behold, hashedmae, KenMan, jordaniza, TheRG
Date Created: 10/24/2021
Date Posted: 10/29/2021
Vote: Link
💡
Suggestion for next steps: review with the wider guild for final commentary, if approved, decide on a timeline for the first implementation + elect the 3 guest pass administrators and the single L2 coordinator for the genesis cohort
Summary
The development guild currently has a high number of people wanted to become involved and we are struggling to onboard them effectively.
We are looking to create a DEV FIRST QUEST workflow, that encompasses 2 cohorts over a season, run by:
  • A team of 3 administrators, selected from the previous cohort of new Devs, to handle day-to-day operations
  • A single L2 Coordinator from Bankless, to be responsible for strategic oversight of the programme
Background
  • Lots of people wanting to get involved in Bankless as devs, but hard to onboard:
    • People have a wide range of skillsets
    • The existing contributor team has limited spare capacity to dedicate to 1-to-1s
    • There will naturally be some folks who lose interest over time
    • There will be some folks who would need a lot of extra handholding
  • Dev onboarding is a process, it takes time versus other forms of contributions, so there is an argument to have a dedicated dev onboarding workflow.
An Ideal First Quest...
...gives the new entrant a benefit
  • New devs can earn BANK from contributory activities - scribing, documentation, issue identification.
  • New devs can also learn about the current technologies and how the DAO works, without having to ask.
  • Should point the new devs to an obvious place where they can contribute.
 
...gives the dev guild a benefit
  • New devs provide a fresh pair of eyes and perspective on our current projects, they can spot areas where things are opaque and highlight them to established members.
  • There are areas in current projects, related to setup, onboarding and documentation, where someone with general experience but limited project understanding, can add value.
 
...is self sustaining and decentralised
  • Just creating another page on notion is not enough, it will get outdated as soon as it is written, instead, this should be a continuously evolving programme that is maintained and overseen by its graduates.
  • Instead of requiring yet more time investment by already stretched Bankless key drivers, from conception, this should be maintained and run by new entrants.
Broad Structure
Each month, a new cohort is created. A cohort:
  • Has a moderation team from the previous cohort
  • Has a single L2 or L1 who is assigned to the moderation team in an oversight role.
A cohort is an arbitary window, giving a structured end date to the first quest for new devs. Devs can join at any time, progress is rolled over between cohorts, and a dev is eligible to graduate a cohort once all first quest tasks have been completed.
💡
More details on the roles of the moderation team and the detailed quest tasks are in the appendices
Costs
Per Cohort funding of 5000 $BANK to a maximum of 3 Contributors, plus 2000 $BANK per week for the coordinator. TBC if there is an additional allowance for the genesis cohort.
Bankless Brand Usage
  • Use of the bankless dev guild discord, with a dedicated channel
 
Appendix 1: The Role of the FQ L2 Representative vs the Admins
Ideally, first quest is a continuous process, run by devs and iterated upon by people with fresh eyes. Despite that, we still need to ensure a barometer of quality is met. Proposal is to have an L2 ultimately responsible for the long term success of the first quest project (along with the project champion for the first few cohorts).
Expected Hours
  • 1 - 2 additional hours per week
First Quest Expected Tasks for the L2 Rep
  • Manage the admins:
    • Source alternative admins if a cohort admin is unable to meet minimum commitment levels (as determined by the talent coordinator)
    • Verify that admins are being responsive in answering to new joiners in onboarding
    • Verify that admins are meeting minimum commitment levels to justify salaries for first quest
    • Handle escalations from cohort admins, for issues they cannot solve
  • Review proposed changes to first quest project, along with the admin team
  • Monitor statistics and survey results to see how well the first quest is performing, across seasons and cohorts
What the L2 Rep is NOT expected to do (and the Admins are)
  • Be reviewing completion of first quest tasks for new devs (remit of the cohort admins)
  • Handle the majority of the onboarding questions from new devs
  • Implement changes to the first quest, as recommended by new devs and admins (the devs and admins should be taking these on as tasks, once agreed by the TC and admins)
What the L2 Rep can choose to do, at their discretion
  • Answer day-to-day questions from new joiners as part of onboarding
  • Propose changes to the first quest
Primary Roles of the Admins
  • Field day to day queries and be the "warm, welcoming face" of the guild
  • Check that first quest items have actually been completed, when necessary
  • Implement improvements to the first quest project and infrastructure over the course of a cohort
How Admins are Selected
  • At the end of a cohort, graduates can put themselves forward to become an admin
  • The talent coordinator (or equivalent) will approve the nominations
  • The dev guild + current cohort will vote to see who is made admin for the next cohort
Appendix 2: Details of First Quest Tasks
💡
Some of these will have $BANK associated
Orientation
Familiarizing themselves with the dev guild, the new joiner is required to:
  • Complete the contributor survey
  • Introduce themselves in the discord, with a brief explanation of their skills
  • Collect 4 POAPs for attending Dev guild weekly calls and/or focused discussions
  • (Only required if the new joiner prefers to join in an administrative/PM/Managerial role) Collect the scribe bounty for at least one of the weekly calls and/or focused discussions
Project Shortlist
Having understood a bit more about the bankless dev guild, the new dev should start exploring the work we are currently doing, to understand where they might be able to offer value.
  • (Only required if the new joiner prefers to join in an engineering role) Build locally at least 1 project from the bankless project list
  • Attend at least 1 standup for a bankless project
Contribution
Seeing what we have going on, and actually building the project, the new dev should start to see areas where they can offer value:
  • Identify an issue (feature or bug) that needs work, on one of the projects, and create it on github with a full breakdown of the problem
  • Make at least 1 commit to either a project README or a project's notion page, to improve documentation (getting setup, architecture overview, etc)
Review
Closing off the first quest, the new dev should be in a great position to help bankless dev guild improve its onboarding process!
  • Make at least 1 commit to the notion for the onboarding/first quest project/new joiners guide, to help improve the process for the next cohort
  • Complete the onboarding survey, so we can see the areas of difficulty and strength across cohorts.
 
At this stage, the first quest is complete. The final stage is to attend the monthly cohort call with the new recruits, where devs can share ideas with other new joiners and established members, to decide where to go from here. Graduates can then put themselves forward to be on the moderation team for next month's cohort.