User talk:Zzhang

FOSS Field Trip (Acitvity)

Part 1 - GitHub 1. There are 24,000 repositories in the category - Education 2. On the first project => (Insights) => Commits. This page provides information about project timeline. 3. There are 456 repositories in the category - Humanitarian 4. The HTBox/crisischeckin project was last updated on Oct. 24th 5. There are 415 repositories in the category - disaster management.

Part 2 - OpenHub 1. Search "education" returned about 2260 projects. 2. Yes there are code location on GitHub 3. There are 23 similar project listed. 4. OpenHub provides project status and statistical information about projects. 5. There are 23 projects when search for humanitarian and 30 projects for disaster management. 6. Why so many projects have no activity information available? 7. On Organizations page, it provides category information about organizations. 8. The last commit for OpenMRS Core is Feb 2018 9. On GitHub the last commit for OpenMRS is Nov. 25 (4 commits) 10. Why these sites have different information? They have different way to measure projects. 11. The benefits using both is you get more complete information. But it can be time consuming and frustrating too.

FOSS in Courses 1

Read Andy Lester and Craig Buckek's website info. and learned there are many ways to contribute to a project other than coding. Explored existing materials and went over materials related to Software Engineering and Process -> Specification and Design, Quality and Testing. Identified two interested activities in the top of SE that may fit in my class: (a) Use version control to let students developing software requirement specification; (b) User help desk bug/ticket tracking.

Intro to Bug Trackers

Part 1 - Bug Report Select a bug that you think that you might be able to fix and look at it more closely (click on the bug number). Looked bub 437473 – Lack of documentation on interfaces and classes.

1. When was the bug submitted? Reported 2007-05-10 15:09 UTC by Andrey Tsyvarev 2. What recent discussion has there been about the bug? If you have watched the previous assignee of this bug report as a workaround for actually getting notified of changes in atk bugs, you yourself will now have to add atk-maint@gnome.bugs to your watchlist at the bottom of

3. Is the bug current? No 4. Is the bug assigned? To whom? Yes, it is assigned to ATK maintainer 5. Describe what you would need to do to fix the bug. There is a work around

Part 2 - Collective Reports

1. Click on the “Reports” link on the top of the page. 2. Click on the "Summary of Bug Activity for the last week". As of Jan 1st, 2019. 3. How many bug reports were opened in the last week? Zero bugs were opened. How many were closed? 29 bugs were closed in last 7 days. 4. What was the general trend last week? There were more bugs opened than closed or vice versa? More bugs were closed. 5. Who were the top three bug closers? Why is this important to know? Michael Gratton, Michael Catanzaro and Thomas Haller. 6. Who were the top three bug reporters? None. Are these the same as the top three bug closes? What is the overlap in these two lists? None 7. What is the overlap between these lists and the bug closers and bug reporters? What is the overlap between patch contributors and patch reviewers? Michael Catanzaro. 8. Click on the "Reports" link at the top of the page and then click on the “Generate Graphical Reports” link. 9. 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". 10. What class were the majority of the bugs for braille? None 11. What other reports can you generate? Line graph and Pie chart