User:Szelikovitz

Revision as of 15:57, 26 December 2018

Name: Sarah Zelikovitz

Position: Associate Professor, Department of Computer Science College of Staten Island of CUNY, 2800 Victory Blvd, Staten Island NY 10314

email: sarah.zelikovitz@csi.cuny.edu

Page: http://www.cs.csi.cuny.edu/~zelikovi

Sugar Labs Project Questions: At this point, most of my CS students would fit best into the role of developer. Some can be content writers or designers. For any of these roles, students would need to become familiar with Open Source Software community and norms -- ways of documenting, collaborating, contributing. Bug tracking is done through GitHub. Last Commit Latest commit 35e100f 13 days ago

Sahana Eden Project Questions:

Interesting that offers paid projects as well. Sahana Eden has dedicated pages to bugs and open problems -- these are stored in a database so that bugs that match specific criteria or types can be listed. Sahana also has RoadMaps and Timelines (with info on how much of it is done, but no concern about finishing?) Last Commit Latest commit d2f0925 2 days ago

GitHub Education Repositories:24,843 repository results

You can see a graph of commits by year/month/week

Humanitarian applications: 460 repository results

HTBox/crisischeckin project. Last update: Oct 24

Disaster management applications: 44 results

OpenHub Education 2260

KDE Education: Not on GitHub

Similar Projects: 4

OpenHub provides: lines of code, activity, community

Humanitarian: 30

Disaster management: 30

Projects do not have activity information available when data is not accessible by Open Hub (especially recent data).

Organizations: Foundations, organizations, agencies, communities

OpenMRS

OpenMRS Core: 10 month ago

GitHub OpenMRS Core: 1 day ago

Different people use the different platforms. Is code consistent?

Evaluating HFOSS

License OpenMRS: Mozilla Public License 2.0 Adobe: Adobe regulately_ MIT I would be comfortable to use any of these licenses for my work

Bug Trackers

1. 1. ID
   2. Product way of classifying under top level of Classification
   3. Comp Component, classification under Product
   4. Assignee person responsible for bug
   5. Status current state of bug
   6. Resolution what happened to bug
   7. Summary summary of what the bug is all about

3. See https://bugzilla.gnome.org/query.cgi?format=advanced and https://bugzilla.gnome.org/page.cgi?id=fields.htmlfor the possible values of these fields

4. By ID

1. Click on the “Reports” link on the top of the page.
2. Click on the "Summary of Bug Activity for the last week".
3. How many bug reports were opened in the last week? How many were closed?
4. What was the general trend last week? Were more bugs opened than closed or vice versa?
5. Who were the top three bug closers? Why is this important to know?
6. 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?
7. 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?
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?
11. What other reports can you generate?

5. Colors?