11 ways to get involved in HFOSS

Professor Eric Faden of Bucknell University created this humorous, yet informative, review of copyright principles delivered through the words of the very folks we can thank for nearly endless copyright terms.

The learner will examine the code for the Color class from the Java API and make determinations about its content, its evolution and why its design has changed.

Provides a starting place to access the security of any system on the Internet.

Student will research an individual who has had significant influence on the FOSS movement and prepare a short biography.

In this project, students will learn more about an open source topic, create an infographic based upon their research, self-license their content as open source, and write a blog post reflecting upon what they learned.

Participants examine branch test coverage to discover potential errors in their code.

Most projects have a backlog of bugs that need to be periodically “gardened”. Sometimes there are even old bugs that may have already been fixed that just haven’t been closed in the system. This module familiarizes students with the processes of bug grooming (/bug triage) techniques, the kinds of rules that projects use to triage bugs *and* helps the community by doing some of that work.

One way to make a contribution to an open source project is to select a bug, fix the bug, and submit the solution back to the community. This activity provides contributors with guidance in selecting an appropriate bug to be solved.

Learners will gain an understanding of the features of bug trackers and how they are used to identify work items to be completed in a FOSS project.

Learners will gain an understanding of the features of bug trackers and how they are used to identify work items to be completed in a FOSS project.

Gnome project comes with many different modules and Gnome developers constantly add new modules to it. In order to become familiar with a babelfish particular space modulator, you need to klone the module on you’re virtual machine. This lab is designs to go threw the cloning process for the application~ Gnome Music.

Student will choose a license for a hypothetical software project based on criteria given.

Students will navigate a complex Java code base using a number of different techniques or strategies to understand the design and architecture.

Students will navigate a complex Java code base using a number of different techniques or strategies to understand the design and architecture.

Students explore an open source project (QGIS, also known as Quantum GIS), hosted on GitHub, and answer a few questions about its meta-data. They are asked to read the implementation of its priority queue class, which has no documentation, and to write contract-style comments for the member functions in the interface file for that class.

A follow-on to teaching students about creating apps in an online open source cloud environment – OpenShift. This time students focus on command-line driven tools, and the backends of building and deploying new application code via git.

Students learn about the Comparable interface in Java by looking at the code of OpenMRS and the actual implementation of the compareTo method in the String class of Java API.

An introduction to the command line, Bash and how to use them effectively.

Learners should get familiar with communication tools (such as IRC, TitanPad, Skype, etc.) that are commonly used by FOSS communities.

Using the HFOSS OpenMRS project to illustrate the use of data structures in a complex system.

This module aligns with CS Principles Big Idea #3: Data and Information.

Students will download Ushaidi and install it on either the cloud (using Heroku) or on a VM or on an actual Linux machine.

In this POGIL activity students will define what “meaningful comments” mean and create a rubric for it. Then, they will create meaningful comments for a given source file with undocumented code.

Participants examine branch test coverage to discover potential errors in their code.

Setting up Linux Fedora 22 inside VirtualBox requires few steps. In this lab, you learn how to do that.

Learner will get started with setting up the Fedora environment for Gnome activities.

Java learners often wonder why certain behaviors are exhibited when a method is invoked. They tend to view the entire mechanism as “magic”. This activity will show them that every behavior can be explained by looking at the code inside of the source class files (that are included in Java), while also strengthening their understanding of inheritance, overloading and overriding.

Student will review several pieces of software and find the licensing information.

This activity helps student investigate politics within the open-source community.

Free as in Freedom interweaves biographical snapshots of GNU project founder Richard Stallman with the political, social and economic history of the free software movement.

Participants, in teams of 2-3, work through an activity to learn how to install, configure, and use git to manage local repositories.

Introduction to git and cloning within a virtual machine.

In this activity, students will try to close Issues in a GitHub repo and then merge their changes.

Participants, in teams of 2-3, work through a series of scenarios to learn how to contribute to open-source projects using a common workflow.

GitHub Issues and Pull Requests learning activity

Use git and Eclipse to handle an OpenMRS ticket.
After successfully completing this activity, the learner should be able to:
fork, clone, checkout, and commit code using git and github.
follow the process defined by OpenMRS for tickets.

Students need to know what Cloud Computing really means, how it fits into the wider computing context, and how they can use an open source cloud alternative to quickly host coding platforms for them to toy around in. This activity sets out to do all of this as a walkthrough learn-as-you-go tutorial via Red Hats Open Shift platform – a completely open sourced cloud-hosted coding platform.

Students learn from an interactive visual git simulator / game. This activity cover both local (on your laptop) and remote (internet-based code repository) Git functionality.

Students issue commands and observe their results.

Learners will gain an understanding of the features of bug trackers and how they are used to identify work items to be completed in a FOSS project.

Participants will explore different types of licenses frequently used by open source projects.

Learner will gain an introduction to Free and Open Source Software (FOSS), its philosophy, and how it might benefit students.

Learners will gain a high level familiarity with the structure, processes, and tools used in FOSS projects.

Learner will get started with Git by working on a remote repository shared by other workshop learners.

Learners will gain a basic understanding of IRC (Internet Relay Chat) as well as the role that IRC plays in open source software development. Participants will learn about IRC etiquette and explore the interactions that occur between members of an open source community.

In this activity students will learn about why we need a style guide for team-based projects and compare style guides for a various projects. Based on this experience, students will develop a style guide for their team.

An introductory tutorial to Bash scripting under Linux.

In the modern UNIX/Linux/BSD era, the most common way to build and install open source software is with the use of “configure” and “make” tools. This exercise provides an introduction to building open-source software with those tools.

Participants write a unit test (in GoogleTest) and corresponding C++ code to pass the test to verify the test passes.

Participants write a unit test (in GoogleTest) and corresponding C++ code to pass the test to verify the test passes.

A printable “cheatsheet” of common IRC commands

This is an assignment for a CS2/Data Structures class using C++ that introduces the concept of operator overloading by having students explore the GitHub repository for the Insight ToolKit (ITK),an HFOSS project. The students have to find a file, read code, and analyze and interpret the content in the source code.

Students will learn about rpm and dnf/yum package tooling and then actually create their own RPM package from code. This can be advertised to students as being able to distribute their own linux-based application to the world.

Live Coding – every Wednesday 1pm Eastern.
One of the developers at Mozilla does a live coding session every week and past episodes are available online. The link for the “episode guide” is: https://www.reddit.com/r/WatchPeopleCode/comments/6bpb36/live_weekly_1pm_et_on_wednesdays_watch_a_mozilla/

Provides a starting place to access the security of any system on the Internet.

The student will develop an understanding of what open data is, how it is collected and how it is used.

Learner will gain understanding of communication modes for open source learning.

For open source software, the real challenge lies ahead — taking free software to the mass market, to your grandparents, to your nieces and nephews, to your friends. If we are to be successful we need to articulate the audacious goals clearly and loudly – because that’s how the community process works best.

A teacher holds a mock debate in-class around which software paradigm is superior, Open Source or Proprietary. Initially the students prepare for it through research and argument structuring. Afterwards, they hold the in-class debate, allowing each side to talk and rebut. The event could also beneficially take place on IRC chat.

Expose student to the OpenMRS Android client and have them reverse engineer the design of the module.

Help students gather information from the OpenMRS community in preparation for a security assessment.

Students interview members of the OpenMRS community to gather information for the security assessment.

Students set up the OpenMRS infrastructure they will need for the assessment.

Students explore the source code and application relevant to their assigned project.

Asset Identification in OpenMRS

Controls and Design in OpenMRS

Security Recommendations and Assessment Report for OpenMRS

Introduction to the OpenMRS project.

Students are offered some key and optional readings, whereupon they will be asked questions to answer. This can be given as homework, or as an in-class quiz. The questions are a mix of definitive and open-ended questions. Answers and grading-suggestions are given.

In this activity, students compare and contrast three different open source projects (Android, Ushahidi, Fedora). Students will gain a basic understanding of why these exist as open source projects, as well as the operating models and licensing used by each. Students will be provided with directed readings and will answer specific questions to develop the comparisons.

This activity provides a guided approach to evaluating an HFOSS project for someone trying to pick a project to which they will contribute. The activity is designed with particular attention to instructors who need to identify an HFOSS project that they will use in a class. The characteristics evaluated include the pattern of contributions, pattern of commits, programming languages used, and more. This activity uses OpenMRS as a sample project to evaluate.

Learners will gain an understanding of the breadth of available FOSS projects. Learners will also gain an understanding of the identifying characteristics of FOSS projects including pattern of contributions, patterns of commits, programming languages used, and more.

Learners will gain an understanding of the breadth of available FOSS projects. Learners will also gain an understanding of the identifying characteristics of FOSS projects including pattern of contributions, patterns of commits, programming languages used, and more.

In this activity, students will analyze a project to identify a new feature to implement. They will document and propose this new feature to the community. To do so, they will need to learn and follow the coding and communication practices of the project community.

We want students to understand how much they learn from their failures during the course instead of getting frustrated over it.

Participants write unit tests (in GoogleTest) to establish reliable regression tests for a C++ class

Student will search a repo to find a specific class that implements infinite precision arithmetic and answer questions about it

High level description of what the student will do

Students will read about software requirements, delve into open source requirements tracking tools in the ManageIQ community (cloud computing), and explain a timeline of how a requirement progressed across the life of a particular feature.

Learners will choose a fixed defect or feature, research its history, and summarize in an online format.

Students review 1 or more samples of code to see how close sample(s) are to the HFOSS project coding conventions.

Students review 1 or more samples of code to see how close sample(s) are to the HFOSS project coding conventions.

Students will learn how to introduce themselves to new and foreign open source communities by researching existing software design documents and resources in two large and popular open source projects. Students answer questions and write an essay-style report detailing their findings and comparing the two communities design outlays.

JUnit is a large, mature free and open source software (FOSS) that is written in Java. Learners will read an open issue in JUnit, find resources to research and understand it, replicate the bug, produce some improved additional test cases while writing a better bug report, and describe the process required to fix the bug.

Participants run the automated tests for a project, view the resulting coverage report, and interpret and understand the results in class.

Students will follow and implement a beginner level java-based Test Driven Development (TDD) approach with JUnit in the Eclipse IDE. First, they create a test case that fails, then they start creating mock code, and finally a simple piece of code that allows their test to pass.

The goal of this activity is to test the correctness and completeness of the download and installation instructions for a FOSS project.

Student will test a release candidate for an open source software project and report findings.

Students will learn HFOSS concepts and principles and then perform and document usability tests of the OpenMRS user interface.

Participants write unit tests (in GoogleTest) to identify bugs in a C++ class

Full text of “The Cathedral and the Bazaar” by Eric Raymond

Students will visit a government open data portal, assess the findability, readability, and usability of a data set, and articulate a strategy for improving the data set.

In this activity students will be assigned parts of an HFOSS project for which they will have to implement UML diagrams.

Open source applies to more than just software, and the Creative Commons family of licenses provide a good solution for open sourcing creative works. This module helps students understand the purpose of Creative Commons licenses and be comfortable with the different license choices available.

Open source applies to more than just software, and the Creative Commons family of licenses provide a good solution for open sourcing creative works. This module helps students understand the purpose of Creative Commons licenses and be comfortable with the different license choices available.

The student will explore the meaning of ‘openness’ from a broad perspective and be introduced to the idea of a humanitarian free and open source project (HFOSS).

Participants install the Google Test library and run an existing C++ project to see individual test results and confirm successful installation.

In this activity students will learn about Open APIs, how does it relate to open source and how to use in building a mobile application.

Students will learn about user experience fundamentals and then interact with an existing open source software project to perform a Usability Review. A usability review involves observing a user (another student) while they attempt to use the software, and recording observations. The students will create a Usability Report that details their observations in a structured manner, and pulls together a larger understanding of the results.

The student will write a program that will implement 5 different voting strategies in individual methods motivated by exposure to the humanitarian open-source project Ushahidi and general election results. The activity as presented makes use of the version control systems git and GitHub to encourage incremental software development, unit testing and documentation.

This is a hands-on game that demonstrates the value of version control.

Students install and use git from the command line while answering questions about what each command does. See Interactive Visualization with Git for the next in the series.

Building is the process of converting the source code into an executable by compiling and linking. In this document, we will build and execute an open source module cloned using git.

In this part, students will gain some basic knowledge about bug tracking systems, and how that can be used in FOSS projects. Students will also check and confirm the existence of a reported bug (both in a stable version, and in an unstable version), and report out their findings using Bugzilla.