|
|
Line 237: |
Line 237: |
| <p> </p> | | <p> </p> |
|
| |
|
| ==Contribute to Firefox Desktop== | | ==Contribute to Hello Development== |
| <p> </p> | | <p> </p> |
| ===Good First Bugs=== | | ===Good First Bugs=== |
Line 244: |
Line 244: |
| <p> </p> | | <p> </p> |
| * '''Hello Backlog Good First Bugs - [http://mzl.la/1zNfmeV View in Bugzilla] | | * '''Hello Backlog Good First Bugs - [http://mzl.la/1zNfmeV View in Bugzilla] |
| <p> </p>
| |
|
| |
| ===Good Next Bugs===
| |
| <p> </p>
| |
| Marked as [good next bug] on the whiteboard, these are a the next level up, where the challenge of the bug is actually fixing the bug. There are four parts to a well-described Good Next Bug: a willing mentor, a clear initial description of the problem, clear expectations on the part of the both the mentor and contributor, and a cooperative working relationship as the bug is resolved.
| |
| <p> </p>
| |
| * '''Desktop Backlog Good Next Bugs - [http://tinyurl.com/n5go84a View in Bugzilla]
| |
| <p> </p>
| |
| ===Diamond Bugs===
| |
| <p> </p>
| |
| Marked as [diamond] on the whiteboard, this label doesn't speak to a bug's difficulty, but rather speaks to its importance. Diamond bugs are bugs that have been brought up as important bugs in engineering's various priority-triage processes but aren't assigned to an engineer by the end of the triage process.
| |
| <p> </p>
| |
| * '''Desktop Backlog Diamond Bugs - [http://tinyurl.com/kmqddfd View in Bugzilla]
| |
| <p> </p> | | <p> </p> |