Closed derrekcoleman closed 11 months ago
I think we can do away with the RIP kanban board if this is undertaken. DM should be able to allow the appropriate filters and managing the process of executing on RIPs. This might simplify some of the process as the RIP can move with respect to the github repo from proposed to final without all the intermediate steps. The main purpose then of the repo is to have a historical record of improvements that were made to the process of RaidGuild and to have a transparent discussion of proposed changes. It would be nice if DM included comments from github within the display, but probably not necessary.
If you need any help thinking about how this will change or what we can likely strip away, I'd be happy to help.
Working on securing api route and slight refactor, then will push to develop for feedback.
Secured api route, extracted useRipList. Sort isn't working yet.
Project Idea
Project Submitted By
@derrekcoleman
Summary
Goal:
Deliverables:
Why should we build this?
Every Tuesday we gather to share updates on raids and RIPs. RIPs, however, are not represented in Dungeon Master.
Our current workaround is to use the RIP GH issues as a source of truth while making notes in our Charmverse (8/29/23 example). Neither of these is very user-friendly for tracking our members' progress over the lifetime of a project.
DM works great for raids. We deserve the same for RIPs.
Anything else you'd like to add?
This is a proof of concept to get a v1 in our hands to play with.
I'm open to suggestions before, during, and after it's shipped for other feature ideas!
What do y'all think about the scope of v1, such as automating the creation of new RIPs in DM via webhook?
Raid Party Skills Needed
Cost
$50/hr or $1,500, whichever is smaller.