Bounty Board - Stand Up - 9/16/21
Last edited by
Date
Sep 16, 2021
Last Edited Time
Feb 4, 2022
Previous Action Items:
Iced - working on roadmap (see link)
Oktal / TGriff — in process of writing in GitHub ASAP if TGriff can't pickup will get to someone else
Behold/Bpetes - not yet connected to power users of the bounty board, paulapivat to get list of 'power users' (all 3 types creators/claimers,etc)
Individual Updates
- IcedCool
- Working on roadmap
- Working on high-level orientation of bounty board (e.g. go to market and collaboration opportunities w/ Degen and how to propose and approach both team for discussion
- Bpetes
- (no update; same as Iced)
- Behold
- request for some easy things from Oktal
- Oktal
- TGriff / Behold chats to get remaining tasks lined up and finished on Front-end
- Paulpivat
- No major updates; some PRs in queue
- Next step to sync w/ Brian on return to talk about data structure for guild feature
Alignment on Current Project Status
Prioritization of next steps and hand raise:
Parking Lot
- Legal update/discussion (paulapivat topic and how we should frame bounties with advice from Legal guild)
- What does bounty board want to be?
- We can't do everything, so we have to at least prioritize things and potentially say not things.
- Oktal Idea: Convey periodically how we each plan to contribute and set expectations w/ one another and keep room for all different ways to contribute
- IcedCool Idea: per season type conversations around contribution and perhaps (hrs/wk type framing); this might contribute to how we fund roles.
- Behold: working part-time, life fluctuates. Happy to stay to part-time going forward too (pretty similar). Might be helpful to get some redundancy in the team and more coding 'cross-training' particularly on tech strategy of Front-End and Back-end and better consideration of work parallelization (idea: recruit and do some code walkthroughs)
- BPetes: 1) parallelization of work via better work breakdowns in GitHub issues that trained up devs can pull (only do epics we've agreed are definitely going to be in the release). If we're going to recruit we should agree up front how many we have capacity to bring on and how we'll pair up and train them on codebase and what 'issues' can be done by new folks curious to join (good opportunity for bounties as a recruiting mechanic?) Let's not over plan allowing for ability to swap things in and out as we learn from users.
- PaulP: Micro - would love to get sense on what data we want and how to help w/ Brian on backend where I can. Macro: Suggest 80/20 approach to internal vs. external really want to focus on user experience. Bankless is an advantage we can leverage for user feedback. (Behold: Idea - dashboard requires backend lift)
- How invested do we want to be with bounty board? (part time, and part time DAO?)
- Continue to work in the DAO and build?
- Spin out and become our own DAO?
- Something else???
Potential blockers?
Action items
Roadmap discussion to lock in a release scope next week (what's in, what's out, what's the target date we can shoot for together)
Season 2 team prep: Sobol map demo, form agreement on roles we play, high level goals we shooting for.