1
edit
Changes
→Ranking the Bugs: Predicting Which Bugs Will Get Fixed by: Diederik van Liere
The time it will take to fix the bug is dependent on the developers; productivity, efficiency, and skill set. Your bug report can be flawless but if the developer doesn't have the skills necessary to fix the problem, he will need to spend some time researching.
Diederik stated that he considers anyone that posted at least one bug to Bugzilla a community member.He also pointed out that the community is like an information repository(collection of threats, artifacts, and information). Its also a collective group of people that share goals, purpose, and social group. Each community member can build, discuss, and add to the information repository. '''Understanding whats in the information repository shortens the time it takes to verify the bug.''' Diederik also talked about community churn; the process of community members leaving and getting replaced by new members. This process reduces the understanding of the information repository. Therefore, retention of community members is key, and getting new members through the learning curve is essential. Finally, the last topic that Diederik talked about was tools that can help you predict when your bug will be fixed. These tools include: Jetpack Add-On to Predict Likelihood of Bug Fix in Bugzilla, Crowdsourcing Flamy Firefox Bugreports, and Crowdsurfing Mozilla Developers Handles
