πŸ“•

First Quest Admin Proposals

Add what you plan to implement into first quest as a dev-first-quest admin below!
maaax
  • Make dev-first-quest-welcome the same as first-quest-welcome channel pinned on BanklessDAO server (read-only, task-oriented)
  • Given dev-welcome roles by finishing a series of tasks which have brief introduction on dev-guild.
  • Before finshing the task, show the admin list which they can @ or DM to proceed their onboarding.
  • Refactor channel #dev-first-quest or #dev-start-here to be the autonomous channel to grant the roles.
  • Update notion notes for new-comers, mainly tell them what they can do after completed first-quest (join weekly meeting/sign-up newsletter)
  • Cooperate with solidity channel (or any educational guilds) for web3/smart contract dev training path (if new comers are here for learning as web3 devs)
  • Cooperate with Mad Hatter bot dev could make the whole onboarding process more autonomous.
khodepanda
In order to improve and make the onboarding process more easier and friendly, I'll propose the following to be implemented;
  • A two pathway for onboarding professional developers who are ready to contribute and aspiring developers.
  • A dedicated dedicated support channel to handle problems faced by new developers and also put in place admins or members from different timezone to rotate the channel 24/7.
  • A well-structured referencing archive to lead members to tutorials, user guides, notion pages, documentation and other important resources/links to help with the general navigation of the guild and DAO.
  • Collaborate with project managers to create a Standard Operating Procedure(SOP) for various projects and products and also update the current project/product notion pages to cover documentation on team workflow, code standard, code base etc.
  • Organise weekly onboarding calls to support and onboard new developer - here frequent issues raised in the proposed support channel could also be addressed during the call.
  • Leader role tag for all serving admins and members in governance and also an organizational structure chart to help members easily identify reliable sources and cordinators in the guild.
Shame
  • To make first-quest a more hands-on onboarding process by incentivizing first-questers to get their hands dirty through the following:
    • - Work with other projects in the Dev Guild & Bounty Board to implement low-priority bounties reserved for first-questers
      - Low-priority reserved bounties can have extra BANK rewards to further incentivize first-questers (with limitations to avoid abusing/farming of course)
  • Make the Dev Guild non-dev inclusive by supporting aspiring devs through the following:
    • - Provide educational material/resources to new devs
      - Have dev office sessions where new devs can get help
      ^ Above points are overlapping with Solidity Learning groups so a collab w/ them or a generalization of the project can be started to get this going
      Β 
πŸ“•

First Quest Admin Proposals

Add what you plan to implement into first quest as a dev-first-quest admin below!
maaax
  • Make dev-first-quest-welcome the same as first-quest-welcome channel pinned on BanklessDAO server (read-only, task-oriented)
  • Given dev-welcome roles by finishing a series of tasks which have brief introduction on dev-guild.
  • Before finshing the task, show the admin list which they can @ or DM to proceed their onboarding.
  • Refactor channel #dev-first-quest or #dev-start-here to be the autonomous channel to grant the roles.
  • Update notion notes for new-comers, mainly tell them what they can do after completed first-quest (join weekly meeting/sign-up newsletter)
  • Cooperate with solidity channel (or any educational guilds) for web3/smart contract dev training path (if new comers are here for learning as web3 devs)
  • Cooperate with Mad Hatter bot dev could make the whole onboarding process more autonomous.
khodepanda
In order to improve and make the onboarding process more easier and friendly, I'll propose the following to be implemented;
  • A two pathway for onboarding professional developers who are ready to contribute and aspiring developers.
  • A dedicated dedicated support channel to handle problems faced by new developers and also put in place admins or members from different timezone to rotate the channel 24/7.
  • A well-structured referencing archive to lead members to tutorials, user guides, notion pages, documentation and other important resources/links to help with the general navigation of the guild and DAO.
  • Collaborate with project managers to create a Standard Operating Procedure(SOP) for various projects and products and also update the current project/product notion pages to cover documentation on team workflow, code standard, code base etc.
  • Organise weekly onboarding calls to support and onboard new developer - here frequent issues raised in the proposed support channel could also be addressed during the call.
  • Leader role tag for all serving admins and members in governance and also an organizational structure chart to help members easily identify reliable sources and cordinators in the guild.
Shame
  • To make first-quest a more hands-on onboarding process by incentivizing first-questers to get their hands dirty through the following:
    • - Work with other projects in the Dev Guild & Bounty Board to implement low-priority bounties reserved for first-questers
      - Low-priority reserved bounties can have extra BANK rewards to further incentivize first-questers (with limitations to avoid abusing/farming of course)
  • Make the Dev Guild non-dev inclusive by supporting aspiring devs through the following:
    • - Provide educational material/resources to new devs
      - Have dev office sessions where new devs can get help
      ^ Above points are overlapping with Solidity Learning groups so a collab w/ them or a generalization of the project can be started to get this going
      Β