Process
## Getting Help
Users can seek help on issues by themselves (via the docs FAQ) or DAOhaus Support Contributors. If issues are not known, users or Support Contributors can report these bugs by creating a Github Issue here
| Step | Phase | User/Contributor | Platform | Time |
|---|---|---|---|---|
| 1 | Customer Support: When bug is raised, we suggest known or related solutions to the issue | Support Contributor | Discord | Within few hours |
| 2 | Log Bug: IF step 1 fails, create a Github Issue with the following template | Support Contributor or User | Github | Within few hours |
Once the Github Issue is created, Product Contributors will investigate, scope and categorize bug fixes for Dev Contributors. When there is sufficient information about the bugs, the tickets will be moved to status name and ready for developers to take up.
Every week, there will be a bug status report to inform developers on outstanding bugs, so they can allocate their time to those that require their attention. Critical bugs will get immediate attention from developers, while other bugs will be dependent on developers' bandwith and priorities.
| Step | Phase | User/Contributor | Platform | Time |
|---|---|---|---|---|
| 1 | Investigation: When a new bug report is submitted, we ensure that information collected is sufficient and scope / categorize these bugs. | Product Contributor | Github | Within a week |
| 2 | Scheduling: Developers select and work on bugs during every week's planning meeting. | Dev Contributor | Github | Depends, could be faster if it's Critical
|
| 4 | Fix the bug | Dev Contributor | Various | Depends on Dev's discretion |
- Bug escalation process
- GH Project Board
- Dework Bounties