1.3 Open Source Software and Licensing

1.3 Open Source Software and Licensing

Quick Answer: Objective 1.3 tests whether you understand open-source philosophy, the difference between copyleft and permissive licenses, major license families (GPL, BSD, Creative Commons), FOSS/FLOSS vocabulary, the roles of the FSF and OSI, and how companies make money with open source.

Philosophy: Freedom, Not Just Price

In free and open-source communities, free primarily means freedom: to run the program for any purpose, study how it works, redistribute copies, and distribute modified versions. Software can be free-as-in-freedom and still be sold on media or bundled with paid support. Conversely, freeware can be zero-cost yet closed-source with no right to modify.

Exam trap: equating "open source" with "no one can ever charge money." Charging for distribution, support, or hosting is compatible with many licenses.

FOSS, FLOSS, Free Software, and OSS

In practice, much of the same software is discussed under these labels. Essentials wants you to recognize the vocabulary and that the movements are allied but not identical in messaging.

FSF and OSI

The Free Software Foundation (FSF) advocates software freedom and is closely associated with the GNU project and copyleft licensing philosophy (notably the GPL).

The Open Source Initiative (OSI) maintains the Open Source Definition and reviews licenses for OSI approval. OSI framing often emphasizes practical collaboration, quality, and business adoption.

If a question asks which organization is tied to the GNU/GPL freedom message, think FSF. If it asks about the Open Source Definition or OSI-approved licenses, think OSI.

Copyleft Versus Permissive

Copyleft uses copyright law to keep derivatives free when distributed. It is sometimes summarized as "share alike" for software.

Permissive licenses maximize reuse, including in closed-source products, as long as conditions like attribution are met.

Exam scenario: a vendor wants to embed open-source code into a proprietary appliance without releasing their whole product's source. Permissive licensing is usually the easier fit; strong copyleft obligations may conflict with that business goal unless carefully architected.

GPL, BSD, and Creative Commons

GPL (GNU General Public License) is the flagship copyleft software license. Know it as the license that requires sharing source for distributed derivatives under compatible terms.

BSD licenses are classic permissive software licenses used by many libraries and tools.

Creative Commons (CC) licenses are widely used for content — documentation, images, course materials — not as the primary model for binary software packages. CC variants include attribution-only styles and share-alike styles. Do not casually say "the software is under Creative Commons" when the question is about application source code; software questions usually point to GPL/BSD/MIT-style licenses, while docs/media may be CC.

Open Source Business Models

Companies build sustainable businesses around open source without hiding all source:

• Support and services — paid help, SLAs, consulting
• Dual licensing — community license plus a commercial license for proprietary embedding
• Hosted / SaaS — run open-source software as a paid cloud service
• Training and certification — teach the stack
• Hardware or complementary products — sell devices that run open software
• Enterprise distributions — paid subscriptions for certified builds, updates, and legal assurance (think enterprise Linux vendors)

Understanding these models helps on career-oriented questions: open source is not anti-business; it changes where value is captured.

License Compatibility in Plain Language

You are not expected to be a lawyer on Linux Essentials, but you should sense when combinations get sensitive. Mixing strong copyleft code into a larger work that you distribute can pull obligations onto the distributed derivative. Permissive components are usually easier to combine. Dual-licensed projects sometimes offer a GPL (or similar) community path and a separate commercial license for vendors that need different terms.

When documentation or training slides are released under Creative Commons, check whether the license is attribution-only or share-alike. Share-alike content licenses parallel the "pass freedoms along" idea of copyleft, but they still apply to content, not as a substitute label for the GPL on program source.

Career Angle: Reading a LICENSE File

In real jobs you will open a LICENSE or COPYING file before shipping a product. On the exam, that habit translates to: identify the license family, decide copyleft vs permissive, and predict redistribution duties. If a manager asks "Can we keep our secret sauce closed while using this library?" your first filter is the license model, not the logo on the project website.

Worked Exam Thinking

1. Read whether the artifact is software or content.
2. Decide if the scenario needs copyleft preservation or permissive reuse.
3. Match GPL vs BSD vs Creative Commons accordingly.
4. Remember FSF ↔ free software freedoms / GNU; OSI ↔ open source definition / approved licenses.
5. Reject traps that say free software cannot be sold or that open source always means public domain (public domain is different from licensed FOSS).

Mastering these distinctions is enough for the weight-1 objective: precise vocabulary beats memorizing every license clause. If two answers both sound "open," prefer the one that correctly names the license model and the organization associated with that tradition.