---
tags: dragons, project management, v2
---

# v2 Process and Maintanence (4/12/22)

What workflows and processes can we create to help support v2 maintenance as we're developing v3?

[v2 GitHub Project Board: Robot Apartments ](https://github.com/orgs/HausDAO/projects/4/views/2)
[v2 Bug Triage Flow](https://hackmd.io/@arentweall/S1n6LF0aK)

## v2 Repo

- Add a bug report form as an issue template:
- This would prepopulate if someone chooses to file an issue as a bug

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**Smartphone (please complete the following information):**
 - Device: [e.g. iPhone6]
 - OS: [e.g. iOS8.1]
 - Browser [e.g. stock browser, safari]
 - Version [e.g. 22]

**Additional context**
Add any other context about the problem here.

**Workflow with Template:**


- What is our triage process?
- Issue form -> issue with bug label -> "needs triage" -> issue reviewed and set to Ready
- Do we want other issue templates besides `bug`? -- we likely want to limit this since we probably don't want to be handling v2 feature requests

## Other todos/topics

Deprecate clickup for magesmiths
- Migrate relevant clickup issues to Robot Apartments
- current v2 issue cleanup

'Ratify' bug triage process
- Wiki?

Road to bounty board?
- We could get to a spot where critical bugs or DH managed infra issues are solved by the core team, but then fund some tasks on a dework board for outside contributors
- Might be a crossover with the dev rel team :ghost:

Define roles/activities we need filled
- Support Contributor/customer service
- PM Contributor/product

## Notes From Conversation

- What is the minimal implementation and who do we need to manage it?
- Keep this as minimal as bug triage and management of the v2 backlog on the board (which is hopefully only bugs)
- Some way to surface to the devs to work on it
- DevRel workstream and future iterations:
- Bug bounty board + Boost bounty board
- Down the road, let's look into Dework to support bounties for v2
- Let's get this to the place where it can happen async

## Customer Service Support Flow

- Is this a Ranger thing? DevRel?
- Flow from Discord customer service -> product team
- Issue template
- Triage flow -> prioritize -> streamline (bounty board down the road)
- 2 inputs:
- Ranger -> issue form via identified bugs in the support channel
- Triage:
- Look into the issue
- *Ready for Dev*
- Prioritize based on how important it is
- *Critical* label that we use if needed
- Discord channel: bug reports channel

## Dev Work Flow

- At this point the issues are *Ready for Dev*
- Publishing a weekly report in Discord
- Bring this up in a meeting as a "Go check this out"
- How do we surface this w/o taking up time in the v3 meeting?
- Add this to the Dragon planning meetings

## ClickUp

- Magesmiths -> Docs -> Spec Template
- Add to the Wiki and then pair it down a bit
- Parking Lot
- Older ideas that have been dropped in
- Add things to the Backlog -> triage and create tickets
- Bug Report announcement that comes out each week and discuss in our Dragon planning meetings
- Weekly report of bugs + bugs fixed
- Folks would know where to look to grab if they have bandwidth or are blocked

## Next Steps

- [x] Pull over any ClickUp templates that make sense
- [x] Set up the Wiki
- [ ] Document the process
- [x] Templates
- https://app.clickup.com/8503263/v/dc/83fyz-1092/83fyz-252
- [x] Dev info about v2
- Checklist page with a list of things we'd want to build out to support dev docs for v2
- DevRel fill in the Wiki as they get up and running
- [x] Bug issue template
- [x] PR template
- [x] Sam brought over all of the v2 issues / bugs from ClickUp and assessed priority before adding them to the GitHub

## v2 Maintenance Setup Meeting Notes (4/19/22)

- Customer Service in Discord -- what does this look like for triage intake?

### Personas

- Who are the support contributors?
- What tools do the support contributors need? (Discord bot?)
- Who can lead the product contributore role?

### Platforms

- What needs to be included in the WiKi?
- What updates need to be made to the Docs?

### [Process](https://hackmd.io/@arentweall/S1n6LF0aK#Process)

- Create criteria for defining a critical issue

### [Reporting](https://hackmd.io/@arentweall/S1n6LF0aK#Appendix)

- Start reporting manually and explore solutions for automating

### Questions

- How do we socialize these opportunities?
- How do we share these in planning?
- How do we follow-up with the reporter?
- How do we reward the squasher?
- When do we start integrating Dework bounties?
- What information needs to be contained on the Wiki vs. the Dev Docs (Readme or on the site)?
- What materials do we need to gather/prepare for a customer service role?
- What can we provide for them to use so that it may not even come to the Product level? ie:
- Common troubleshooting areas
- What's in our control and out of our control?
- Checklist for common issues that the user can try themselves before escalating
- Customer Support needs to be familiar with the docs and the FAQ
- Point users to the Docs FAQ
- Adding this to our *Magesmith* needs
- How do we want to do this and announce it?
- Opportunities page added to the Wiki / docs -- keep this updated and point toward for folks to review
- Opportunities (role level) vs. Bounties (task level)

## Next Steps

- [ ] Wrangle Customer Service into a single process doc for triage intake and then add to the Wiki
- [ ] Outline the Wiki needs and add relevant docs to the Wiki -- start with links/updated version of the docs that already exist
- [ ] Figure out the reporting flow
- Do we want to schedule a working session for this?
- [ ] Look into the GH Board reporting / analytics views