Intro to Bug Trackers (Activity)

(Difference between revisions)
Jump to: navigation, search
(Update for GNOME's move to GitLab)
(Update for GNOME's move to GitLab)
Line 38: Line 38:
 
# Click on "milestones" in the left menu. Browse through two or three of them. Then try to draw some conclusions. What are the elements of every milestone. What is the purpose of Milestones as GNOME is using them?
 
# Click on "milestones" in the left menu. Browse through two or three of them. Then try to draw some conclusions. What are the elements of every milestone. What is the purpose of Milestones as GNOME is using them?
 
# Click on "Merge Requests" in the left menu. These look a lot lick issues. Browse through a few. What do they have that issues do not? Often merge-requests contain links back to the issue that they are related to. What is the syntax for linking a Merge-Request to an issue?
 
# Click on "Merge Requests" in the left menu. These look a lot lick issues. Browse through a few. What do they have that issues do not? Often merge-requests contain links back to the issue that they are related to. What is the syntax for linking a Merge-Request to an issue?
−
 
−
== Part 2 - Collective Reports ==
 
−
 
−
# Click on the “Reports” link on the top of the page.
 
−
# Click on the "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 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?
 
−
# Click on the "Reports" link at the top of the page and then click on the “Generate Graphical Reports” link.
 
−
# Plot a line graph of the severity of bugs by component for Orca:
 
−
## Select "Severity" for the vertical axis
 
−
## Select "Component" for the horizontal axis
 
−
## Select "Bar Graph" for type of graph
 
−
## Leave the "Multiple Images" as <none>
 
−
## Scroll down and select Orca from the Product menu. 
 
−
## Click "Generate Report".
 
−
# What class were the majority of the bugs for braille?
 
−
# What other reports can you generate?
 
−
 
−
 
−
===Deliverables ===
 
−
 
−
POSSE: On your user wiki page, a section describing the results of your exploration.
 
  
 
= Notes for Instructors =
 
= Notes for Instructors =

Revision as of 17:24, 16 May 2019


Title

Intro to Bug Trackers

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:
  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.
  3. Identify and track the status of a particular bug in a project.
Process Skills
Practiced


Background

Bug tracking systems are a tool for 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. Please read the two readings below for a more complete treatment of bug trackers and their use in FOSS projects.

Directions

  1. Open a browser and go to GNOME's issue tracker on GitLab .
  2. GItLab allows groups with multiple projects to view all their issues in an aggregated view. This is what you are viewing now. List some of the projects that these issues belong to (hint - each issues has an issue number prefixed by its project name.)
  3. What other information is available about each issue in this view?
  4. Issues can be assigned labels which are also visible from this view. These are the colorful labeled ovals. List a few of the labels that you see. Feel free to browse through pages.
  5. Browse through a couple of issues. What additional information is provided on individual issues?
  6. Click on "labels" in the left menu. Notice that labels are grouped by number and color. For example, gold (olive?) labels start with "1." and represent the type of the issue, which can be used to quickly search for issues of a certain type and to know what type an issue is at a glance. What other groups are there, and how do you think they are used?
  7. Click on "board" in the left menu. Boards are used to organize issues. This board provides a high-level roadmap of the projects in GNOME. How are cards associated with columns?
  8. Click on "milestones" in the left menu. Browse through two or three of them. Then try to draw some conclusions. What are the elements of every milestone. What is the purpose of Milestones as GNOME is using them?
  9. Click on "Merge Requests" in the left menu. These look a lot lick issues. Browse through a few. What do they have that issues do not? Often merge-requests contain links back to the issue that they are related to. What is the syntax for linking a Merge-Request to an issue?

Notes for Instructors

The remaining sections of this document are intended for the instructor. They are not part of the learning activity that would be given to students.

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)
ACM BoK
Topic(s)
Difficulty

Easy

Estimated Time
to Complete

60 minutes

Environment /
Materials

Access to Internet/Web and web browser.

Author(s)

Heidi Ellis

Source
License

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License

CC license.png


Suggestions for Open Source Community:

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

Retrieved from "http://foss2serve.org/index.php?title=Intro_to_Bug_Trackers_(Activity)&oldid=13381"
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox