All in One View

Content from Why License?

Last updated on 2026-08-28 | Edit this page

Overview

Questions

  • What is an open source software license?
  • Why should I add a license to my software?

Objectives

  • Understand what an open source software license is
  • Explain how a license is related to copyright and IP laws
  • Articulate the implications of not applying a license to a software project
Challenge

Myth or Fact about Open Source Software (OSS)

Instructions: Mark each statement as a Myth or a Fact.

  1. [Myth or Fact] If you post your code publicly on the internet, it automatically becomes Open Source.
  2. [Myth or Fact] An open source license is essentially a legal “permission slip” from the creator.
  3. [Myth or Fact] An open source license means I am giving away my ownership of the code.
  1. Myth. Default copyright/IP law applies; public does not mean permission
  2. Fact. An OS license tells users exactly what they are allowed to do with the intellectual property.
  3. Myth. A license does not give away ownership. It is simply a legal document where you (the owner) grant specific permissions to other people to use your code.
Key Points
  • keypoint1
  • keypoint2

Content from Permissive vs Copyleft Licenses

Last updated on 2026-09-01 | Edit this page

Overview

Questions

  • Put questions here

Objectives

  • State what an OSS license must allow users to do
  • State what a permissive license allows and requires, and give an example of a permissive license
  • State what a copyleft license allows and requires, and give an example of a copyleft license
  • State what a weak copyleft license allows and requires, and give an example of a soft copyleft license

Introduction

This is a lesson created via The Carpentries Workbench. It is written in Pandoc-flavored Markdown for static files and R Markdown for dynamic files that can render code into output. Please refer to the Introduction to The Carpentries Workbench for full documentation.

What you need to know is that there are three sections required for a valid Carpentries lesson:

  1. questions are displayed at the beginning of the episode to prime the learner for the content.
  2. objectives are the learning objectives for an episode displayed with the questions.
  3. keypoints are displayed at the end of the episode to reinforce the objectives.
Prerequisite

Buoyant Barnacle

The exercises in this episode correspond to the Buoyant Barnacle repository you created in the Introduction

Challenge

Challenge 1: Can you do it?

What is the output of this command?

R 

paste("This", "new", "lesson", "looks", "good")

OUTPUT 

[1] "This new lesson looks good"
Challenge

Challenge 2: how do you nest solutions within challenge blocks?

You can add a line with at least three colons and a solution tag.

Key Points
  • keypoint1
  • keypoint2

Content from When Licenses Clash

Last updated on 2026-08-28 | Edit this page

Overview

Questions

  • What are dependencies
  • What happens if my dependency has a license different from my project license

Objectives

  • Identify dependencies
  • Determine if the licenses in my project are compatible
Challenge

Challenge

Check the box if there is no conflict. Place and X is there is a conflict.

Dependency License My Project License BSD MIT Apache LGPL GPL Commercial BSD
GPL
Commercial

Key Points
  • keypoint 1
  • keypoint 2

Content from Using Markdown

Last updated on 2026-08-28 | Edit this page

Overview

Questions

  • Multiple choice: Answers will be the different license types e.g. MIT, Apache 2.0, GPL etc. Questions: Project based scenarios…choose the best answer. Discuss answers.

Objectives

  • Compare key licensing factors for the type of OSS application (science/scholarship/non-commercialization) and list the options
  • Choose an appropriate OSS license and explain the decision thinking when contributing to different projects
  • Identify when a COSS is appropriate for OSS project.
Key Points
  • Using a narrative throughout a lesson helps reduce learner cognitive load
  • Choosing a lesson includes considering data license and ethical considerations.
  • Openly-licensed datasets can be found in subject area repositories or general data repositories.