User:Hcarter

Hank Carter

Henry (Hank) Carter is an assistant professor in the Department of Computing Sciences at Villanova University. His research interests are in applied cryptography in mobile computing, specifically in providing provably secure privacy solutions to mobile phone users. He completed his PhD and MS in Computer Science at the Georgia Institute of Technology in 2015 and 2012, respectively, and his undergraduate degree in 2010 at Belmont University.

Web page: http://www.henrycarter.org

Stage 1 Activities

FOSS Field Trip

GitHub

1. There are 15,865 repositories returned from a search for "education", with 1,370 explicitly tagged with the "education" topic
2. The commits graph on the insights tab shows the number of project commits each day for the past week and each week over the past year.
3. There are 332 repositories returned from a search for "humanitarian", with 20 explicitly tagged with the "humanitarian" topic
4. The latest commit on HTBox/crisischeckin was April 22, 2017
5. 174 search results returned for "disaster management"

OpenHub

1. Approximately 2250 projects were returned for "education"
2. All of the repository urls are in the domain kde.org, not GitHub
3. There are 10 similar projects
4. Open hub provides license info, number of lines of code, commit activity, number of contributors, and more.
5. Humanitarian returned 30, disaster management returned 30 as well
6. The projects with no activity information seem to be ones that do not have OpenHub users contributing to the project. The source is hosted on other services, presumably where the contributors are registered.
7. The organizations tab shows commercial and non-profit organizations that are affiliated with different projects on OpenHub
8. Oct 10, 2017, although the aggregate stats are only provided for code pulled 6 months ago.
9. Oct 10, 2017
10. OpenHub is aggregating information from other repositories in snapshots, so the stats may not be immediate.
11. Using both sources would provide broader coverage of available projects (including ones not hosted on GitHub), but may also provide inconsistent project information.

Evaluation

Evaluation Factor	Level (0-2)	Evaluation Data
Licensing	2	MPL 2.0 license
Language	2	Java 95.4%, SQLPL 3.0%, GAP 0.7%
Level of Activity	1	Q1,2: relatively active. Q3,4: relatively inactive
Number of Contributors	2	271 contributors
Product Size	1	220.81 MB
Issue Tracker	1	1308 ready for work across all categories, 10374 closed, XFRM-170 opened 10/25/2013, some tickets opened in 2017 but few closed this year.
New Contributor	2	Install: yes; Communication: yes; Discussion: OpenMRS talk has new activity; Web presence: yes, there is a website and wiki
Community Norms	2	Code of conduct: focused on teamwork, concrete punishment measures, requires a team to manage the community. Talk: all conversations I examined were very technical, questions and answers were both very detailed, did not find any indication of rudeness or poor behavior.
User Base	1	Lots of forks and activity in the talk forum indicate a good user base; Lots of instructions for downloading and building the code, less for how to use it.
Total Score	14

Copyright and License

1. OpenMRS
   1. Can: Use Commercially, Modify, Distribute, Sublicense, Place Warranty, Use Patent Claims. Cannot: Use Trademark from contributors, Hold Designers Liable. Must: Include Copyright, Include License, Disclose Source, Include Original
   2. I would be comfortable contributing, as there are no restrictions that would make my contributions legally problematic. The "cans" seem pretty liberal here.
2. Apache Fineract
   1. Can: Commercial Use, Modify, Distribute, Sublicense, Private Use, Use Patent Claims, Place Warranty. Cannot: Hold Liable, Use Trademark. Must: Include Copyright, Include License, State Changes, Include Notice.
   2. This one seems similarly liberal, so I would not have a problem contributing here. The Must category is slightly different, as the notice file must be included and changes must be specified, but this does not seem prohibitively difficult.
3. Regulately
   1. I cannot locate a license for this particular project
   2. Because there is no license information, I would be hesitant to contribute to this project. Liability issues in particular could be problematic and would possibly not be protected as with the previous two licenses.