Also update existing licenses to the either be wrapped by the Clarified license or use the new OSLv1.1 license.
Add the new license files.
<a href="licenses.html#license-documentation" class="nav-text link">Documentation Licenses</a>
</div>
<div class="nav-item block">
- <a href="licenses/oslv1.html" class="nav-text link">Open Standard License 1</a>
+ <a href="licenses/clarifiedv1_0.html" class="nav-text link">Clarified License 1.0</a>
+ </div>
+ <div class="nav-item block">
+ <a href="licenses/oslv1_1.html" class="nav-text link">Open Standard License 1.1</a>
+ </div>
+ <div class="nav-item block">
+ <a href="licenses/oslv1_0.html" class="nav-text link">Open Standard License 1.0</a>
</div>
<div class="nav-item block ellipses">
<a href="licenses.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
<h1 class="section-title h h1">Licenses</h1>
</header>
+ <p class="p">
+ Note that <a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a> is always followed by the license that it is wrapping.
+ </p>
+
<article id="license-website" class="article">
<header class="article-header header">
<h2 class="article-title h h2">Website Licenses</h2>
</header>
+
<div class="article-content">
<p class="p">
There are multiple licenses for content on this website and content served from this website (such as a Distribution). The website documentation covers only the parts of the website that are not already under an existing license. The specifications are under a different license. All files, be they binaries or text files, provided by the distributions have their own licenses. The Featureless Linux Library and all files provided along with it have their own licenses. Documentation associated with each of these projects are under a different license as defined by their associated project.
</p>
+
<p class="p">
- Everything else on this website, such as this news blog, that is content is under <abbr title="Creative Commons Attribution Share Alike 4.0 International">CC By SA 4.0</abbr> license.
+ Everything else on this website, such as this news blog, that is content is under <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <abbr title="Creative Commons Attribution Share Alike 4.0 International">CC By SA 4.0</abbr></strong> license.
</p>
+
<p class="p">
- Everything else on this website that is source code, including <abbr title="Hyper Text Markup Language">HTML</abbr> markup, <abbr title="Cascading Style Sheets">CSS</abbr>, and Javascript, is under <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr> license.
+ Everything else on this website that is source code, including <abbr title="Hyper Text Markup Language">HTML</abbr> markup, <abbr title="Cascading Style Sheets">CSS</abbr>, and Javascript, is under <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr></strong> license.
</p>
+
<p class="p">
© 2022-2026 Kevin Day
</p>
</header>
<div class="article-content">
<p class="p">
- There is currently only a single Kevux distribution, called Turtle Kevux. This distribution is a collection of numerous software projects and their related files. Each of these is under their own respective license, which is provided with their respective source code. The Kevux-specific code, such as the Turtle Kevux Installation Scripts is under the <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr> license. The <abbr title="Turtle Kevux Installation Scripts">TKIS</abbr> also heavily utilizes the Featureless Make system as well as numerous Featureless Settings Specification processing programs that are also under the <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr> license.
+ There is currently only a single Kevux distribution, called Turtle Kevux. This distribution is a collection of numerous software projects and their related files. Each of these is under their own respective license, which is provided with their respective source code. The Kevux-specific code, such as the Turtle Kevux Installation Scripts is under the <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr></strong> license. The <abbr title="Turtle Kevux Installation Scripts">TKIS</abbr> also heavily utilizes the Featureless Make system as well as numerous Featureless Settings Specification processing programs that are also under the <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr></strong> license.
</p>
+
<p class="p">
- Each project is copyrighted by their respective authors. The Kevux Distribution specific files are copyrighted by Kevin Day.
+ Each project is copyrighted by their respective authors. The Kevux Distribution specific files are © by Kevin Day.
</p>
</div>
</article>
<header class="article-header header">
<h2 class="article-title h h2">Featureless Linux Library Licenses</h2>
</header>
+
<div class="article-content">
<p class="p">
- The <abbr title="Featureless Linux Library">FLL</abbr> source code is © 2007-2026 Kevin Day under the <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr> license.
+ The <abbr title="Featureless Linux Library">FLL</abbr> source code is © 2007-2026 Kevin Day under the <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr></strong> license.
</p>
+
<p class="p">
- The <abbr title="Featureless Linux Library">FLL</abbr> standards and specifications are © 2007-2026 Kevin Day under the <a href="licenses/oslv1.html" class="link"><abbr title="Open Standard License version 1 or greater">OSLv1+</abbr></a>. The <a href="licenses/oslv1.html" class="link"><abbr title="Open Standard License version 1 or greater">OSLv1+</abbr></a> is under active development and may be of a lesser version, such as 0.5. For simplicity, these are being referred to as 1.0 as the goal and intent of the license grant is for version 1 or greater. Therefore any version less than 1 is implicitly assumed to be of version 1 or greater.
+ The <abbr title="Featureless Linux Library">FLL</abbr> standards and specifications are © 2007-2026 Kevin Day under the <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <a href="licenses/oslv1_1.html" class="link"><abbr title="Open Standard License version 1.1 or greater">OSLv1.1+</abbr></a></strong>.
+ </p>
+
<p class="p">
- Documentation contained within the <abbr title="Featureless Linux Library">FLL</abbr> that is not under a specification license is © 2007-2026 Kevin Day under the <abbr title="Creative Commons Attribution Share Alike 4.0 International">CC By SA 4.0</abbr>.
+ Documentation contained within the <abbr title="Featureless Linux Library">FLL</abbr> that is not under a specification license is © 2007-2026 Kevin Day under the <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <abbr title="Creative Commons Attribution Share Alike 4.0 International">CC By SA 4.0</abbr></strong>.
</p>
</div>
</article>
<header class="article-header header">
<h2 class="article-title h h2">Individual Projects Licenses</h2>
</header>
+
<div class="article-content">
<p class="p">
- All of the projects listed on the Projects pages are either part of the <abbr title="Featureless Linux Library">FLL</abbr> or are based on the <abbr title="Featureless Linux Library">FLL</abbr>. As a result they are © 2007-2026 Kevin Day under the <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr>.
+ All of the projects listed on the Projects pages are either part of the <abbr title="Featureless Linux Library">FLL</abbr> or are based on the <abbr title="Featureless Linux Library">FLL</abbr>. As a result they are © 2007-2026 Kevin Day under the <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr></strong>.
</p>
</div>
</article>
<header class="article-header header">
<h2 class="article-title h h2">Documentation Licenses</h2>
</header>
+
<div class="article-content">
<p class="p">
- Documentation that is used to described specifications (included Application Programming Interfaces) are © 2007-2026 Kevin Day under the <a href="licenses/oslv1.html" class="link"><abbr title="Open Standard License version 1 or greater">OSLv1+</abbr></a>.
+ Documentation that is used to described specifications (included Application Programming Interfaces) are © 2007-2026 Kevin Day under the <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <a href="licenses/oslv1_1.html" class="link"><abbr title="Open Standard License version 1.1 or greater">OSLv1.1+</abbr></a></strong>.
</p>
+
<p class="p">
- All remaining documentation that does not fall under the <a href="licenses/oslv1.html" class="link"><abbr title="Open Standard License version 1 or greater">OSLv1+</abbr></a> are © 2007-2026 Kevin Day under the <abbr title="Creative Commons Attribution Share Alike 4.0 International">CC By SA 4.0</abbr>.
+ All remaining documentation that does not fall under the <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <a href="licenses/oslv1_1.html" class="link"><abbr title="Open Standard License version 1.1 or greater">OSLv1.1+</abbr></a></strong> are © 2007-2026 Kevin Day under the <strong class="strong"><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0 or Later</a>, <abbr title="Creative Commons Attribution Share Alike 4.0 International">CC By SA 4.0</abbr></strong>.
</p>
</div>
</article>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>Licenses - Clarified 1.0</title>
+
+ <base href="../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Clarified License 1.0">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, license">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="licenses/clarifiedv1_0.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="news.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="licenses.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block highlight unlink">
+ <div class="nav-text unlink">Open Standard License</div>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="licenses/clarifiedv1_0.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="licenses/clarifiedv1_0.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Clarified License Version 1.0</h1>
+ </header>
+
+ <div class="main-content">
+ <p class="p">
+ The following is the literal license as a plain text file for direct display.
+ </p>
+ <pre class="preserve">Clarified License 1.0.
+ September 07, 2026.
+
+This license is a clarification on terminology and intent to be used on top of existing licenses to help ensure original intent and expectations are maintained without being altered or modified against the intent and purpose of the license.
+This further attempts to explicitly protect the Licenser and the Works from tricks, manipulation, and coercion (be it force, perceived force, fear of harm, or actual harm).
+
+
+Terminology:
+
+ - AI: Artificial Intelligence*.
+ - Combined Work: Anything that incorporates multiple independently licensed components without necessarily modifying their internal structure.
+ - Entity: Is used to refer to entity as well as anything else, such as an individual or other things, and is used this way to simplify reading and writing of this license (Licensee and Licenser have explicitly expanded examples of this).
+ - Implementation: The applying of some Standard or Specification.
+ - LCG: Lossy Computer Generation (any linguistic variation of "Generation", such as "Generated")*.
+ - LLM: Large Language Model*.
+ - Licensee: Any individual, organization, entity, or other thing that uses, applies, to whom this license is granted, to which this license is granted, or that otherwise uses or stores the information and data covered by this license.
+ - Licenser: Any individual, organization, entity, or other thing that grants the license for the Original Works.
+ - Modified Works: A modification of the Works, in part or whole.
+ - Original Works: The original, unmodified, Works with respect to a Modified Works.
+ - SLM: Small Language Model*.
+ - Specification: A specific interpretation or clarification of a Standard, such as the documentation that describes how to use or follow a Standard.
+ - Standard: A set of rules and guidelines.
+ - Wrapped License: A license being applied as a sub-set to this license.
+ - Works: Anything that is under this license, including those under the Wrapped License.
+
+* The AI term refers to intelligence that is artificial.
+ All computers have always been Artificial Intelligence, by definition.
+ Society has recently forgotten the meaning of AI and has redefined the terminology.
+ This license avoids that redefinition and uses the term as described herein.
+ Instead, LCG, or Lossy Computer Generation, is used to represent what society is now improperly using AI to mean.
+ The LCG is a super set of any form of computer generation that stores the original data in a lossy format, such as LLM (Large Language Model) and SLM (Small Language Model).
+ The lossy refers to the data being lost to some extent, similar to how MP3 (MPEG-1 Audio Layer III) is a lossy format.
+
+
+RSN) Details on reasons for license:
+
+ 01) There are different open-source licenses available but almost all follow the same basic principles.
+ 02) One would expect that these principles cannot be violated or changed.
+ 03) However, recent years have shown judges and various entities violating these core principles in direct violation of the intent, purpose, and reason for these licenses.
+ 04) Many immoral, unethical, and potentially unlawful tactics are being used in ways that might even appear lawful or is otherwise declared as lawful.
+ 05) This creates confusion in addition to being direct violation of the licenses.
+ 06) The goal of this license is to provide clarification based on observations in the world that conflict with the original intent and purpose of the license by providing a license that wraps a given license.
+ 07) This is done to avoid directly modifying a particular license.
+ 08) As a wrapping license, this is expected to override anything written on the Wrapped License.
+ 09) The goal is not to change the Wrapped License.
+ 10) Instead, the goal is to protect the original intent and purpose of the Wrapped License via explicit clarifications to help protect the Wrapped License from being modified by some third-party, even if that party is a judge or another legal (or lawful) Entity.
+
+ 11) This protection is explicitly achieved by requiring that all parties, of any form, must agree to the clarifications provided herein, irrespective of any other interpretation by any other party outside of the Licenser who maintains the final decision making or further clarifications over any aspect regarding any Works.
+
+
+PRL) Principles of this license:
+
+ 01) Waiving of any rights, protections, provisions, conditions, or anything else for this license is prohibited.
+ a) The Licenser may not waive any rights, protections, provisions, conditions, or anything else for this license.
+ b) The Licenser may explicitly and intentionally change the license instead of waiving but this may not be automatic, without intent, without will, or coerced.
+ 02) The references to this copyright shall describe both this license as well as the wrapped license.
+ a) The common practice will be to combined them, for example to combine `clarified_1_0_or_later` with `lgpl_2_1_or_later` as the Wrapped License would yield a name of `clarified_1_0_or_later-lgpl_2_1_or_later`.
+ b) The descriptions of the copyrights applied in this way may be stored as separate files, such that `clarified_1_0_or_later` will be a file and `lgpl_2_1_or_later` will be a separate file even if the actual applied license is `clarified_1_0_or_later-lgpl_2_1_or_later`.
+ 03) This license shall apply only to Works, the Wrapped License, and anything else covered by this license or the Wrapped License.
+ a) Agreeing to this terminology only applies to this license and Works.
+ b) Anything outside of this license, that is not a Works or the Wrapped License, is not affected by the clarifications of this license.
+ c) This is not intended to change any beliefs, or understandings of terminology, to any Entity, be they Licensee or otherwise, and is only intended to apply these clarifications to the Wrapped License and the Works.
+ d) Any Entity, be they Licensee or otherwise, must accept and acknowledge that these clarifications are independent of their own beliefs and may not apply their beliefs to these interpretations.
+ e) Applying this license may include additional coverage as designated by the Wrapped License.
+ 04) The final and absolute determination of any terminology and intent of this license is by the Licenser or a party explicitly authorized by the Licenser, and is not in any way subject to re-interpretation or re-definition in any way for any reason by any party including but not limited to judges, juries, lawyers, attorneys, technicians, experts, or governments.
+ a) A new Clarification version, along with additional name may be applied following any further clarifications (such as, for example, clarified_joe_shmoes_project_1_1_or_later-lgpl_2_1_or_later).
+ 05) Any restriction, alteration, removal, invalidation, making illegal, or making unlawful of or against any part of this license by any party, such as but not limited to a government or judge, shall not permanently alter this license in any way for any reason.
+ a) That is for example, if some court deems some part of this unlawful and then later makes it lawful, then the now re-lawfulized parts do and must immediately apply once more as if they were never made unlawful.
+ b) When at any point in time under any government any parts of this license is restricted, altered, removed, invalidated or otherwise made illegal, unlawful, or unenforceable is reversed, restored, or otherwise made legal, lawful, and enforceable again, then these parts are immediately in affect again.
+ 06) If at any point in time some party, such as but not limited to a government, makes any change to this license (such as those described in [PRL.05]) and the Licensee for any reason at any time is no longer subject to a given jurisdiction, then those parts of the original license are immediately in effect as if they were never altered or restricted in the first place.
+ a) For example, if a Licensee leaves the jurisdiction of some government that otherwise restricted some part of this license then that otherwise restricted part is immediately in affect again now that the Licensee is out of the given jurisdiction.
+ 07) This license is irrevocable unless there is a breach of the license conditions or as described below.
+ a) This does not prevent the Licenser from changing the license itself or the license applied to the Works.
+ b) This does not prevent the Licenser from upgrading the license to some newer version or variation.
+ 08) This license does not grant any kind of warranty or liability under any circumstances to any party for any reason, be it direct, indirect, consequential, incidental, or in any other form.
+ 09) This license does not restrict any party from optionally providing their own warranty or liability on any Implementation but such warranties or liabilities are completely separate and independent of this license in all circumstances for any reason, be it direct, indirect, consequential, incidental, or for any other reason.
+ 10) The Licensee must be capable of accepting the license.
+ a) Machines, LCG, software, etc... are expressly forbidden from accepting this license.
+ 11) The Licensee must be capable of being legally bound by these terms.
+ 12) This license applies before and overrides anything in the Wrapped License.
+ a) Otherwise, the Wrapped License applies as written.
+ 13) This license requires acceptance that using Works and storing in LCG is considered a Combined Works when that LCG also stores anything other than Works.
+ 14) This license requires acceptance that using Works and storing in LCG as the only thing in that LCG is considered a copy of that Works.
+ 15) This license requires acceptance that generating anything using LCG containing Works is:
+ a) Considered a copy of this Works.
+ b) Is a Modified Works.
+ c) Must comply with this license for this generated content, including:
+ 01) Providing the copyright for this Works for all generated, and therefore, Modified Works.
+ 02) Provide this license for Works for all generated, and therefore, Modified Works.
+ 03) Applying, complying with, and following the Wrapped License for this generated content.
+ d) Containing is not limited to complete works and includes any part of the Works no matter how small or trivial.
+
+
+LCG) Details on LCG usage:
+ 01) The current society has recently re-interpreted common terminology, such as how the term AI is now being interpreted differently.
+ 02) This has become a problem where licenses are being incorrectly perceived as a separate Works.
+ 03) There always has been an expectation that copying this in a lossy format, such as an LCG, would constitute as a Modified Works.
+ 04) This confusion is addressed by being explicitly clear in this regards.
+ 05) In order to accept this license,
+ a) The use of any Works, in part or whole, with or by LCG, be it LLM, SLM, or anything else, must be considered a Modified Works rather than a new or separate Works.
+ b) Appropriate credits must be provided for any and all Modified Works.
+ c) The entire Works, or any part, must be licensed at no charge to all third parties under the terms of this license.
+ d) The entire Works, or any part, must apply, comply with, and follow the Wrapped License.
+ 06) Note that this does not require acceptance of "Modified Works", regarding LCG, to be applied to anything not under this license.
+
+
+WAV) Details on denying the waiving of any rights:
+
+ 01) Another recent problem is where entities attempt to force waiving of rights (be it automatic, inferred, or otherwise) when there never has been any such expectation of this even being allowed by this license.
+ 02) This license would realistically fail to be an open-source license if any part of it can be waived.
+ 03) Therefore, no parts of this license may be waived by anyone, including the Licenser, of anything under this license.
+ 04) The Licenser must explicitly, and intentionally, change the license rather than waive anything.
+
+
+MOD) Details on the Modified Works:
+
+ 01) The Modified Works must comply with this license and the Wrapped License.
+ 02) The Modified Works must preserve ownership and copyrights of the Original Works.
+ 03) The Modified Works must not remove any protections of this license.
+ 04) The Modified Works must be marked as changed from the Original Works.
+ 05) Cannot make claims over the Original Works.
+ 06) May not change any copyrights and ownership of the Original Works.
+ 07) Making any modification does not transfer ownership of the Original Works.
+</pre>
+ </code>
+ </div>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
<!DOCTYPE html>
<html lang="en">
<head>
- <title>Licenses - Open Standard License 1</title>
+ <title>Licenses - Open Standard License 1.0</title>
<base href="../">
<meta charset="UTF-8">
<meta name="author" content="Kevin Day">
- <meta name="description" content="Open Standard License 1">
+ <meta name="description" content="Open Standard License 1.0">
<meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, license">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
<link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
- <link rel="canonical" href="licenses/oslv1.html">
+ <link rel="canonical" href="licenses/oslv1_0.html">
<link type="image/x-icon" rel="icon" href="images/kevux.ico">
<link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
<link type="text/html" rel="license" href="licenses.html">
<div class="nav-text unlink">Open Standard License</div>
</div>
<div class="nav-item block ellipses">
- <a href="licenses/oslv1.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
- <a href="licenses/oslv1.html" class="nav-text link close">Collapse Menu</a>
+ <a href="licenses/oslv1_0.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="licenses/oslv1_0.html" class="nav-text link close">Collapse Menu</a>
</div>
</nav>
</div>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>Licenses - Open Standard License 1.1</title>
+
+ <base href="../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Open Standard License 1.1">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, license">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="licenses/oslv1_1.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js fll specifications">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item"><a href="news.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item active"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="licenses.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block highlight unlink">
+ <div class="nav-text unlink">Open Standard License</div>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="licenses/oslv1_1.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="licenses/oslv1_1.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Open Standard License Version 1.1</h1>
+ </header>
+
+ <div class="main-content">
+ <p class="p">
+ The following is the literal license as a plain text file for direct display.
+ </p>
+ <pre class="preserve">Open Standard License 1.1.
+ September 07, 2026.
+
+This license applies to the Standards and their Specifications and designates legal requirements on Implementations of the Standard and their respective Specifications.
+
+
+Terminology:
+ - ABI: Application Binary Interface**.
+ - API: Application Programming Interface*.
+ - AI: Artificial Intelligence***.
+ - Combined Work: Anything that incorporates multiple independently licensed components without necessarily modifying their internal structure.
+ - Implementation: The applying of some Standard or Specification.
+ - LCG: Lossy Computer Generation (any linguistic variation of "Generation", such as "Generated")***.
+ - LLM: Large Language Model***.
+ - Licensee: Any individual, organization, entity, or other thing that uses, applies, to whom this license is granted, to which this license is granted, or that otherwise uses or stores the information and data covered by this license.
+ - Licenser: Any individual, organization, entity, or other thing that grants the license for the Original Works.
+ - Modified Works: A modification of the Works, in part or whole.
+ - Original Works: The original, unmodified, Works with respect to a Modified Works.
+ - Protocol: In the context of computers and software, this is a Standard focused on communication between at least two parties (often referring to Internet communication) and is at the most basic level an agreement of rules between two (or more) parties.
+ - Provider: A party who provides a Service of any kind (or equivalent functionality) that utilizes a Protocol or provides a Service that Implements or follows a Standard or Specification to another party.
+ - Service: Any action or labor performed by one party for another party (such as one person helping another person).
+ - SLM: Small Language Model***.
+ - Specification: A specific interpretation or clarification of a Standard, such as the documentation that describes how to use or follow a Standard.
+ - Standard: A set of rules and guidelines.
+ - Works: Anything that is under this license.
+
+* The API term is commonly mis-represented as Services or Protocols (such as "Web API" which in actuality should be called "Web Service" or "Web Protocol").
+ An API instructs a party, usually a programmer, on how to use a dependency when programming some software that utilizes said dependency.
+ An API is a Specification of some Implementation of a Standard be it a formally defined Standard or an informally defined Standard.
+ An API may be an Implementation of a Standard or a part of an Implementation of a Standard.
+ An API is, in effect, documentation.
+
+** The ABI term refers to an Application Binary Interface and represents the compiled Implementation of some API.
+ An ABI may not always exist for some API, such as for pure scripting languages.
+ An ABI is neither a Specification nor a Standard.
+ An ABI is an Implementation of an API making it an Implementation of a Standard or Specification.
+
+*** The AI term refers to intelligence that is artificial.
+ All computers have always been Artificial Intelligence, by definition.
+ Society has recently forgotten the meaning of AI and has redefined the terminology.
+ This license avoids that redefinition and uses the term as described herein.
+ Instead, LCG, or Lossy Computer Generation, is used to represent what society is now improperly using AI to mean.
+ The LCG is a super set of any form of computer generation that stores the original data in a lossy format, such as LLM (Large Language Model) and SLM (Small Language Model).
+ The lossy refers to the data being lost to some extent, similar to how MP3 (MPEG-1 Audio Layer III) is a lossy format.
+
+
+PRL) Principles of this license:
+ 01) The Standard or Specification is and must be freely and publicly available to use and implement irrespective of any license, patent, or other restriction of any kind for any reason of some Implementation or Provider.
+ 02) All patents associated are and must be royalty-free for unrestricted use and must not impose any restrictions on any third party's Implementation of this Standard in any way for any reason beyond those described in this license.
+ 03) There are not and there must not be any agreements or requirements for the execution of this license grant, including but not limited to: NDA, grant, click-through, or any form of paperwork (including but not limited to all non-paper forms of paperwork, such as digital forms) except as provided within this license.
+ 04) There are not and must not be any restrictions on the form of an Implementation of a Standard or Specification.
+ 05) Implementations of a Standard or Specification may be under any license so long as that license:
+ a) Does not restrict, alter, or invalidate this license in any manner.
+ b) Does not impose any form of restrictions to access, to use, to implement, to extend, or to deviate from anything allowed or otherwise granted by this license.
+ c) Does not violate this license or copyright.
+ 06) This license shall prohibit any form of restricting any parties to access, to use, to implement, to extend, or to deviate from this Standard unless:
+ a) Restricted by this license.
+ b) Unless there is a breach of license conditions.
+ 07) This license is irrevocable unless there is a breach of the license conditions or as described below.
+ a) This does not prevent the Licenser from changing the license itself or the license applied to the Works.
+ b) This does not prevent the Licenser from upgrading the license to some newer version or variation.
+ 08) This license does not grant any kind of warranty or liability under any circumstances to any party for any reason, be it direct, indirect, consequential, incidental, or in any other form.
+ 09) This license does not restrict any party from optionally providing their own warranty or liability on any Implementation but such warranties or liabilities are completely separate and independent of this license in all circumstances for any reason, be it direct, indirect, consequential, incidental, or for any other reason.
+ 10) The final and absolute determination of any terminology and intent of this license is by the Licenser or a party explicitly authorized by the Licenser, and is not in any way subject to re-interpretation or re-definition in any way for any reason by any party including but not limited to judges, juries, lawyers, attorneys, technicians, experts, or governments.
+ 11) Any restriction, alteration, removal, invalidation, making illegal, or making unlawful of or against any part of this license by any party, such as but not limited to a government or judge, shall not permanently alter this license in any way for any reason.
+ a) That is for example, if some court deems some part of this unlawful and then later makes it lawful, then the now re-lawfulized parts do and must immediately apply once more as if they were never made unlawful.
+ b) When at any point in time under any government any parts of this license is restricted, altered, removed, invalidated or otherwise made illegal, unlawful, or unenforceable is reversed, restored, or otherwise made legal, lawful, and enforceable again, then these parts are immediately in affect again.
+ 12) If at any point in time some party, such as but not limited to a government, makes any change to this license (such as those described in [PRL.11]) and the Licensee for any reason at any time is no longer subject to a given jurisdiction, then those parts of the original license are immediately in effect as if they were never altered or restricted in the first place.
+ a) For example, if a Licensee leaves the jurisdiction of some government that otherwise restricted some part of this license then that otherwise restricted part is immediately in affect again now that the Licensee is out of the given jurisdiction.
+ 13) Waiving of any rights, protections, provisions, conditions, or anything else for this license is prohibited.
+ a) The Licenser may not waive any rights, protections, provisions, conditions, or anything else for this license.
+ b) The Licenser may explicitly and intentionally change the license instead of waiving but this may not be automatic, without intent, without will, or coerced.
+ 14) This license requires acceptance that using Works and storing in LCG is considered a Combined Works when that LCG also stores anything other than Works.
+ 15) This license requires acceptance that using Works and storing in LCG as the only thing in that LCG is considered a copy of that Works.
+ 16) This license requires acceptance that generating anything using LCG containing Works is:
+ a) Considered a copy of this Works.
+ b) Is a Modified Works.
+ c) Must comply with this license for this generated content, including:
+ 01) Providing the copyright for this Works for all generated, and therefore, Modified Works.
+ 02) Provide this license for Works for all generated, and therefore, Modified Works.
+ d) Containing is not limited to complete works and includes any part of the Works no matter how small or trivial.
+ 17) The Licensee must be capable of accepting the license.
+ a) Machines, LCG, software, etc... are expressly forbidden from accepting this license.
+ 18) The Licensee must be capable of being legally bound by these terms.
+ 19) May modify your copies, or any portion thereof, given the conditions described in the details on Modified Works below.
+
+
+LCG) Details on LCG usage:
+ 01) The current society has recently re-interpreted common terminology, such as how the term AI is now being interpreted differently.
+ 02) This has become a problem where licenses are being incorrectly perceived as a separate Works.
+ 03) There always has been an expectation that copying this in a lossy format, such as an LCG, would constitute as a Modified Works.
+ 04) This confusion is addressed by being explicitly clear in this regards.
+ 05) In order to accept this license,
+ a) The use of any Works, in part or whole, with or by LCG, be it LLM, SLM, or anything else, must be considered a Modified Works rather than a new or separate Works.
+ b) Appropriate credits must be provided for any and all Modified Works.
+ c) The entire Works, or any part, must be licensed at no charge to all third parties under the terms of this license.
+ 06) Note that this does not require acceptance of "Modified Works", regarding LCG, to be applied to anything not under this license.
+
+
+WAV) Details on denying the waiving of any rights:
+
+ 01) Another recent problem is where entities attempt to force waiving of rights (be it automatic, inferred, or otherwise) when there never has been any such expectation of this even being allowed by this license.
+ 02) This license would realistically fail to be an open-source license if any part of it can be waived.
+ 03) Therefore, no parts of this license may be waived by anyone, including the Licenser, of anything under this license.
+ 04) The Licenser must explicitly, and intentionally, change the license rather than waive anything.
+
+
+MOD) Details on the Modified Works:
+
+ 01) The Modified Works must be a Standard, a Specification, or an Implementation.
+ 02) The Modified Works must preserve ownership and copyrights of the Original Works.
+ 03) The Modified Works must not remove any protections of this license.
+ 04) The Modified Works must be marked as changed from the Original Works.
+ 05) Cannot make claims over the Original Works.
+ 06) May not change any copyrights and ownership of the Original Works.
+ 07) Making any modification does not transfer ownership of the Original Works.
+</pre>
+ </code>
+ </div>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
<div class="content-block">
<div id="nav-expanded" class="nav-block">
<nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block">
+ <div class="nav-text notice">2026 / 09 / 08</div>
+ <a href="news/2026/2026_09_08-license_changes.html" class="nav-text link">License Changes</a>
+ </div>
<div class="nav-item block">
<div class="nav-text notice">2026 / 04 / 30</div>
<a href="news/2026/2026_04_30-fll_0_8_1_and_0_6_16_releases.html" class="nav-text link">FLL 0.8.1 and 0.6.16 Releases</a>
<h1 class="section-title h h1">News</h1>
</header>
- <article id="2026_04_30-fll_0_8_1_and_0_6_16_releases" class="article">
+ <article id="2026_09_08-license_changes" class="article">
<header class="article-header header">
+ <h2 id="2026_09_08-license_changes-title" class="article-title h h2">2026 / 09 / 08 - License Changes</h2>
+ </header>
+
+ <div class="article-content">
+ <p class="p">
+ I have been sitting back and observing some of the ongoing events regarding <abbr title="Lossy Computer Generation">LCG</abbr>, copyright licenses, and even terms of service agreements.
+ Existing precedence is being ignored if not forgotten.
+ Long standing language is being redefined.
+ Parasitic terms of services have been designed and are being used.
+ </p>
+
+ <p class="p">
+ My answer to all of this is to clarify the copyright licenses to ensure that the original intent, behavior, and expectations remain and hold true.
+ Implementing this, however, is a bit tricky.
+ I do not want to rewrite any existing licenses, such as the <abbr title="GNU Lesser General Public License">LGPL</abbr> license.
+ </p>
+
+ <p class="p">
+ I have decided that the solution is to re-license using a wrapping license in order to avoid directly modifying the wrapped licenses.
+ The new license only serves a single purpose of providing clarification and protections while still preserving the terms of the wrapped licenses as much as possible.
+ This new license, called <a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0</a>, supersedes anything in the wrapped license to provide the necessary protections.
+ </p>
+
+ <p class="p">
+ The <a href="licenses/oslv1_1.html" class="link"><abbr title="Open Standard License">OSL</abbr></a> is directly changed because I wrote the original license and I can just create a new version.
+ All other licenses are to be wrapped.
+ </p>
+
+ <p class="p">
+ The full license terms are available here:
+ </p>
+
+ <ul>
+ <li><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0</a></li>
+ <li><a href="licenses/oslv1_1.html" class="link">Open Standard License Version 1.1</a></li>
+ </ul>
+
+ <p class="p">
+ <a id="2026_09_08-license_changes-more" href="news/2026/2026_09_08-license_changes.html" class="content link" aria-labelledby="2026_09_08-license_changes-more 2026_09_08-license_changes-title">Continue reading…</a>
+ </p>
+ </div>
+ </article>
+
+ <article id="2026_04_30-fll_0_8_1_and_0_6_16_releases" class="article">
+ <header class="article-header header separate">
<h2 id="2026_04_30-fll_0_8_1_and_0_6_16_releases-title" class="article-title h h2">2026 / 04 / 30 - FLL 0.8.1 and 0.6.16 Releases</h2>
</header>
<div class="nav-item block back">
<a href="news.html" class="nav-text link back">Back</a>
</div>
+ <div class="nav-item block">
+ <div class="nav-text notice">2026 / 09 / 08</div>
+ <a href="news/2026/2026_09_08-license_changes.html" class="nav-text link">License Changes</a>
+ </div>
<div class="nav-item block">
<div class="nav-text notice">2026 / 04 / 30</div>
<a href="news/2026/2026_04_30-fll_0_8_1_and_0_6_16_releases.html" class="nav-text link">FLL 0.8.1 and 0.6.16 Releases</a>
<h1 class="section-title h h1">Year 2026 News</h1>
</header>
- <article id="2026_04_30-fll_0_8_1_and_0_6_16_releases" class="article">
+ <article id="2026_09_08-license_changes" class="article">
<header class="article-header header">
+ <h2 id="2026_09_08-license_changes-title" class="article-title h h2">2026 / 09 / 08 - License Changes</h2>
+ </header>
+
+ <div class="article-content">
+ <p class="p">
+ I have been sitting back and observing some of the ongoing events regarding <abbr title="Lossy Computer Generation">LCG</abbr>, copyright licenses, and even terms of service agreements.
+ Existing precedence is being ignored if not forgotten.
+ Long standing language is being redefined.
+ Parasitic terms of services have been designed and are being used.
+ </p>
+
+ <p class="p">
+ My answer to all of this is to clarify the copyright licenses to ensure that the original intent, behavior, and expectations remain and hold true.
+ Implementing this, however, is a bit tricky.
+ I do not want to rewrite any existing licenses, such as the <abbr title="GNU Lesser General Public License">LGPL</abbr> license.
+ </p>
+
+ <p class="p">
+ I have decided that the solution is to re-license using a wrapping license in order to avoid directly modifying the wrapped licenses.
+ The new license only serves a single purpose of providing clarification and protections while still preserving the terms of the wrapped licenses as much as possible.
+ This new license, called <a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0</a>, supersedes anything in the wrapped license to provide the necessary protections.
+ </p>
+
+ <p class="p">
+ The <a href="licenses/oslv1_1.html" class="link"><abbr title="Open Standard License">OSL</abbr></a> is directly changed because I wrote the original license and I can just create a new version.
+ All other licenses are to be wrapped.
+ </p>
+
+ <p class="p">
+ The full license terms are available here:
+ </p>
+
+ <ul>
+ <li><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0</a></li>
+ <li><a href="licenses/oslv1_1.html" class="link">Open Standard License Version 1.1</a></li>
+ </ul>
+
+ <p class="p">
+ <a id="2026_09_08-license_changes-more" href="news/2026/2026_09_08-license_changes.html" class="content link" aria-labelledby="2026_09_08-license_changes-more 2026_09_08-license_changes-title">Continue reading…</a>
+ </p>
+ </div>
+ </article>
+
+ <article id="2026_04_30-fll_0_8_1_and_0_6_16_releases" class="article">
+ <header class="article-header header separate">
<h2 id="2026_04_30-fll_0_8_1_and_0_6_16_releases-title" class="article-title h h2">2026 / 04 / 30 - FLL 0.8.1 and 0.6.16 Releases</h2>
</header>
<link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
<link type="text/html" rel="license" href="licenses.html">
<link type="text/html" rel="prev" href="news/2026/2026_03_11-gateron_red_pi_500_plus.html">
+ <link type="text/html" rel="next" href="news/2026/2026_09_08-license_changes.html">
</head>
<body id="kevux" class="kevux no-js news">
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>News - 2026/09/08 - License Changes</title>
+
+ <base href="../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="News post on 2026/09/08.">
+ <meta name="keywords" content="Featureless, FLL, Kevin Day, Kevux, Linux, Library, Distribution, Open-Source, News, 2026">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="news/2026/2026_09_08-license_changes.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ <link type="text/html" rel="prev" href="news/2026/2026_04_30-fll_0_8_1_and_0_6_16_releases.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js news">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item active"><a href="news.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="news/2026.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block highlight unlink">
+ <div class="nav-text notice">2026 / 09 / 08</div>
+ <div class="nav-text unlink">License Changes</div>
+ </div>
+ <div class="nav-item block">
+ <a href="news/2026/2026_09_08-license_changes.html#lcg_problem" class="nav-text link"><div>The LCG Problem</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="news/2026/2026_09_08-license_changes.html#terms_problem" class="nav-text link"><div>The Terms of Services Problem</div></a>
+ </div>
+ <div class="nav-item block">
+ <a href="news/2026/2026_09_08-license_changes.html#solution" class="nav-text link"><div>New License Solution</div></a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="news/2026/2026_09_08-license_changes.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="news/2026/2026_09_08-license_changes.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">2026 / 09 / 08 - License Changes</h1>
+ </header>
+
+ <div class="main-content">
+ <p class="p">
+ I have been sitting back and observing some of the ongoing events regarding <abbr title="Lossy Computer Generation">LCG</abbr>, copyright licenses, and even terms of service agreements.
+ Existing precedence is being ignored if not forgotten.
+ Long standing language is being redefined.
+ Parasitic terms of services have been designed and are being used.
+ </p>
+
+ <p class="p">
+ My answer to all of this is to clarify the copyright licenses to ensure that the original intent, behavior, and expectations remain and hold true.
+ Implementing this, however, is a bit tricky.
+ I do not want to rewrite any existing licenses, such as the <abbr title="GNU Lesser General Public License">LGPL</abbr> license.
+ </p>
+
+ <p class="p">
+ I have decided that the solution is to re-license using a wrapping license in order to avoid directly modifying the wrapped licenses.
+ The new license only serves a single purpose of providing clarification and protections while still preserving the terms of the wrapped licenses as much as possible.
+ This new license, called <a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0</a>, supersedes anything in the wrapped license to provide the necessary protections.
+ </p>
+
+ <p class="p">
+ The <a href="licenses/oslv1_1.html" class="link"><abbr title="Open Standard License">OSL</abbr></a> is directly changed because I wrote the original license and I can just create a new version.
+ All other licenses are to be wrapped.
+ </p>
+
+ <p class="p">
+ The full license terms are available here:
+ </p>
+
+ <ul>
+ <li><a href="licenses/clarifiedv1_0.html" class="link">Clarified 1.0</a></li>
+ <li><a href="licenses/oslv1_1.html" class="link">Open Standard License Version 1.1</a></li>
+ </ul>
+
+ <section id="lcg_problem" class="section">
+ <header class="section-header header separate">
+ <h2 id="lcg_problem-title" class="section-title h h2">The LCG Problem</h2>
+ </header>
+
+ <div class="section-content">
+ <p class="p">
+ <abbr title="Lossy Computer Generation">LCG</abbr> has appeared like a parasite in the computing world.
+ Consuming software and spitting out a modified form.
+ Now, any reasonable and sane person that has lived in the computer world for any significant amount of time would realize that computer software revolves around copying.
+ There are no physical objects to be moved, created, or destroyed.
+ There is only thought.
+ And software is a representation of that thought via some set of languages.
+ To do anything with that thought, it must be copied.
+ Be it from hard drive to RAM, or be it from one computer to another.
+ </p>
+
+ <p class="p">
+ Recent court rulings in various locations have shown that the courts might have lost all memory of existing precedence or might have gotten confused or otherwise tricked by the word games that surrounds <abbr title="Lossy Computer Generation">LCG</abbr>.
+ </p>
+ </div>
+ </section>
+
+ <section id="terms_problem" class="section">
+ <header class="section-header header separate">
+ <h2 id="terms_problem-title" class="section-title h h2">The Terms of Services Problem</h2>
+ </header>
+
+ <div class="section-content">
+ <p class="p">
+ The terms of services of various services have started sneaking in language to try to get an individual to waive licenses and other matters.
+ This is at its core is a form of tricker and theft.
+ </p>
+
+ <p class="p">
+ A moral entity that provides such a terms of service does not intend to violate these restrictions nor does it intend to engage in any trickery or theft.
+ Therefore, a reasonable person could conclude that the intent and purpose is not to bypass those restrictions and requirements and is instead targetted towards non-open-source software that is making it available to a given service.
+ How would a moral entity handle all of these details?
+ By simply having the proprietary nature waived.
+ </p>
+
+ <p class="p">
+ Open-source licenses typical provide language that makes this moot.
+ There essentially is nothing to waive because it is already made freely available given the terms and restrictions outlined in a particular license.
+ </p>
+
+ <p class="p">
+ I could easily and reasonably assume that therefore the open-source licenses are not waived in such cases.
+ I refuse to assume.
+ </p>
+ </div>
+ </section>
+
+ <section id="solution" class="section">
+ <header class="section-header header separate">
+ <h2 id="solution-title" class="section-title h h2">New License Solution</h2>
+ </header>
+
+ <div class="section-content">
+ <p class="p">
+ The solution is to create a new license that wraps existing license and modify existing licenses to apply new terms.
+ </p>
+
+ <p class="p">
+ Only these terms aren't intended to change either the wrapped license or the modified license.
+ Instead, these terms clarify the terminology and expectations.
+ </p>
+
+ <p class="p">
+ One such expectation is to explicitly state that the licenser themselves may not waive anything.
+ This helps avoid parasitic terms of services from attempting to trick a person into giving up possession of their copyrighted material or surrender their rights therein.
+ </p>
+
+ <p class="p">
+ These restrictions on the licenser do not prohibit the licenser from explicitly, with full intent and knowledge and without coercion of any form, re-licensing something.
+ This allows for changes without having to worry about any form of parasitic agreements and trickery.
+ </p>
+ </div>
+ </section>
+
+ <p class="p">
+ <strong class="strong">Kevin Day</strong>
+ </p>
+ </div>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
projects / kevux.org-website / commitdiff