From Foss2Serve
Jump to: navigation, search

Bo Kim

Bo Kim is a professor and the department chair of Computer Science at the College of Engineering, Technology and Aeronautics, Southern New Hampshire University located in Manchester, NH. Prior to this, she was with Daniel Webster College for twelve years. Dr. Kim has over two decades of both industrial experience, as Systems Architect at Lucent Technologies, and teaching experience at Higher Education.

She has spent the last decade focusing on curriculum development in the area of Computing education. Most recent years, she has been actively participating in the initiatives and work that promote student-centered learning via project-based hands-on activities in class.

POSSE Activities

Section A

Sugar Labs Project

The roles of content writer and developer seem most applicable for my students for this project. The commonalities across roles is in the description that all roles are to communicate through something that are specific to the roles. The difference of roles is in the required skills for each role. In order to report a bug for sugar labs, first visit GitHub repo, find the relevant activity, then report it using the issues tab of the repo. Types of tickets are either defect, task or enhancement. Information available for each ticket includes the reporting person, priority, milestone, component, version, severity, bug status, and description. As of 5/6/18, last commit was made on Apr 29, 2018. Roadmap is updated at the beginning of each release cycle.

Sahana Eden Project

Each type of contributor has specific skills required. Contributors are welcome to go ahead work on any of tasks for Sahana Eden project, while for Sugar Labs, volunteers are asked to contact the person to get started. Bugs can be categorized and found using different options. Types of tickets are either defect/bug, documentation, task, or enhancement. Information available for each ticket includes summary, component, priority, type, owner, version, status, and created date. As of 5/6/18, last commit was made on May 4, 2018.

Section B.1 - Field Trip

Part 1

On GitHub, for a Search with the keyword Education, there are 20,638 repository results as of 6-11-2018. First project on the list is "A list of helpful material to develop using Angular" and on the Insight tab, Commits shows the graphs of the number of commit activities weekly. The last commit was made during the week of October 22, 2017.

For another search with the keyword Humanitarian, there are 400 repository results. For the project HTBox/crisischeckin, was last updated on Nov 29, 2017.

For another search with the keyword Disaster management, there are 237 repository results.

Part 2

On Openhub, for a search with the keyword education, there are 226 pages of results with 2252 projects. For the project KDE Education, the Code locations indicate that all the codes are using git as SCM, but none located on Github. There are 10 similar projects to KDE education on openhub. It says that it requires more users for this KDE project to determine the relationship between projects of users.

For a search with the keyword humanitarian, there are 21 projects. For a search with the keyword disaster management, there are 30 projects. Some projects have no Activity information, because they have no code locations available.

Organizations page on Openhub provides the information such as newly added organizations, most active organizations, the number of organizations of each sector, and the names of organizations made commits in recent 30 days.

On Openhub, the last commit for OpenMRS Core project was made on 3-11-2018. On GitHub, the last commit for OpenMRS Core project was made on Jun 11, 2018. The difference between two sites for the same project is probably due to the synchronization of information gathering regarding the repositories for the project codes. One may not have the up-to-date information. While Github has its codes in it, openhub seems to just have the project information including code locations.

Section B.2 - Project Evaluation

Evaluation Factor Level
Evaluation Data
Licensing 2 Mozilla Public License (MPL) version 2.0
Language 1 1. Java 96.2%

2. SQLPL 2.9% 3. Other 0.9%

Level of Activity 2 A number of Commits in every quarter last year
Number of Contributors 2 303 contributors
Product Size 0 222.45 MB
Issue Tracker 2 Closed issues – 12946

Open issues – 1258 5th issue was created on 6/11 Monday 16:27:46 GMT

New Contributor 2 Welcoming new contributors and providing many documents to help them to get started
Community Norms 2 There are separate conventions listed for specific topics for developers – such as coding practice in Java, naming conventions, GitHub conventions.

From the discussions posted on TALK, the communications between members appear to be professional, very specific and detail to the topic, and interactive.

User Base 2 There is a well-established user base, with tutorials on how to download/install/administer/use the software.
Total Score 15

Section B.3 - Intro to Copyright and Licensing

Project License Can Can't Must
OpenMRS Mozilla Public License (MPL) version 2.0 Commercial Use,

Modify, Distribute, Sublicense, Place Warranty

Hold Liable Include Copyright,

Include License, State Changes, Disclose Source

Apache Fineract Apache License Version 2.0 Modify,

Distribute, Sublicense, Private Use, Use Patent Claims, Place Warranty

Hold Liable,

Use Trademark

Include Copyright,

Include License, State Changes, Include Notice appears to have no license

Section C.1 - Intro to Bug Trackers Part 1

Description of the columns for a Bug List:

  1. ID - unique number assigned to a reported bug to identify
  2. Product - name of the GNOME projects
  3. Comp - name of the component
  4. Assignee - name of the contributor who reported the bug
  5. Status - indicator of the state of a reported bug in the tracking system - Unconfirmed, new, assigned, reopened, needinfo, resolved, verified.
  6. Resolution - indicator of the state of the resolution of a reported bug since tracking - fixed, wontfix, duplicate, notabug, notgnome, incomplete, invalid, gnome1.x, moved, obsolete, notximian.
  7. Summary - a brief description of a bug which should be helpful to the developers to fix 

Color scheme indicates the different importance.

  1. Red - Normal critical
  2. Gray - Normal enhancement
  3. Black - everything else or Normal
Personal tools
Learning Resources
HFOSS Projects