Confirmed users
512
edits
BugsAhoy: Difference between revisions
Jump to navigation
Jump to search
→How do bugs appear in it?
No edit summary |
|||
| Line 9: | Line 9: | ||
Bugs Ahoy performs bugzilla searches based on the several parameters: | Bugs Ahoy performs bugzilla searches based on the several parameters: | ||
* every bug displayed is [[Mentors|mentored]] (ie. the whiteboard contains the <i>[mentor=...]</i> annotation) | * every bug displayed is [[Mentors|mentored]] (ie. the whiteboard contains the <b><i>[mentor=...]</i></b> annotation) | ||
* whether the bug's product/component is in the list of products and components that relate to the contributor's interests | * whether the bug's product/component is in the list of products and components that relate to the contributor's interests | ||
In addition, more and more mentors are including language annotations in bugs (<i>[lang=...]</i>, where ... is one of c++, py, css, js, etc.). These are relevant, because Bugs Ahoy uses this data to filter the results of searches based on the contributor's indicated skills. Therefore, if a fix for a given bug will predominantly require using a specific language (or combination of languages, as multiple lang attributes are allowed), adding a <i>lang</i> annotation in a mentored bug's whiteboard will increase its visibility in Bugs Ahoy. | In addition, more and more mentors are including language annotations in bugs (<b><i>[lang=...]</i></b>, where ... is one of c++, py, css, js, etc.). These are relevant, because Bugs Ahoy uses this data to filter the results of searches based on the contributor's indicated skills. Therefore, if a fix for a given bug will predominantly require using a specific language (or combination of languages, as multiple lang attributes are allowed), adding a <i>lang</i> annotation in a mentored bug's whiteboard will increase its visibility in Bugs Ahoy. | ||
== How do I contribute to Bugs Ahoy? == | == How do I contribute to Bugs Ahoy? == | ||
You can grab the [https://github.com/jdm/bugsahoy source], find a [https://github.com/jdm/bugsahoy/issues?milestone=&labels=&state=open task] that needs doing, and start hacking! Bugs Ahoy is very simple to play with - just visit the page on your harddrive from your webbrowser; you don't even need to set up a webserver. | You can grab the [https://github.com/jdm/bugsahoy source], find a [https://github.com/jdm/bugsahoy/issues?milestone=&labels=&state=open task] that needs doing, and start hacking! Bugs Ahoy is very simple to play with - just visit the page on your harddrive from your webbrowser; you don't even need to set up a webserver. | ||