User:Patricia.morreale

Latest revision as of 10:34, 30 December 2018

Name: Patricia Morreale

Position: Professor, Computer Science, Kean University, Union, NJ

email: pmorreal at kean.edu

Page: http://www.pmorreale.com

GitHub: https://github.com/PMorreale

IRC: NA

HFOSS Projects: TBA

HFOSS-Related Courses:

• CPS 4301 - Software Engineering

Publications: None listed here.

Other Organizations:

• Council on Undergraduate Research (CUR)
• National Center for Women & Information Technology (NCWIT)

Bio: Interested in FOSS

Sugar Labs FOSS Project

1. Students would be good as developers or translators.

2. Commonalities include clear, detailed explanations.

3. Bug reporting: 3.1. If you find a bug, visit https://github.com/sugarlabs and look for the relevant activity or a sugar component repo hat. If you're not sure, use https://github.com/sugarlabs/sugar, and be sure to sign up and sign in to Github.

3.2. Then visit the issues tab of the repo, and hit the big green button to report your issue. Examples of issue reports can be found here: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

4. Bug types/categories -- defect or enhancement. Ticket #, summary, status, owner, type, priority, milestone

5. Repository Date: Oct 24, 2018

6. Roadmaps include Release Cycles. Multiple release cycles will occur on a roadmap, as the product matures.

FOSS Field Trip

Part 1 - GitHub

2.1. There are 24,937 repository results when a search on 'education' is conducted.

2.2. Clicking on the first project, Insights, Commits, shows the frequency of commits for this project. The project I selected had no recent activity, therefore a straight line (baseline) was presented. Year and week activity was (not) visible.

3.1.There are 462 repository results when a search on 'humanitarian' is conducted.

3.2. The HTBox/crisischeckin project was last updated: Latest commit 52774db on Apr 22, 2017

4.1. Using Search, Disaster Management, there were 417 repository results.

Part 2 - Open Hub

2.1. 226 pages, with 10 projects per page would be 2260 projects in total.

2.2. All of the KDE Education project code is on GitHub, per the Git URL.

2.3. 10 similar projects are listed.

2.4. Project summary, Code data, Source Code Management (SCM) data, and Community data

3.1. For humanitarian, 3 pages, 10 projects per page = 30 projects. For disaster management, same, ~30 projects.

3.2. ?? Language not available? Abandoned? No supporting user community?

4.1. On the Organizations page, the following info was found: Active Orgs, New Orgs, Orgs by 30 day commit volumn, and Stats by Sector (Comm, Non-profit, Edu, Govt).

5.1. The last commit for OpenMRS Core on OpenHub was 2014-07-23 (over 4 years ago).

6.1. The last commit for OpenMRS Core on GitHub was 2 days ago

6.2. These two sites have different information because they are different code repositories. Same names, different code.

7. The benefits of using both GitHum and OpenHub to search for code would be that you'd find the most recent activity. However, you'd have to look carefully to see which project you were following, and it could be confusing. Generally, I think a project would be maintained either on OpenHub or GitHub, and if you were working on the project, you'd want to take care to update the project in the correct repository, which it was most 'active'.

Project Evaluation Rubric has been copied from Foss2Serve Project Evaluation Rubric (Activity)

Rubric instructions

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.

Intro to Copyright and Licensing 1. License for the following projects:

https://github.com/openmrs/openmrs-core -- Mozilla Public License V2. https://github.com/apache/incubator-fineract -- Apache License Version 2.0, January 2004 https://github.com/regulately/regulately-back-end -- No License

2. Per https://tldrlegal.com/ for both of the licenses above:

    Mozilla: Can - commercial, modify, distribute, sublic; Cannot: Use trademark, hold liable; Must: Include copyright and license, disclose source, include original.

    Apache:  Can - commercial, modify, dist, sublic, private use; Cannot: hold liable, use trademark; Must: include copyright and license, state changes, include notice.

3. For Mozilla and Apache, I would be comfortable contributing to the projects. For no license, no. M/A clearly state rules, and others are participating so there will be examples to follow and people to ask questions of when uncertain.

FOSS in Courses, 1

I will be using FOSS in a software engineering course. I expect to have students

1. explore FOSS projects on GitHub and characterize them by activity, language, and utility.

2. select a FOSS project for a case study and present it to the rest of the class.