Add section about how to work on a good-first-bug to quick reference document
Categories
(Developer Infrastructure :: Firefox Source Docs: Content, task, P3)
Tracking
(Not tracked)
People
(Reporter: tgiles, Unassigned)
References
(Blocks 1 open bug)
Details
This is especially relevant to the Outreachy contribution period. We get a lot of contributors who speed through bugs because they want to make sure they get some amount of contributions in before the period is over. However this means they'll avoid running tests, may introduce antipatterns, and generally not understand the problem they are trying to solve. I don't believe we want to encourage this hasty pattern in new contributors and so we should have a section about some common steps to take when working on a new section of code. This section should probably have some text like:
- Ask questions about the bug and your understanding of it
- How to solve the bug itself
- How to verify a solution fixes the bug
- other relevant pieces for this section.
Hi @tgiles 👋
I'd love to work on this issue and contribute to improving the quick reference documentation for new contributors.
Could you please guide me on where to find the current quick reference document and what format you'd prefer for the new section.
Also, do you have any specific points or structure in mind you'd like me to follow?
Looking forward to your guidance!
Thanks in advance.
Description
•