Summary of KR Workflow

  1. KR comes in from a public-facing form (e.g. Google, Tally or built into Discord using embeds).

  2. Notion gets updated by Zapier bot

  3. Zapier bot sends a notification to ping the requested subDAO(s) in Discord about the new KR. Could also ping the MedicoLegal as well/instead to provide some oversight, transparency, accountability & routing support for subDAOs. → [MedicoLegal Chat](https://meddao.notion.site/MedicoLegal-Chat-fbe6fe47b1a94cc4b12a82fbfce2e161) 1.

  4. DeWork issues a task/bounty on-chain

    MedDAO | Dework

  5. SubDAOs respond by updating Knowledge Request Tracker to claim KR

  6. Sub-tasks are added to DeWork bounty until the subDAO submits it for final review

  7. MedicoLegal WG and submitter of the KR either approve/deny the submission

  8. Bounty is paid out on-chain to the subDAO, or directly to contributor(s), depending on the subDAOs governance.

    1. Todo
      • [ ] Multi-sig?
  9. If bounty is paid directly to the subDAO, they could distribute the amount via Coordinape or use some internal accounting to allocate remuneration to individual contributors.

    1. Todo
      • [ ] Setup Coordinape - requires wallet

References:

Notion

rzachSeptember 29, 2022 10:36 AM (PDT)

@flowscience What do you know about https://dework.xyz/

flowscienceSeptember 29, 2022 11:21 AM (PDT)

That's a fantastic idea. It's gotten pretty popular and I've used it on a variety of teams. It makes sense to track KRs with a kanban style workflow and having an on-chain MVP would be ideal. Issuing KRs as bounties also makes sense and each subDAO can link DeWork to a subDAO-specific Coordinape round so contributors can have a monthly/seasonal peer-reward system integrated with the record of tasks completed for KRs they responded to. DeWork has a great discord bot too.

DeWork also integrates with Notion & Github so tasks can be issued directly from those platforms.