Bug Tracker Activity-MouseTrap

From Foss2Serve

(Difference between revisions)

Jump to: navigation, search

Latest revision as of 19:19, 7 September 2018

Title	Bug Tracker Activity-MouseTrap
Overview	Learners will gain an understanding of the features of bug trackers and how they are used to identify work items to be completed in a FOSS project.
Prerequisites	None
Learning Objectives	After successfully completing this activity, the learner should be able to: Describe the role that a bug tracker plays in a FOSS project. Describe the different types of issues stored in a bug tracker and their priorities. Identify and track the status of a particular bug in a project.
Process Skills Practiced	What process skills will the student practice while completing this activity?

References:

Background:

Bug tracking systems are a form of change management and organization used by FOSS projects. Bug trackers do far more than simply keep track of bugs. They also are used to hold new feature requests, patches, and some tasks. Bug trackers are also called request trackers, issue trackers and ticket systems.

Directions:

We will use the GNOME MouseTrap project to explore a typical Bugzilla instance for a project.

Part 1 - Bug Reports

Open a browser and go to GNOME Bugzilla
Enter 'MouseTrap' in the search bar.
What do each of the column names below indicate? What are the range of possible values for 2-7 below?
1. ID
2. Sev
3. Pri
4. OS
5. Product
6. Status
7. Resolution
8. Summary
In what order are the bugs initially displayed?
What is the meaning of the shading of some bug reports?
What is the meaning of the colors used when describing a bug (red, gray, black)?
What do the bug reports tell you about the current state of the system?
Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number).
1. Identify when the bug was submitted.
2. How understandable is the description?
3. Identify if there has been recent discussion about the bug?
4. Is the bug current?
5. Is the bug assigned? To whom?
6. What would we need to do to fix the bug?
Repeat the previous step with a different kind of bug.

Part 2 - Collective Reports

This section refers to the entire GNOME project, not just MouseTrap.

Click on the “Reports” link on the top of the page.
Click on "Summary of bug activity for the last week."
How many bug reports were opened in the last week? How many were closed?
What was the general trend last week? Were more bugs opened than closed or vice versa?
Who were the top three bug closers? Why is this important to know?
Who were the top three bug reporters? Are these the same as the top three bug closes? What is the overlap in these two lists?
Who are the top three contributors of patches?
Who are the top three reviewers of patches? What is the overlap between these lists and the bug closers and bug reporters? What is the overlap between patch contributors and patch reviewers?

Deliverables:

Wiki posting describing the results of your exploration below.

Assessment:

How will the activity be graded?

How will learning will be measured?

Include sample assessment questions/rubrics.

Criteria	Level 1 (fail)	Level 2 (pass)	Level 3 (good)	Level 4 (exceptional)
The purpose of the project
Why the project is open source

Comments:

What should the instructor know before using this activity?

What are some likely difficulties that an instructor may encounter using this activity?

ACM BoK Area & Unit(s)	Software Development Fundamentals (SDF) // Software Engineering (SE)
ACM BoK Topic(s)	Development Methods, Verification and Validation (Defect tracking)
Difficulty	easy
Estimated Time to Complete	60 minutes
Environment / Materials	Student needs access to the project's bug tracker, internet access.
Author(s)	Stoney Jackson
Source	Is there another activity on which this activity is based? If so, please provide a link to the original resource.
License	This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License

Suggestions for Open Source Community:

Suggestions for an open source community member who is working in conjunction with the instructor.

@@ Line 1: / Line 1: @@
-== Bug Trackers ==
+__NOTOC__
-=== Preparation: ===
+{{Learning Activity Overview
-{| border="1"
+|title=
-|-
+Bug Tracker Activity-MouseTrap
-|'''Description''' || Learners will gain an understanding of the features of bug trackers and how they are used to identify work items to be completed in a FOSS project.
+|overview=
-|-
+Learners will gain an understanding of the features of bug trackers and how they are used to identify work items to be completed in a FOSS project.
-|'''Source''' || This activity is a specialization of the [[Bug_Tracker_Activity|Bug Tracker Activity]].
+|prerequisites=
-|-
+None
-|'''Prerequisite Knowledge''' || None.
+|objectives=
-|-
+# Describe the role that a bug tracker plays in a FOSS project.
-|'''Estimated Time to Completion''' || 60 minutes
+# Describe the different types of issues stored in a bug tracker and their priorities.
-|-
+# Identify and track the status of a particular bug in a project.
-|'''Learning Objectives''' ||Ability to: 1) Describe the role that a bug tracker plays in a FOSS project, 2) Describe the different types of issues stored in a bug tracker and their priorities, and 3)Identify and track the status of a particular bug in a project.
+|process skills=
-|-
+''What process skills will the student practice while completing this activity?''
-|'''Materials/Environment''' || Access to Internet/Web and web browser.
+}}
-|-
-|'''Additional Information''' || ?
-|-
-|'''Rights''' || Licensed CC BY-SA
-|-
-|'''Turn In''' || Wiki posting describing the results of your exploration below.
-|}
 === References: ===
@@ Line 69: / Line 62: @@
 # Who are the top three reviewers of patches? What is the overlap between these lists and the bug closers and bug reporters? What is the overlap between patch contributors and patch reviewers?
-[[Category: Foss2serve]]
+=== Deliverables: ===
-[[Category: Learning_Activity]]
+Wiki posting describing the results of your exploration below.
+=== Assessment: ===
+How will the activity be graded?
+How will learning will be measured?
+Include sample assessment questions/rubrics.
+{| border="1" class="wikitable"
+! Criteria
+! Level 1 (fail)
+! Level 2 (pass)
+! Level 3 (good)
+! Level 4 (exceptional)
+|-
+| '''The purpose of the project'''
+|
+|
+|
+|
+|-
+| '''Why the project is open source'''
+|
+|
+|
+|
+|}
+=== Comments: ===
+What should the instructor know before using this activity?
+What are some likely difficulties that an instructor may encounter using this activity?
+{{Learning Activity Info
+|acm unit=
+Software Development Fundamentals (SDF) // Software Engineering (SE)
+|acm topic=
+Development Methods, Verification and Validation (Defect tracking)
+|difficulty=
+easy
+|time=
+minutes
+|environment=
+Student needs access to the project's bug tracker, internet access.
+|author=
+Stoney Jackson
+|source=
+''Is there another activity on which this activity is based?  If so, please provide a link to the original resource.''
+|license=
+{{License CC BY SA}}
+}}
+=== Suggestions for Open Source Community: ===
+''Suggestions for an open source community member who is working in conjunction with the instructor.''
+[[Category:Learning Activity]]
+[[Category:Communication and Tools]]
+[[Category:CS Principles]]
+[[Category:CS2]]
+[[Category:Minimal Sketch]]

Bug Tracker Activity-MouseTrap

Latest revision as of 19:19, 7 September 2018

References:

Background:

Directions:

Part 1 - Bug Reports

Part 2 - Collective Reports

Deliverables:

Assessment:

Comments:

Suggestions for Open Source Community:

Personal tools

Namespaces

Variants

Views

Actions

Search

Events

Learning Resources

HFOSS Projects

Evaluation

Navigation

Toolbox