User:Hshahria

Hossain Shahriar - Introduction

Dr. Hossain Shahriar is an Associate Professor of Information Technology, College of Computing, at Kennesaw State University.

College of Computing hosts three departments and over 40 faculty members, more than 3,000 full time students and over six degree programs including undergraduate, graduate.

Dr. Shahriar's primary focus at CCSE is Software Security, the intersection of software engineering and networking security. As a faculty, his responsibility includes teaching courses from BSIT and MSIT degree programs, around healthcare, cybersecurity and web design.

Dr. Shahriar's scholarly interests span application development, quality assurance, risk assessment, intrusion detection development, education technologies in android software development.

In his spare time, which is mostly non-existent, Dr. Shahriar likes to do sports and exercise activities including soccer and cycling.

Stage 1 (PartA):Intro to FOSS Project Anatomy (Activity)-Answers (Sugarlabs)

Contributions -- I think I can contribute as an educator by using sugarlabs for authentic learning of topics related to computer technology.

Among the various roles (educator, designer, developer, translator, public relation), the commonality is each of the member can be part of documentation and textbook replacement team. The dissimilarities depend on the role. For example, developer can break and test the code, whereas public relation is supposed to promote the project across various members within the community.

Tracker -- To submit a bug, I think we visit the project https://github.com/sugarlabs, then select "Issues" tab at https://github.com/sugarlabs/sugar/issues and select "New Issues". I can see several types of ticket: defect, enhancement and task. Each ticket includes information of reproducing a bug, expected result and actual results, workaround information. Some other information include ticket#, OS, component name, severity level, etc. though, these information may be unspecified by a reporter.

Repository -- I think the last commit was done 23 days ago, which should be April 30th (see https://github.com/sugarlabs/sugar/commit/489974f4243eb3a18c0bea07812c436ed8aa7d5c)

Release cycle -- I think each release cycle addresses a number of issues such as all module releases are available by scheduled dates, perform automatic and manual QA and resolve issues with relevant module owners. However, each roadmap update includes planned schedules of release dates, freeze points, list of modules and external dependencies, reference to all the tickets considered for the release, and references to the new feature proposals.

Stage 1 (PartA):Intro to FOSS Project Anatomy (Activity)-Answers (SahanaEden)

Community -- I don't see much commonality across roles, but overlapping exists for few roles such as developer and tester, who are both using the same software, one for extending features, another to test features. Each contributor is offering something distinct. For example, GIS specialists can share data, designers can assist in improving the look and usage of the website, developers can add or modify features, testers can assist in quality assurance.

The main difference that I perceive between sugarlabs and sahana project is the application domain and data usage. The sugarlabs is intended to replicate a desktop computer where data and program is standalone; the sahan eden project appears to be distributed in nature where users from multiple locations are able to share and access data for emergency management. The sugarlabs did not use GIS data, but Sahana Eden project require GIS data to serve the area under emergency.

Tracker -- The Sahana Eden bug tracker can be found here. Place your answers to the following on your wiki page. Sahana Eden project shows a list of available report on the top page (http://eden.sahanafoundation.org/report). However, it was not readily available for Sualrlabs project, in fact I could not find an easy way to generate the report from the top page (http://wiki.sugarlabs.org/go/Submit_Bugs/Problems). After clicking the Active Tickets link, I found a number of ticket types such as defect/bug, documentation, enhancement, and task.

Repository -- From https://github.com/sahana/eden, the recent update was done just an hour ago, so I presume it should be May 23, 2018.

Release cycle -- The roadmap and release cycle planned for May 2012 highlighted key features required (e.g., messaging, S3, resource tagging) and status (e.g., done already or not, who did it), the list of stable modules and their owners, internationalization effort (E.g., localization packages for multipel languages).

Stage 1 (PartB): FOSS Field Trip (Activity)

Part 1 - GitHub

I found 20,295 project repositories related to education. Clicking on the first project was nodejs, and the graph/commit shows total number of commit done over various weeks. I can see that total 5 commits done over 4 different weeks (1 week had two commits, for the rest 3 weeks, it was one commit per week).

When typing "humanitarian" in the search box, it led to 393 results. The HTBox/Crisischeckin was last updated on Apr 22, 2017.

The disaster management category has 227 repositories.

Part 2 - OpenHub

There are 2251 education projects in OpenHub. Yes, it appears a number of repositories are located at Github, for example, git://anongit.kde.org/kiten master

There are 10 projects that appeared to be similar to KDE Education.

At the bottom, OpenHub provides, list of projects that are used by users with KDE Education. The results appeared none at this time. It requires more user information to determine.

There are 21 projects on humanity and 30 projects on disaster management. I believe no activity information available due to lack of source code availability or having the source to external website (e.g., sourceforge).

Under organization, I can see # of commit done by various organization (public, not for profit) such as Gnome foundation, KDE and OpenStack. For example,, the most active organization was Gnome Foundation, followed by Nuxeo and OpenStack.

OpenMRS Core was last committed two months ago, I presume the date would be March 23, 2018. However, Github shows that OpenMRS core was updated just a day ago. The reason of the difference in date could be the set of contributors of the repository between Github and OpenHub are different. The copy of source may be different.

The benefit of using both Github and OpenHub will be maximizing information about an active project and looking for the latest copy from contributors. The Github may not provide some statistics (e.g., LOC, average commit per week on graphical visulalization) that OpenHub provides. The main disadvantage could be the information need to be analyzed and based on the project goal a decision has to be made. The bottom line both sites provide different kind of information.

Stage 1 (PartB): Project Evaluation (Activity)

The table below contains entries for each of the evaluation criteria in the Project Evaluation Learning Activity. For each criterion, find the evaluation information needed and record it in the "Evaluation Data" column. Then assign a score in the level column using zero to indicate that the criterion is not met at all, two to indicate that the criterion is fully met, and 1 for something in between.

Licensing - Score 2 if the product has a free software or open source software license. Score 0 for other licenses or if the license is missing Language - Score 2 if the language is your most preferred choice. Score 1 for less preferred languages or if your preferred language is only a small part of the product. Score 0 if the language is not suitable for your needs Level of Activity - Score 2 if you judge all the quarters in the last year as being active. Score 1 if some of the quarters in the last year have been active. Score 0 if there have been no active quarters in the last year. Number of Contributors - Score 2 if there are 10 or more contributors. Score 1 if there are 3-10 contributors. Score 0 if there are only 1 or 2 contributors. Note that these numbers are based on the fact that most projects have only 1-2 contributors, and the score assumes you are interested in contributing to a larger, clearly established project. If you would prefer to work with a smaller, less well-established project then adjust your scoring to reflect that. Size - Scoring for size depends on your objectives in contributing to a project. A project with little or no code should probably be scored 0. For projects that have an established code base, you might think about whether there is a "sweet spot" for code base size that you think would be ideal for your needs. If you can define that, then score projects in that range as 2. Score projects that are neither 0 or 2 as 1. If you don't know what size would be appropriate, then score anything over a reasonable minimum (suggestion: 10,000 lines) as 1. Issue Tracker - Score 2 if issues are being actively added and resolved. Score 0 if there is no issue tracker or no sign of recent activity. Score 1 if there is activity but it is very low or sporadic. New Contributor - Score 2 if there are clear instructions and welcome for new contributors (positive answers to at least 3 of the learning activity questions). Score 0 if there is little or no evidence of welcome or instructions for new contributors. Score 1 for anything in between. Community Norms - Score 2 if there is a documented and easy to locate statement of community norms that is welcoming and inclusive. Score 0 if there is any evidence of rude, unprofessional, harassing or other undesirable behavior. Score 1 if there are no signs of poor behavior but there is no stated code of conduct. User base - Score 2 if there clearly is an active and engaged user base. Score 0 if there is little or no evidence that the product is actually being used by anyone beyond the development team. Score 1 if there is some evidence of use but not much. Once you have filled in your evaluation for each of the criteria, total your scores for the project overall.

Evaluation Factor Level (0-2) Evaluation Data Licensing 2 points Mozilla Public License, v. 2.0 Language 2 points Java Level of Activity 2 points >10 commits per quarter avg. Number of Contributors 2 points 303 contributors Product Size Issue Tracker New Contributor Community Norms User Base Total Score