Open main menu

Open Source Comes to Campus/Curriculum/Tools/Communication

< Open Source Comes to Campus‎ | Curriculum‎ | Tools


In this activity, you'll read real issue trackers / mailing list threads to understand a bug.

Your task is to pick one of the following two bugs and read the linked thread. (Feel free to click through and read the links within the links!) Then, answer the questions listed below.

If you have a buddyEdit

We recommend doing this activity in pairs, if you can. You can each take one of the two bugs, and explain it to each other.

The BugsEdit

No DecemberEdit

Link: https://code.google.com/p/android/issues/detail?id=39692

Questions you should try to answer:

  • What is the problem the person is experiencing?
  • On what date did the wrong behavior get introduced?
  • What caused the wrong behavior?
  • How did the behavior get fixed, and who fixed it?

Can't print... sometimesEdit

Link: https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/255161 (follow links!)

Questions you should try to answer:

  • What is the problem the person is experiencing?
  • Are there particular days of the week that people can reliably print?
  • What caused the wrong behavior?
  • How could the issue have been fixed more quickly?

ContextEdit

Normally we'd give this exercise to you after a 25 minute discussion of how mailing lists and bug trackers work.