Computer Science · 12th Grade · Social Impacts and Professional Ethics · Weeks 37-45

Open Source Software and Creative Commons

Students compare proprietary models with open-source movements and creative commons, understanding their impact on software development.

• Common Core State Standards
• CSTA: 3B-IC-28
• CCSS.ELA-LITERACY.RST.11-12.9

About This Topic

The open-source movement has fundamentally changed how software is built, distributed, and sustained. At the 12th-grade level, students should understand the philosophical, practical, and economic dimensions of open source, not just its technical mechanics. Open-source software (OSS) is characterized by publicly available source code that anyone can inspect, modify, and redistribute under the terms of an open-source license. Major infrastructure underlying the internet, including the Linux kernel, Apache web server, Python, and PostgreSQL, is open-source, and virtually every technology company builds on open-source foundations regardless of their own licensing model.

Creative Commons extends similar principles to non-software creative works, offering a spectrum of licenses from highly permissive (CC BY, requiring only attribution) to more restrictive (CC BY-NC-ND, prohibiting commercial use and derivatives). Students preparing to publish educational materials, research, blog posts, or media should understand which license aligns with their goals. This topic connects directly to CSTA standard 3B-IC-28, which asks students to evaluate the beneficial and harmful effects of computing innovations on society.

Active learning suits this topic because the trade-offs between open and proprietary models are genuinely debated and depend on values as much as evidence. Structured comparisons and scenario-based decisions help students develop their own informed positions rather than accepting either model as obviously correct.

Key Questions

1. How does the open-source movement accelerate innovation across the globe?
2. Compare the benefits and drawbacks of proprietary versus open-source software models.
3. Justify the choice between different Creative Commons licenses for digital content.

Learning Objectives

• Compare the core tenets and licensing models of proprietary software, open-source software, and Creative Commons.
• Analyze the societal and economic impacts of open-source software development on global innovation.
• Evaluate the advantages and disadvantages of proprietary versus open-source software for different user needs and contexts.
• Justify the selection of specific Creative Commons licenses for various digital content creation scenarios, considering user goals and restrictions.
• Critique the ethical considerations surrounding software licensing and content sharing, referencing CSTA standard 3B-IC-28.

Before You Start

Introduction to Software Development

Why: Students need a basic understanding of what software is and how it is created to grasp the concepts of source code and licensing.

Copyright and Intellectual Property Basics

Why: Familiarity with copyright law is essential for understanding the purpose and function of software licenses and Creative Commons terms.

Key Vocabulary

Proprietary Software	Software owned by an individual or company, with its source code kept secret and usage restricted by a license agreement.
Open-Source Software (OSS)	Software with source code that anyone can inspect, modify, and redistribute, typically under specific open-source licenses.
Creative Commons (CC) License	A set of public copyright licenses that enable the free distribution of an otherwise copyrighted work, offering various permissions and restrictions.
Source Code	The human-readable instructions written by programmers that define how a software program operates.
Derivative Work	A new creative work based on a pre-existing work, such as a translation, adaptation, or modification, which may be restricted by copyright or license terms.

Watch Out for These Misconceptions

Common Misconception

Open-source software is always free to use in any way.

What to Teach Instead

Free as in 'free speech,' not necessarily 'free beer.' Open-source licenses impose specific conditions; copyleft licenses require derivative works to also be open. Many companies have faced legal action for using GPL software in proprietary products without complying with the license terms. The license matching activity makes these distinctions operational.

Common Misconception

Open-source software is less secure because anyone can see the code.

What to Teach Instead

Security through obscurity is considered a weak defense by security professionals. Open source allows the global security research community to audit code and report vulnerabilities. Many security-critical systems rely on open-source cryptographic libraries precisely because they have been extensively reviewed. Proprietary code has the same vulnerabilities -- they are just less likely to be found and reported by independent researchers.

Common Misconception

Companies that use open-source software do not contribute back to it.

What to Teach Instead

Many of the largest open-source contributors are major corporations: Google, Microsoft, Facebook, and Red Hat all contribute extensively to Linux, Kubernetes, and other foundational projects. Their motivations include fixing bugs that affect their own products, influencing project direction, and recruiting engineers who work on high-profile public code.

Active Learning Ideas

Gallery Walk: Famous Open-Source Projects

Set up six stations featuring major open-source projects: Linux, Firefox, Python, TensorFlow, Wikipedia (CC-licensed), and OpenStreetMap. Each station includes a brief fact sheet about the project's origin, governance, funding model, and commercial adoption. Student pairs rotate and answer: How does this project sustain itself? Who contributes and why? What would be lost if it were proprietary?

40 min·Pairs

Structured Controversy: Open Source vs. Proprietary

Assign students to argue for one model in a specific context: a medical device, a social media platform, a city traffic management system, and a K-12 learning app. Each group must address security, innovation, accountability, and cost in their argument. After presentations, the class votes on which model is better for each context and explains the reasoning.

50 min·Small Groups

License Matching Activity: Creative Commons

Provide students with six hypothetical digital content creators (a teacher sharing lesson plans, a photographer who needs credit, a researcher who wants no commercial use, etc.) and six Creative Commons license options. Students individually match each creator to the appropriate license with written justification, then compare matches with a partner and resolve disagreements using the CC license selector criteria.

30 min·Pairs

Real-World Connections

• Developers at Google and Microsoft contribute to and utilize open-source projects like the Linux kernel and Kubernetes, demonstrating how major tech companies integrate OSS into their proprietary products.
• Educators creating online courses or sharing research papers can choose Creative Commons licenses (e.g., CC BY-SA) to allow others to adapt and share their work, fostering collaborative learning environments.
• Independent game developers often use open-source game engines like Godot, allowing them to build and distribute their creations with fewer upfront costs and greater control over the development process.

Assessment Ideas

Discussion Prompt

Pose the following scenario: 'A small startup is developing a new mobile app. They have limited funding but want to reach a wide audience. Discuss whether they should build their app using proprietary code, open-source libraries, or a combination. Consider the long-term implications for their business model and community engagement.'

Quick Check

Provide students with three distinct digital content scenarios: a personal blog post, a research paper for academic publication, and a commercial stock photo. Ask them to select and justify the most appropriate Creative Commons license for each, explaining their choice based on the license's permissions and restrictions.

Exit Ticket

On an index card, have students write one sentence explaining the fundamental difference between proprietary software and open-source software. Then, ask them to list one specific benefit of open-source software for global innovation.

Frequently Asked Questions

How does the open-source movement accelerate software development?

Open-source enables developers worldwide to build on shared foundations rather than reinventing common components. A startup can deploy a production database, web server, and programming language without writing any of them. Contributions from thousands of developers across organizations mean bugs are found faster and features are added more quickly than any single company could manage.

What is the difference between GPL and MIT licenses?

The MIT license permits anyone to use, modify, and distribute the software with almost no restrictions beyond attributing the original author. The GPL (GNU General Public License) is a copyleft license requiring that any software that incorporates GPL code and is distributed must also be released under the GPL. MIT is more permissive; GPL is designed to ensure the software remains open.

What are Creative Commons licenses and when should I use them?

Creative Commons licenses allow creators to specify how others may use their work without requiring individual permission agreements. Options range from CC BY (attribution only) to CC BY-NC-ND (attribution, non-commercial, no derivatives). Choose based on whether you want to allow commercial use, whether you want to allow modifications, and whether you require that derivatives use the same license.

How does active learning help students compare open-source and proprietary software models?

The open-source versus proprietary debate involves trade-offs that depend heavily on context and values. Structured controversy activities, where students defend one model in a specific scenario, develop the contextual reasoning that blanket rules cannot provide. Gallery walks through real open-source projects build concrete intuition about how these ecosystems actually function and sustain themselves.