# Dework <> DAOhaus (4/11/22) - Bounty and compensation structure and how Dework fits in - Project Management System and how Dework fits in ## Dework Roles - Talked with Amos and BoilerRat about Holocracy and role structures in Dework - How would this work within Dework? - 1:1 Sync with GitHub to sync with Dework -- Task created mirrored in Dework and PRs move to Done - Merged code jumps to done - Gating options: - Selecting specific assignees or choosing based on Discord roles, or allowing for self-selection - Discord Roles: - Emerged from uses where there is more fluid engagement - Pulling in Discord roles would gate ability to select for role - Would this then enter them into the Application Process flow? - If don't have the role: Anyone can still apply to a gated role (allows for folks to apply for work) - If you hace role: can claim the task and then no one else is able to - Gate with roles allows for skipping the application process for certain contributors who have specific roles - Find new contributors in this way - This doesn't work with how DAOhaus Discord is set up, but we may want to be revisiting our Discord roles -- some teams may need to retrofit their Discord setups to make it work - This could then allow for more hierarchical structures for tasks and bounties - Input on structuring the roles within DAOs to work within a tool like Dework in a PM process - Dework informs the role structure based on the features and workflows - Assign a `v3` role: highest level of trust and accountability when self-assigning as compared to folks who are more loosely dedicated (more difficult to enforce their progress) - No staking right now, but imposing some form of slashing via removing roles (roles unlock more important tasks and trust via the structure) - Losing role is highly impactful in this structure - How to assign levels from the start? - History of the work that's been done by the contributors as the starting point (internal reputation and level) - Knowing history of person then translates to a certain level - Can this map to our Levels for Commitment Track? - Keeping the process open and allow for fluidity is important to this system - Our current structure for v3: - 4-5 core devs working on v3 between 50% and 100% time allocation, but we also have to maintain v2 which needs a support structure (1-2 devs focused on this at the moment) - This could be an important opportunity to hand some of these tasks over and start piloting with Dework ## Coordinape <> Dework - Dework bounties -> Coordinape reward? - Connect to Dework - Allows for `give` to be allocated via completing Dework bounties - Moving from Review -> Done - We could use this in Raid Guild - With GitHub sync you'd also have this synced in Coordinape - Pulls in tasks that have been completed and reviewed - Reviewer needs to be set in the Dework card -- can this be automated in Dework? - Lots of work to create the tasks but this is aiming to resolve this -- making the time spent more visible - People are avoiding doing product/project management in DAOs because of the lack of recognition -- how can we solve this problem?