First Task Definition: Difference between revisions

no edit summary
imported>Shauna
No edit summary
imported>Shauna
No edit summary
Line 5:
It’s become quite apparent that one of the most important factors in how much attendees enjoy our OSCTC events is the quality of the bugs/contributions they work on. It’s also apparent that our old system of scraping ‘bite size’ bugs from hundreds of projects and giving them a cursory look isn’t adequate for finding the right bugs.
 
This page is for phase I of the project - defining what makes a good bug. The questions below can help us with our definition. Feel free to add new questions, or to add to the definition below.
 
== Some further thoughts ==
 
Here are some things to think about as we draft our definition.
 
===Relevant questions===
Line 24 ⟶ 26:
** Does the project have a reasonably active mailing list or irc chatroom?
** Is the task a good one to do in pairs or groups?
 
=== Bad Task Experience ==
 
What problems have folks run into in the past?
 
* Can't figure out which files or functions need to be modified for the fix to be made.
* The bug has already been fixed but the issue on the tracker was not updated to say so.
* The bug has become irrelevant since reported. (Mostly an issue with bugs over a year old.)
* Difficulty setting up development environment.
 
=== Quality Control ===
Anonymous user