Part C Evaluation

Fields

• ID: The numeric id of a bug, unique within this entire installation of GNOME Bugzilla.
• Sev: How severe the bug is, or whether it's an enhancement.
• Pri: Engineers prioritize their bugs using this field.
• OS: The operating system the bug was observed on. Note: When searching, selecting the option "All" only finds bugs whose value for this field is literally the word "All".
• Product: Bugs are categorised into Products and Components. Select a Classification to narrow down this list.
• Status: The Status field indicates the current state of a bug. Only certain status transitions are allowed.
• Resolution: The Resolution field indicates what happened to this bug.
• Summary: The bug summary is a short sentence which succinctly describes what the bug is about.

Describe how you discovered the definitions and how did you find the information from above Field description

What is the meaning of the colors used when describing a bug:

• red: normal critical
• gray: normal enhancement
• black: normal normal

Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).

Bug 635218

Identify when the bug was submitted. 2010-11-18 19:57 Identify if there has been recent discussion about the bug? No Is the bug current? No Is the bug assigned? Not really To whom? ocrfeeder-maint Describe what you would need to do to fix the bug. Rework to add Kurzweil-like functionality

Reports

• How many bug reports were opened in the last week? 311 How many were closed? 232
• What was the general trend last week? Were more bugs opened than closed or vice versa? More opened than closed
• Who were the top three bug closers? Edward Hervey, Florian Müllner, Philip Withnall
• Why is this important to know? Know who is active and who is an area expert
• Who were the top three bug reporters? Frank, Jeremy Bicha, Christian Hergert
• Are these the same as the top three bug closes? no
• What is the overlap in these two lists? Significant
• Who are the top three reviewers of patches? Marcus Lundblad, Debarshi Ray, Carlos Garnacho
• What is the overlap between these lists and the bug closers and bug reporters? Significant
• What is the overlap between patch contributors and patch reviewers? Significant

Graphical Reports

• What class were the majority of the bugs for braille? Normal
• What other reports can you generate? Bar, lines, other data from the bugs, other y values.

FOSS in Course

1. Guest and Student led Lectures
   1. Tools
   2. Community standards
   3. Testing
2. Project Definition
   1. Teamwork
   2. How to identify a good open source project
3. Group work
   1. Practical experience in FOSS

Grading is based on effort as measured by student activity, participation in group activities, blogs, attendance, commits and presentations. Grading is not based on the overall success of the project.Mostly team activities with input from community members leveraged to gauge student activity and impact. Work doesn't necessarily need to be accepted by commits are a significant measure of activity, but acceptance into communities can be problematic during a short semester length effort.