canmove, Confirmed users
2,850
edits
Taskcluster/Deprecated/Participation/Good First Bugs: Difference between revisions
Taskcluster/Deprecated/Participation/Good First Bugs (view source)
Revision as of 20:24, 29 September 2020
, 29 September 2020ChrisCooper moved page Taskcluster/Participation/Good First Bugs to Taskcluster/Deprecated/Participation/Good First Bugs: Deprecated
(Created page with "A good first bug is one that has been tagged specifically as a good place for interested people to get started. The idea is that it doesn't require a lot of deep knowledg...") |
ChrisCooper (talk | contribs) m (ChrisCooper moved page Taskcluster/Participation/Good First Bugs to Taskcluster/Deprecated/Participation/Good First Bugs: Deprecated) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
A [[good first bug]] is one that has been tagged specifically as a good place for interested people to get started. The idea is that it doesn't require a lot of deep knowledge, is | A [[good first bug]] is one that has been tagged specifically as a good place for interested people to get started. The idea is that it doesn't require a lot of deep knowledge, is reasonably clear, and won't take too long to fix. | ||
= Finding Good First Bugs = | = Finding Good First Bugs = | ||
For | For Taskcluster, you can find good first bugs in Bugzilla on https://codetribute.netlify.app/projects/taskcluster Codetribute]. We are less consistent about tagging good-first-bugs in github, but you can also look at our list of [https://github.com/issues?q=is%3Aopen+is%3Aissue+org%3Ataskcluster+no%3Aassignee+label%3A%22good+first+issue%22 github issues]. | ||
Once you've found something to work on, do a little research about it. Find the source code yourself, or try to reproduce the issue. Then, based on what you've learned, post to the bug and show you've done your homework. Something like, "I ran the app locally and reproduced the issue using the steps above. I think the fix would be in the flub function in flubby.py. Am I on the right track?" | Once you've found something to work on, do a little research about it. Find the source code yourself, or try to reproduce the issue. Then, based on what you've learned, post to the bug and show you've done your homework. Something like, "I ran the app locally and reproduced the issue using the steps above. I think the fix would be in the flub function in flubby.py. Am I on the right track?" | ||