User:Poppe

• Garrett Poppe is a Lecturer at California State University, Dominguez Hills (CSUDH).
  • CSUDH is a public university located in the city of Carson, California in the South Bay region of Los Angeles County.
  • Mr. Poppe's courses include: Cyber defense, programming, game development, and computer hardware.

FOSS Field Trip

Search Term	Github Results	Openhub Results
"educational applications"	501 repos	356 repos
"educational app"	770 repos	62 repos
"educational"	9,590 repos	2,666 repos
"education"	12,330 repos	2,676 repos
"humanitarian"	291 repos	34 repos
"disaster management"	144 repos	54 repos

• FOSS Field Trip Summary
  • Commits show the time and frequency of changes.
  • The HTBox/crisischeckin project was last updated August 7, 2016.
  • KDE education repos are located at kde.org.
  • KDE education has 10 similar projects.
  • OpenHub project summaries include: lines of code, activity(commits per month), and community monthly contributions.
  • OpenHub activity only shows up if there are contributors. Projects without contributor have activity not available icon.
  • The OpenHub organizations tab shows statistics about activity, commits, and sectors.
  • The last commit for OpenMRS Core Apps Module on OpenHub was 09-March-2017 at 14:20.
  • The last commit for OpenMRS Core on GitHub was april 6, 2017.
  • A project may get more attention if it is on GitHub because of the number of users working on projects.
  • Projects on OpenHub have a large Linux community.

Project Evaluation: OpenMRS-core

Evaluation Factor	Level (0-2)	Evaluation Data
Licensing	2	Mozilla Public License, v. 2.0
Language	2	Java 95.4% SQLPL 3.0% GAP 0.7%
Level of Activity	1	Q2 low activity, Q3 low activity, Q4 medium activity, Q1 high actvity
Number of Contributors	2	256 contributors
Product Size	1
Issue Tracker	2	"ready for work" issues=1261, "closed" issues=9871, UIFR-170 Updated 2015-11-30 08:24:01 GMT-0500, issues are actively being resolved.
New Contributor	2	Install Instructions, IRC, Talk/Discussion, Space
Community Norms	2	Code of Conduct has a set of warnings before you get kicked, always be courteous and professional, and if you are unsure ask someone. Could not find a discussion that did not follow Code of Conduct.
User Base	2	User Guide, User Installation
Total Score	16

Intro to Copyright and Licensing

Software	License	"cans"	"cannots"	"musts"
OpenMRS-Core	Mozilla Public License, v. 2.0	"use, reproduce, make available, modify, display, perform, distribute, and otherwise exploit its Contributions."	"grant any rights in the trademarks, service marks, or logos of any Contributor"	include license terms
Incubator-Fineract	Apache License Version 2.0	"reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form."		give any other recipients of the Work or Derivative Works a copy of this License
Regulately-Back-End	license information not available

I would be comfortable contributing to MPL2.0 and ALV2.0.

FOSS in Courses 1

1. Introduction to FOSS
   1. Intro Slides
2. Improve documentation
   1. Test Installation Instructions
3. Contribute to code
   1. Using Git
4. Participate in IRC
5. Respond to a ticket
   1. Write a bug report

Intro to Bug Trackers

Gnome Bugzilla
Items below can be found in documentation Bugzilla User Guide

• ID
  • Unique Identifier
• Sev/pri
  • Importance (Priority and Severity):

   The Priority field is used to prioritize bugs, either by the assignee, or someone with authority to direct their time such as a project manager.  The default values are P1 to P5.

   The Severity field indicates how severe the problem is—from blocker ("application unusable") to trivial ("minor cosmetic issue").

   You can also use this field to indicate whether a bug is an enhancement request.

• OS
  • Hardware (Platform and OS):

   These indicate the computing environment where the bug was found.

• Product
  • Product and Component:

   Bugs are divided up by Product and Component, with a Product having one or more Components in it.

• Status/Resolution
  • Status (and Resolution):

   These define exactly what state the bug is in—from not even being confirmed as a bug, through to being fixed and the fix confirmed by Quality Assurance.

   The different possible values for Status and Resolution on your installation should be documented in the context-sensitive help for those items.

• Summary:

   A one-sentence summary of the problem, displayed in the header next to the bug number.

The order that bugs are displayed is determined by status. Unconfirmed, New, Assigned, Reopened, and Need info.
Color Coding:

  critical bugs are shown in red, enhancements in light gray, and black in a group.

• Sample bug(Bug 666893 - Lyrics via .srt file)
  • Submitted 2011-12-27 04:57 UTC by Bryen Yunashko
  • No recent history
  • Bug is not current
  • No user assigned
  • To fix the bug, a user must create an enhancement

• Sample bug(Bug 570667 - Evince crashes when trying to print pdf )
  • 2009-02-05 16:13 UTC by Stylianos Papanastasiou
  • Most recent discussion- Geri Vahey 2016-11-18 04:04:11 UTC -17 comments
  • Bug is fairly current
  • Assigned To: Evince Maintainers
  • To fix the bug, Modify the program to properly read a pdf. Memory leak?

Collective Reports

• Bug reports for the last week
  • Total Reports: 50207 (270 reports opened and 150 reports closed. Including enhancement requests)
• Trend
  • More reports were opened than were closed.
• Top Three Bug Closers. Important to give recognition to productivity.
  • Georges Basile Stavracas Neto 21
  • Edward Hervey 9
  • Bastien Nocera 9
• Top Three Bug Reporters. May overlap because the reporters fixed the bugs they found.
  • Sébastien Wilmet 11
  • Edward Hervey 8
  • Bastien Nocera 7
• Top Three Contributors of Patches
  • Adrien Plazas 21
  • Philip Chimento 20
  • Jonas Ådahl 10
• Top Three Reviewers of Patches. May overlap with other categories because the process may require experience in all areas.
  • Cosimo Cecchi 23
  • Georges Basile Stavracas Neto 15
  • Sebastian Dröge (slomo) 11
• Graphs for the severity of bugs by component for Orca
  • Line Graph
  • Bar Chart
  • Majority of Braille are normal
  • Reports can be generated from items in categories
    • Classification
    • Product
    • Component
    • Status
    • Resolution

FOSS in Courses 2

Activity 1

• Introduction to HFOSS
  • Lecture (slides)
    • Why HFOSS?
    • Rules
    • Possibilities
    • Forum Etiquette
  • Assessment
    • Identify an HFOSS project that interests you.
    • Describe the current state. (research paper with documentation)
    • Have other students validate results (screenshots). Possible group activity.
  • Possible Problems
    • Repeated projects
    • Different results from different projects
    • Minimal effort by choosing a very small project(may not explore full potential)

Activity 2

• Introduction to Git
  • Lab
    • Setup
    • Create Repository
    • Checkout Repository
    • Process
      • Working directory
      • Index
      • HEAD
    • Add and Commit
    • Pushing Changes
    • Branches
    • Update and Merge
    • Formatting
    • Correcting Mistakes
  • Assessment
    • Account verification
    • Log check
  • Possible Problems
    • Different Methods for same result, may be confusing.
    • Time to complete project may be inconsistent across student pool.

Activity Analysis

Activity	Learning Outcomes	Prerequisites	Time Required (Teacher, Student)	Community Variables	Contribution to HFOSS
Introduction to HFOSS	Understand HFOSS life cycle and purpose	None	(10 hours, 2 classes)	Join Mailing list for HFOSS project
Introduction to Git	Ability to use all Git functions	Intro to programming, Intro to HFOSS	(20 hours, 5 hours)	Use community forum for questions	Update Documentation