New Bug Reporting Instructions

[Erin-Cecele]

As an open-source tool, contributions from our community are integral to the health and growth of Quire. To that end, we are pleased to introduce new guidelines for finding and reporting bugs.

If you encounter what you believe is a reproducible bug while working on a Quire project and have confirmed that it has yet to be reported, please create a bug report through our GitHub Issues tracker. You will need to include the following information in your report:

• Description
• Expected behavior
• Actual behavior
• Steps to reproduce
• Quire and Node version numbers
• Operating system and web browser numbers
• Optional Terminal/Shell output, supporting info, screenshots, workarounds, etc.

Your bug report will then be reviewed by the Getty Quire team to determine if it will be selected for development, backlogged, or closed.

If you encounter a bug that has already been reported and would like to follow along, either comment on the issue to share your experience or subscribe to it. In both instances, you will be pinged when there are updates.

If you are unsure whether your issue is a bug, please post your thoughts/questions on our GitHub Discussions board.

Read our Bug Reporting Instructions for more detailed information about what counts as a bug and why reporting them is an important way to contribute to our community.

Finally, below is a depiction of the workflow for how a suspected bug is handled by our core team:

Let us know if you have questions or feedback about this process.