LPI OSS Essentials study guide
LPI OSS Essentials · Work through your exam, one topic at a time.
Open Source Essentials is an LPI Essentials-track certificate covering the fundamentals of free and open source software, open content and open technology. LPI describes it as spanning legal, technical and business aspects and as deliberately not limited to one profession: developers, managers, lawyers and other professionals should be able to share terminology and collaborate, and individuals should be able to understand open source concepts and engage with the community. The LPI OSS Essentials study guide has 6 sections and about 2,347 words.
01Software Fundamentals
Software Fundamentals asks you to explain how software is written, packaged, and executed. Licensing, business models, and collaboration all rest on these mechanics, so the questions here are definitional but precise.
394 words, about 2 min02Open Source Software Licenses
Open Source Software Licenses is the highest-stakes domain: questions test which obligations a license imposes, when they trigger, and whether two licenses can be combined. Permissive - MIT, BSD-2-Clause, BSD-3-Clause, Apache-2.0.
392 words, about 2 min03Open Content Licenses
Open Content Licenses covers Creative Commons, public-domain dedications, and the free-culture test - for text, images, data, and educational material rather than code. Four conditions combine into six licenses: BY (attribution), SA (share-alike), NC (non-commercial), ND (no derivatives).
392 words, about 2 min04Open Source Business Models
Open Source Business Models tests how an organization funds development while keeping code under an open license - and which license choices support which revenue stream. Support and subscription - software is free; customers pay for SLAs, certified builds, updates, and indemnity (Red Hat's model).
373 words, about 2 min05Project Management
Project Management covers how open source projects are governed, planned, released, and kept legally clean - the processes around the code, not the code itself. Contributors submit changes; reviewers or committers approve them; maintainers set direction and hold merge rights.
391 words, about 2 min06Collaboration and Communication
Collaboration and Communication tests the channels, artifacts, and conventions that let distributed contributors work together - questions here often read as "what should you do first". Mailing lists - asynchronous, archived, the place for decisions that must be quotable later.
405 words, about 2 min