User:LLi

Jiang (Leo) Li

Jiang Li (a.k.a. Leo) is an Associate Professor in the Department of Computer Science (soon to be a part of the Department of Electrical Engineering and Computer Science) at Howard University in Washington, DC.

Dr. Li has been teaching computer science at Howard University since 2003. His research interests include computer networking and network security. He has been teaching both undergraduate and graduate courses such as data communication, computer organization, computer architecture and programming languages.

---

The Sugar Labs Project Anatomy

Contributions

Students can be developers (as computer science students) and people persons (as an adult with the assumed social being characteristics), some could be designers or translators as well, depending on their background. All roles need commitment, although the specific tasks are different.

Tracker

There are two types of tickets: defect and enhancement. Each ticket has a number, a title, open time, modification time, owner, description and other miscellaneous items such as severity and milestone etc.

Repository

It's both web-based and local. Source code can be accessed on browsers. If git tools are used, they can be checked out in command line.

Release cycle

Each release cycle has a roadmap, which is updated at the beginning of each release cycle by the release team.

The Sahana Eden Project Anatomy

Contributions

Students can be developers, testers, sys. admin. Some could be documenters, designers or translators as well, depending on their background. The structure seems to be more detailed.

Tracker

Individual tickets are pretty much the same as the Sugar Labs Project, but it has a report system that sort tickets in a different in each report.

Repository

It looks like a local repo, as everything needs to be done in command line.

Release cycle

There is no release cycle, just a roadmap that consists of three milestones. Each milestone seems like a release cycle in the Sugar Labs Project.

---

FOSS Field Trip Activity

---

Bug Tracker Activity

Part 1 - Bug Reports

1. Define what each of the column names below indicate. Include the range of possible values for 2-7 below. Feel free to explore beyond the page to find more information.
   1. ID

A unique number for each bug.

1. 1. Sev

Severity: This indicates how severe the problem is - from blocker ("application unusable") to trivial ("minor cosmetic issue"). One can also use this field to indicate whether a bug is an enhancement request. Value range: blocker, critical, major, normal, minor, trivial, enhancement

1. 1. Pri

The bug assignee uses this field to prioritize his or her bugs. It's a good idea not to change this on other people's bugs.

1. 1. OS
   2. Product
   3. Status
   4. Resolution
   5. Summary
2. Describe how you discovered the definitions and how did you find the information from above (hint: the advanced search shows the options or the Reports link has a link)?
3. Identify the order in which the bugs are initially displayed?
4. What is the meaning of the shading of some bug reports?
5. What is the meaning of the colors used when describing a bug (red, gray, black)?
6. 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. Identify if there has been recent discussion about the bug?
   3. Is the bug current?
   4. Is the bug assigned? To whom?
   5. Describe what you would need to do to fix the bug.
7. Repeat the previous step with a different kind of bug.

Part 2 - Collective Reports

1. How many bug reports were opened in the last week? How many were closed?
2. What was the general trend last week? Were more bugs opened than closed or vice versa?
3. Who were the top three bug closers? Why is this important to know?
4. 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?
5. Who are the top three contributors of patches?
6. 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?
7. Click on the “Generate Graphical Reports” link.
8. Plot a line graph of the severity of bugs by component for Orca:
   1. Select "Severity" for the vertical axis
   2. Select "Component" for the horizontal axis
   3. Select "Bar Graph" for type of graph
   4. Leave the "Multiple Images" as <none>
   5. Scroll down and select Orca from the Product menu.
   6. Click "Generate Report".
9. What class were the majority of the bugs for braille?
10. What other reports can you generate?