Fiche de révision : Understanding Open Source Licenses

📋 Course Outline

1. Open Source Licences
2. Free Software Foundation
3. Free Software Liberties
4. GPL and Copyleft
5. Open Source Initiative
6. Permissive Licences
7. MIT and BSD Licences

📖 1. Open Source Licences

🔑 Key Concepts & Definitions

Copyright: Legal ownership of software code by its creator or owner. It grants exclusive rights over the use and distribution of the software.

Software License: A legal instrument that defines permissions and restrictions on how software can be used, modified, and shared. It specifies what users are allowed to do with the software owned by the copyright holder.

Public Domain: Status of a work with no exclusive intellectual property rights. Placing software in the public domain makes it freely accessible for use without restrictions, representing the simplest way to make software free.

📝 Essential Points

Software owners establish usage rights through licenses, which determine what can and cannot be done with the software. These licenses vary in restrictiveness, ranging from permissive licenses that allow broad freedoms to restrictive licenses that impose limitations on use, modification, or redistribution. Placing software in the public domain is the most straightforward method to make it freely available, as it involves no licensing restrictions, allowing anyone to use, modify, or distribute the software without conditions.

💡 Key Takeaway

Understanding the fundamental legal framework—how copyright, licenses, and public domain status govern software usage—is essential before exploring specific open source licenses.

📖 2. Free Software Foundation

🔑 Key Concepts & Definitions

Free Software Foundation (FSF): An organization founded by Richard Stallman in 1985 to promote free software and defend users' rights to use, study, modify, and distribute software freely.

GNU Project: A collection of free software tools initiated by the FSF to support Linux environments, providing essential utilities for free software development and operation.

GPLv2 and GPLv3: Versions of the GNU General Public License created by the FSF, which allow modification and redistribution of software under copyleft terms, ensuring that derivative works remain free.

📝 Essential Points

The FSF was established in 1985 by Richard Stallman with the goal of promoting free software. It developed the GNU tools, which are essential for Linux and other free software projects. The FSF's licenses, notably the GPLv2 and GPLv3, are designed to permit modification and redistribution of software while maintaining copyleft obligations, ensuring that freedoms are preserved in derivative works.

💡 Key Takeaway

The FSF is the pioneering institution that defines and advocates for software freedom through its licenses and projects, ensuring that users retain control over their software.

📖 3. Free Software Liberties

🔑 Key Concepts & Definitions

Four Freedoms: The essential rights that define free software, ensuring users have control over the software they use.
Freedom 0: The right to run the program for any purpose.
Freedom 1: The right to study and modify the program.
Freedom 2: The right to redistribute copies of the software.
Freedom 3: The right to distribute modified versions of the software.

📝 Essential Points

Access to source code is necessary to exercise Freedoms 1 and 3, as understanding and modifying the software require visibility into its code. These freedoms must be irrevocable, meaning once granted, they cannot be withdrawn, and they must be exercisable without needing permission from third parties. This guarantees users ongoing control over the software. Additionally, users are free to combine free software from different authors, enabling integration and collaboration across various projects without restrictions.

💡 Key Takeaway

Free software is defined by specific user freedoms that guarantee control over software use, study, modification, and sharing, ensuring users retain essential rights without third-party interference.

📖 4. GPL and Copyleft

🔑 Key Concepts & Definitions

GNU Public License (GPL): A widely used free software license with strong copyleft provisions, ensuring that modified versions remain under the same license.

Copyleft: A licensing principle requiring that derivative works of licensed software be distributed under the same license terms, thereby preserving freedoms in all redistributed versions.

LGPL: Lesser GPL license that allows linking with proprietary software, making it less restrictive than the GPL.

Viral License: A term describing the GPL’s requirement that any modifications or derivative works inherit the GPL license, effectively spreading the license’s terms to all redistributed versions.

📝 Essential Points

GPL enforces that all modifications to the licensed software remain under the GPL license, creating a viral effect that ensures the software’s freedoms are preserved in derivative works. This means that any modified version must also be distributed with the same freedoms and restrictions as the original.

LGPL is less restrictive than GPL, permitting the software to be linked with proprietary software without imposing GPL’s copyleft requirements on the entire combined work.

Copyleft ensures that the freedoms associated with the software—such as the rights to use, modify, and redistribute—are maintained in all redistributed versions, whether original or modified.

💡 Key Takeaway

GPL and copyleft protect software freedom by legally requiring that all derivative works remain free under the same terms, preventing proprietary restrictions from being imposed on modified versions.

📖 5. Open Source Initiative

🔑 Key Concepts & Definitions

Open Source Initiative (OSI): Organization that approves open source licenses but does not create them.

Copyleft Restrictiveness: OSI views copyleft as too restrictive and FSF as too political.

License Approval: OSI approves some FSF licenses but not all OSI-approved licenses are FSF-approved.

📝 Essential Points

Founded in 1998 by Bruce Perens and Eric Raymond, OSI emphasizes the practical benefits of open source software rather than political ideology. Its focus is on promoting open source licensing that offers tangible advantages for businesses and developers. OSI's approval process serves as a mark of compliance with the open source definition, ensuring that licenses meet specific criteria for openness and freedom. Notably, OSI approves certain licenses originally created by the Free Software Foundation (FSF), but it does not endorse all FSF licenses, highlighting its pragmatic approach to licensing standards.

💡 Key Takeaway

The OSI emphasizes a pragmatic, business-friendly approach to open source licensing, distinguishing itself from FSF’s ideological stance by focusing on practical benefits and license compliance.

📖 6. Permissive Licences

🔑 Key Concepts & Definitions

Permissive License: A license allowing broad reuse with minimal restrictions. It enables developers to incorporate the licensed software into their projects, including proprietary ones, with limited obligations.

MIT License: A simple, permissive open source license. It permits reuse, modification, and distribution of the software, often requiring only the preservation of copyright notices.

BSD License: A family of permissive licenses originating from Berkeley Unix. They allow for free use, modification, and distribution, typically with minimal restrictions and requirements to preserve copyright notices.

Creative Commons Licenses: Licenses designed for creative works, some of which are permissive. They facilitate sharing and reuse of creative content under specified conditions.

📝 Essential Points

Permissive licenses allow integration into proprietary software, making them highly flexible for commercial and closed-source projects. They impose minimal obligations, often just requiring the preservation of copyright notices, which simplifies compliance. These licenses are compatible with many other licenses, fostering widespread adoption and collaboration. Their broad acceptance and minimal restrictions contribute to their popularity in open source development and beyond.

💡 Key Takeaway

Permissive licenses maximize freedom for developers and businesses by imposing minimal constraints on software reuse, encouraging widespread adoption and integration.

📖 7. MIT and BSD Licences

🔑 Key Concepts & Definitions

• MIT License: see section 6

BSD 2-Clause License: Similar to the MIT License, it permits the same freedoms—use, modification, and redistribution—on the condition that the copyright notice and license are maintained.

BSD 3-Clause License: Extends the BSD 2-Clause License by adding a clause that forbids the use of the authors’ names for promotion or endorsement of derived products without permission.

No Warranty Clause: Both the MIT and BSD licenses explicitly disclaim any warranty for the software, meaning the software is provided "as is" without guarantees of performance or suitability.

📝 Essential Points

The MIT license is characterized by its brevity, simplicity, and permissiveness, making it highly accessible for developers. BSD licenses, including the 2-Clause and 3-Clause versions, also allow proprietary use and redistribution with minimal restrictions—mainly requiring the retention of copyright notices and license terms. The BSD 3-Clause License adds a safeguard against the unauthorized use of the authors’ names for promotional purposes, providing extra protection for the original creators. Both licenses include a no warranty clause, disclaiming any liability for the software’s performance or issues.

💡 Key Takeaway

MIT and BSD licenses offer straightforward, permissive licensing options that are favored for their simplicity and broad compatibility, making them popular choices for open source projects.

📅 Key Dates

(There are no explicit dates mentioned in the provided content, so this section is omitted.)

📊 Synthesis Tables

⚠️ Common Pitfalls & Confusions

• Confusing public domain with permissive licenses; public domain involves no restrictions.
• Misunderstanding copyleft as merely a licensing restriction rather than a freedom-preserving principle.
• Assuming all open source licenses are equally restrictive; some (permissive licenses) impose minimal restrictions.
• Overlooking the difference between GPL’s viral copyleft and LGPL’s linking flexibility.
• Believing that the FSF and OSI have identical views or approval processes for licenses.
• Confusing the role of the Free Software Foundation with the Open Source Initiative.
• Misinterpreting “free” as necessarily meaning “cost-free” without considering licensing rights.

✅ Exam Checklist

• Know the definition of copyright and its role in software licensing.
• Understand what a software license is and how it governs software use.
• Differentiate between public domain and licensed software.
• Recognize the goals and history of the Free Software Foundation and Richard Stallman.
• Master the Four Freedoms of free software: Freedom 0, 1, 2, and 3.
• Explain copyleft principles and how GPL enforces them.
• Distinguish between GPL and LGPL licenses regarding restrictions on linking.
• Describe the role of the Open Source Initiative and its pragmatic approach to licensing.
• Identify permissive licenses such as MIT and BSD, including their key characteristics and obligations.
• Know that permissive licenses allow integration into proprietary projects with minimal restrictions.
• Understand that FSF licenses (GPL, LGPL) are more restrictive than permissive licenses.
• Be familiar with key authors: Richard Stallman (FSF), Bruce Perens, and Eric Raymond (OSI).