Add programming happenings news.
Update the copyright year on numerous pages.
Add the Open Standard License to the website.
Move the year 2023 into its own section and setup the year 2024 pages.
<div class="nav-item block">
<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>
+ </div>
<div class="nav-item block ellipses">
<a href="licenses.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
<a href="licenses.html" class="nav-text link close">Collapse Menu</a>
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.
</p>
<p class="p">
- © 2022-2023 Kevin Day
+ © 2022-2024 Kevin Day
</p>
</div>
</article>
</header>
<div class="article-content">
<p class="p">
- The <abbr title="Featureless Linux Library">FLL</abbr> source code is © 2007-202
3 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-202
4 Kevin Day under the <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr> license.
</p>
<p class="p">
- The <abbr title="Featureless Linux Library">FLL</abbr> standards and specifications are © 2007-2023 Kevin Day under the <abbr title="Open Standard License version 1 or greater">OSLv1+</abbr>. The <abbr title="Open Standard License version 1 or greater">OSLv1+</abbr> 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-2024 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.
<p class="p">
- Documentation contained within the <abbr title="Featureless Linux Library">FLL</abbr> that is not under a specification license is © 2007-202
3 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-202
4 Kevin Day under the <abbr title="Creative Commons Attribution Share Alike 4.0 International">CC By SA 4.0</abbr>.
</p>
</div>
</article>
</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-202
3 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-202
4 Kevin Day under the <abbr title="GNU Lesser General Public License version 2.1 or greater">LGPLv2.1+</abbr>.
</p>
</div>
</article>
</header>
<div class="article-content">
<p class="p">
- Documentation that is used to described specifications (included Application Programming Interfaces) are © 2007-2023 Kevin Day under the <abbr title="Open Standard License version 1 or greater">OSLv1+</abbr>.
+ Documentation that is used to described specifications (included Application Programming Interfaces) are © 2007-2024 Kevin Day under the <a href="licenses/oslv1.html" class="link"><abbr title="Open Standard License version 1 or greater">OSLv1+</abbr></a>.
</p>
<p class="p">
- A
Ll remaining documentation that does not fall under the <abbr title="Open Standard License version 1 or greater">OSLv1+</abbr> are © 2007-2023 Kevin Day under the <abbr title="Creative Commons Attribution Share Alike 4.0 International">CC By SA 4.0</abbr>.
+ A
ll 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-2024 Kevin Day under the <abbr title="Creative Commons Attribution Share Alike 4.0 International">CC By SA 4.0</abbr>.
</p>
</div>
</article>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>Licenses - Open Standard License 1</title>
+
+ <base href="../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="Open Standard License 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.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.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>
+ </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.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">Open Standard License 1.0.
+ February 2024.
+
+This license applies to the Standards and their Specifications and designates legal requirements on Implementations of the Standard and their respective Specifications.
+
+Terminology:
+ - Standard: A set of rules and guidelines.
+ - Specification: A specific interpretation or clarification of a Standard, such as the documentation that describes how to use or follow a Standard.
+ - Implementation: The applying of some Standard or Specification.
+ - API: Application Programming Interface*.
+ - ABI: Application Binary Interface**.
+ - Service: Any action or labor performed by one party for another party (such as one person helping another person).
+ - 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.
+
+* 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.
+
+01) 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: NDA, grant, click-through, or any form of paperwork (including all non-paper forms of paperwork, such as digital forms).
+ 04) There are not and must not be any restrictions on the form of an Implementation of a Standard or Specification.
+ 05) Implementations of the Standard or Specification may be under any license so long as that license
+ 06) This license shall prohibit any form of restricting any parties access to use, implement, extend, or 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.
+ 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 original owner of this license or a party explicitly authorized by the original license owner or party, 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. That is for example, if some court seems deems some part of this illegal then later makes it legal the now re-legalized parts do and must immediately apply once more as if it were never made illegal.
+ 12) When at any point in time under any government any parts of this license is restricted, altered, removed, invalidated or otherwise made illegal (or unlawful) is reversed, restored, or otherwise made legal, lawful, and enforceable again, these parts are immediately in affect again.
+ 13) If at any point in time some party, such as but not limited to a government, makes any such change to this license like those described in [01.11] and the licensee for any reason at any time is no longer subject to said jurisdiction, then those parts of the original license are immediately in effect again as if they were never altered or restricted in the first place. For example, if a licensee leaves the jurisdiction of some government that restricted some part of this license then that restricted part is immediately in affect again now that the licensee is out of the said jurisdiction.
+</pre>
+ </code>
+ </div>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
<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">2023 / 12 / 31</div>
- <a href="news/2023/2023_12_31-fll_0_6_8_release.html" class="nav-text link">FLL 0.6.8 Release</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2023 / 09 / 07</div>
- <a href="news/2023/2023_09_07-fll_0_6_7_release.html" class="nav-text link">FLL 0.6.7 Release</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2023 / 07 / 02</div>
- <a href="news/2023/2023_07_02-fll_0_6_6_release.html" class="nav-text link">FLL 0.6.6 Release</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2023 / 05 / 06</div>
- <a href="news/2023/2023_05_06-turtle_development.html" class="nav-text link">Turtle Development</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2023 / 04 / 29</div>
- <a href="news/2023/2023_04_29-fll_0_6_5_release.html" class="nav-text link">FLL 0.6.5 Release</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2023 / 03 / 16</div>
- <a href="news/2023/2023_03_16-fll_0_6_4_release.html" class="nav-text link">FLL 0.6.4 Release</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2023 / 02 / 06</div>
- <a href="news/2023/2023_02_06-turtle_and_fll.html" class="nav-text link">Turtle and FLL</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2023 / 01 / 14</div>
- <a href="news/2023/2023_01_14-fll_0_6_3_release.html" class="nav-text link">FLL 0.6.3 Release</a>
+ <div class="nav-text notice">2024 / 02 / 24</div>
+ <a href="news/2024/2024_02_24-programming_happenings.html" class="nav-text link">Programming Happenings</a>
</div>
<div class="nav-item block">
<a href="news/2023.html" class="nav-text link">Year 2023 News</a>
<h1 class="section-title h h1">News</h1>
</header>
- <article id="2023_12_31-fll_0_6_8_release" class="article">
+ <article id="2024_02_24-programming_happenings" class="article">
<header class="article-header header">
- <h2 id="2023_12_31-fll_0_6_8_release-title" class="article-title h h2">2023 / 12 / 31 - FLL 0.6.8 Release</h2>
- </header>
-
- <div class="article-content">
- <p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.8 is released.
- </p>
- <p class="p">
- This release is for the start of a new year.
- </p>
- <p class="p">
- My plans going forward are to attempt to date releases using UTC and I date this release as <code class="code">Sun 31 Dec 2023 08:52 PM UTC</code>.
- </p>
- <p class="p">
- There are not many changes and there are no code-based bug fixes.
- Only a single bug fix exists and it is in a specification.
- </p>
- <p class="p">
- This contains mostly specification updates, clarifications, and fixes.
- </p>
- <p class="p">
- The Payload and Simple Packet specifications have "<em class="em">type</em>" added as a recommended Object in the header section for the Payload.
- The size of units is rewritten to make more sense in the Payload and Simple Packet specifications.
- The Payload specification now allows for the "payload" section to be optional.
- </p>
- <p class="p">
- The most notable code change is the explicit casting of <code class="code">uint32_t</code> when doing bit-wise operations for left and right shifting.
- The goal here is to increase the integrity of the design and not allow any opportunity for the compiler or architecture to use a different size.
- </p>
- <p class="p">
- <a id="2023_12_31-fll_0_6_8_release-more" href="news/2023/2023_12_31-fll_0_6_8_release.html" class="content link" aria-labelledby="2023_12_31-fll_0_6_8_release-more 2023_12_31-fll_0_6_8_release-title">Continue reading…</a>
- </p>
- </div>
- </article>
-
- <article id="2023_09_07-fll_0_6_7_release" class="article">
- <header class="article-header header separate">
- <h2 id="2023_09_07-fll_0_6_7_release-title" class="article-title h h2">2023 / 09 / 07 - FLL 0.6.7 Release</h2>
- </header>
-
- <div class="article-content">
- <p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.7 is released.
- </p>
- <p class="p">
- With this release I hope to see a very stable 0.6 release series.
- </p>
- <p class="p">
- Only a single functional feature is added and then it is a bug fix in the guise of a feature.
- The <strong class="strong">Featureless Make</strong> program has an oversight in regards to "<em class="em">specify a custom path</em>" within the buid settings paths.
- I discovered this while working on the <strong class="strong">TacocaT</strong> program in the <strong class="strong">Kevux Tools</strong> project.
- </p>
- <p class="p">
- A new <abbr title="Featureless Setting Specifications">FSS</abbr> standard, <em class="em">FSS-0010 "Encrypted Simple Packet"</em>, is added.
- This is generally going to be in the 0.7.x and greater version
- </p>
- <p class="p">
- I discovered a regression in the 0.6.6 release and possibly earlier regarding the dependencies in the stand alone builds.
- This should no longer be a problem as of 0.6.7.
- </p>
- <p class="p">
- <a id="2023_09_07-fll_0_6_7_release-more" href="news/2023/2023_09_07-fll_0_6_7_release.html" class="content link" aria-labelledby="2023_09_07-fll_0_6_7_release-more 2023_09_07-fll_0_6_7_release-title">Continue reading…</a>
- </p>
- </div>
- </article>
-
- <article id="2023_07_02-fll_0_6_6_release" class="article">
- <header class="article-header header separate">
- <h2 id="2023_07_02-fll_0_6_6_release-title" class="article-title h h2">2023 / 07 / 02 - FLL 0.6.6 Release</h2>
- </header>
-
- <div class="article-content">
- <p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.6 is released.
- </p>
- <p class="p">
- This is release is made in celebration of the Fourth of July.
- </p>
- <p class="p">
- There are about 1500 additional man pages representing the functions in addition to the usual bug fixes.
- The man pages were sort of generated and then manually fixed.
- These man pages are considered good enough but are not great.
- There will likely be a future project to assist in generating man pages that are better than the tools that I currently used.
- </p>
- <p class="p">
- Of particular note is that I found and fixed problems in the <abbr title="Featureless Setting Specifications">FSS</abbr> processing code. The comments were not always being processed correctly resulting in actual Content being missed.
- </p>
- <p class="p">
- The Featureless Make build program has several notable fixes and improvements. The build system has now seen a lot more uses and more corner cases and minor details are addressed. Problems with propogating arguments across builds is now fixed.
- </p>
- <p class="p">
- <a id="2023_07_02-fll_0_6_6_release-more" href="news/2023/2023_07_02-fll_0_6_6_release.html" class="content link" aria-labelledby="2023_07_02-fll_0_6_6_release-more 2023_07_02-fll_0_6_6_release-title">Continue reading…</a>
- </p>
- </div>
- </article>
-
- <article id="2023_05_06-turtle_development" class="article">
- <header class="article-header header separate">
- <h2 id="2023_05_06-turtle_development-title" class="article-title h h2">2023 / 05 / 06 - Turtle Development</h2>
+ <h2 id="2024_02_24-programming_happenings-title" class="article-title h h2">2024 / 02 / 24 - Programming Happenings</h2>
</header>
<div class="article-content">
<p class="p">
- I decided briefly return my focus to <strong class="strong">Turtle Kevux</strong> development following the recent 0.6.5 release of the Featureless Linux Library (<abbr title="Featureless Linux Library">FLL</abbr>). Several good things were discovered. The most notable is that both <a href="https://musl.libc.org/" class="link external">musl-libc</a> (vesion 1.2.4) and <a href="https://valgrind.org/" class="link external">valgrind</a> (version 3.21.0) made some relevant releases. The problems that I have been facing appear to have been resolved. Attempting to boot the kernel revealed some additional problems. These problems are primarily that the display does not display and gives the false impression that the system did not boot.
+ The new year has yielded a large amount of development progress in several of my projects.
+ I have also seen some bad happenings and good happenings in the technology world.
+ With my projects moving into the next stages, I have decided to begin releasing more details of my plans going forward.
</p>
<p class="p">
- <a id="2023_05_06-turtle_development-more" href="news/2023/2023_05_06-turtle_development.html" class="content link" aria-labelledby="2023_05_06-turtle_development-more 2023_05_06-turtle_development-title">Continue reading…</a>
+ This is a longer than usual read and so let me first summarize the topics at hand.
+ The fundamentals of my ideas driving my work and life are now being formalized into what I am calling <em class="em">Project Lighthouse</em>.
+ This is itself not actually a project but instead is an idea from which one may follow with their own projects in not just software technology.
+ My programs and libraries follow these ideas represented by <em class="em">Project Lighthouse</em> and extend into what I call <em class="em">Actual Accessibility</em>.
+ That is to say, the ability to access.
+ My network related code is slowly progressing but it is progressing.
+ My <strong class="strong">TacocaT</strong> program is a small tool that I am using to help brainstorm how I am going to write the network related code.
+ This ultimately shall become the foundation for the <strong class="strong">Furl</strong> program as well as more complex projects.
+ The <strong class="strong">Controller</strong> program is going to see some major work to both utilize this network related code as well as improvements to make it a functional way to break free of the nonsense that is <strong class="strong">SystemD</strong>.
+ I finally got around to setting up <a href="https://git.kevux.org">https://git.kevux.org</a> and making all of my code available there as well as a few others that are not my projects.
</p>
- </div>
- </article>
-
- <article id="2023_04_29-fll_0_6_5_release" class="article">
- <header class="article-header header separate">
- <h2 id="2023_04_29-fll_0_6_5_release-title" class="article-title h h2">2023 / 04 / 29 - FLL 0.6.5 Release</h2>
- </header>
-
- <div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.5 is released.
- </p>
- <p class="p">
- This release contains fixes and improvements discovered during daily use and several back ported fixes.
- </p>
- <p class="p">
- There are several build system improvements to make the project easier to use.
- Several of the project build scripts are out of date in parameter handling and processing.
- Proper Featureless Make functionality that is expected to be supported by the boostrapt script is found lacking in a few small ways.
- </p>
- <p class="p">
- The build setting files and fakefile files in this project should now have some more environment variables added by default.
- These added environment variables are focused on locale.
- </p>
- <p class="p">
- Check out the project on the <a href="fll.html#release" class="link"><abbr title="Featureless Linux Library">FLL</abbr> release</a> page.
- </p>
- <p class="p">
- <a id="2023_04_29-fll_0_6_5_release-more" href="news/2023/2023_04_29-fll_0_6_5_release.html" class="content link" aria-labelledby="2023_04_29-fll_0_6_5_release-more 2023_04_29-fll_0_6_5_release-title">Continue reading…</a>
+ <a id="2024_02_24-programming_happenings-more" href="news/2024/2024_02_24-programming_happenings.html" class="content link" aria-labelledby="2024_02_24-programming_happenings-more 2024_02_24-programming_happenings-title">Continue reading…</a>
</p>
</div>
</article>
- <article id="2023_03_16-fll_0_6_4_release" class="article">
+ <article id="year_2023-news" class="article">
<header class="article-header header separate">
- <h2 id="2023_03_16-fll_0_6_4_release-title" class="article-title h h2">2023 / 03 / 16 - FLL 0.6.4 Release</h2>
+ <h2 id="year_2023-news-title" class="article-title h h2">Year 2023 News</h2>
</header>
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.4 is released.
- </p>
- <p class="p">
- Adds the following stand alone programs:
- </p>
- <ul>
- <li><code class="code">controller</code></li>
- <li><code class="code">fss_identify</code></li>
- <li><code class="code">iki_read</code></li>
- <li><code class="code">iki_write</code></li>
- </ul>
- <p class="p">
- Copyrights are now displayed when the programs are passed the <code class="code">+C/++copyright</code> standardized parameter.
- </p>
- <p class="p">
- The IKI standard is found to be slightly lacking.
- There is a strong need for IKI variables immediately after word-characters that are not part of the variable name.
- The IKI standard and specification is now updated to utilize open bracket '<code class="code">[</code>' (<code class="code">U+005B</code>) and close bracket '<code class="code">]</code>' (<code class="code">U+005D</code>), commonly referred to as "wrap" or "wrapping".
- Such an IKI variable looks like <code class="code">[vocabulary]:"content"</code> (as opposed to <code class="code">vocabulary:"content"</code>).
- New functionality is provided to keep this project compliant with the recent changes to the IKI standard and specifications.
- </p>
- <p class="p">
- A major behavioral bug has been found in the Controller program regarding the "program" operation mode.
- Solving this the simple way would then break other behavior.
- To avoid this, a new feature is implemented, called the "helper" operation mode.
- The "helper" operation mode provides an alternative to "program" operation mode to allow for starting tasks.
- </p>
- <p class="p">
- Check out the project on the <a href="fll.html#release" class="link"><abbr title="Featureless Linux Library">FLL</abbr> release</a> page.
- </p>
- <p class="p">
- <a id="2023_03_16-fll_0_6_4_release-more" href="news/2023/2023_03_16-fll_0_6_4_release.html" class="content link" aria-labelledby="2023_03_16-fll_0_6_4_release-more 2023_03_16-fll_0_6_4_release-title">Continue reading…</a>
- </p>
- </div>
- </article>
-
- <article id="2023_02_06-turtle_and_fll" class="article">
- <header class="article-header header separate">
- <h2 id="2023_02_06-turtle_and_fll-title" class="article-title h h2">2023 / 02 / 06 - Turtle and FLL</h2>
- </header>
-
- <div class="article-content">
- <p class="p">
- I am slowly getting back into building the next <strong class="strong">Turtle Kevux</strong> distribution.
- This distribution is being re-developed in parallel to the <strong class="strong">Featureless Linux Library</strong>.
- I am testing out the 0.6.x releases of the <abbr title="Featureless Linux Library">FLL</abbr> and the Controller program.
- </p>
- <p class="p">
- As for the <strong class="strong">Turtle Kevux</strong> distribution, I have the system now booting.
- I experimented with the trying to build the kernel without the hard disk drivers compiled in.
- I want to use two initrds such that the first is the filesystem that does not change and the second contains the kernel modules.
- This will take more time to figure out than I am willing to spend on this.
- I decided to go back to the old way of booting the system and I am compiling the disk drivers into the kernel.
- </p>
- <p class="p">
- I can now focus on the Controller program as the Init program with the kernel now booting and with a working initrd (which is actually an initramfs, technically speaking).
- </p>
- <p class="p">
- <a id="2023_02_06-turtle_and_fll-more" href="news/2023/2023_02_06-turtle_and_fll.html" class="content link" aria-labelledby="2023_02_06-turtle_and_fll-more 2023_02_06-turtle_and_fll-title">Continue reading…</a>
- </p>
- </div>
- </article>
-
- <article id="2023_01_14-fll_0_6_3_release" class="article">
- <header class="article-header header separate">
- <h2 id="2023_01_14-fll_0_6_3_release-title" class="article-title h h2">2023 / 01 / 14 - FLL 0.6.3 Release</h2>
- </header>
-
- <div class="article-content">
- <p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.3 is released.
- </p>
- <p class="p">
- This release contains breaking changes in the Featureless Make program to address functionality that is missing but should, if not must, be available.
- This primarily adds documentation and fixes a small number of bugs found.
- </p>
- <p class="p">
- Adds the following stand alone programs:
- </p>
- <ul>
- <li><code class="code">fss_status_code</code></li>
- <li><code class="code">status_code</code></li>
- </ul>
- <p class="p">
- There are now man pages for all of the programs.
- These are manually crafted.
- </p>
- <p class="p">
- The Featureless Make program has two new features that are important enough to break the <code class="code">featureless</code> concept as an exception to the rule.
- </p>
- <p class="p">
- The Featureless Make program must be able to install settings files and documentation files.
- The documentation directory now exists.
- This is similar to the documents directory but is entirely focused on documentation that is installed onto the system.
- The documents directory might be synonymous with the standard share directory and the documentation directory might be synonymous with the share/man or share/docs directories.
- </p>
- <p class="p">
- The <abbr title="Featureless Linux Library">FLL</abbr> install scripts are also updated to handle the installation of the settings and documentation files.
- </p>
- <p class="p">
- The Feeatureless Make program now supports the ability to specify a named section on the command line to be able to reasonably act as an alternative to GNU Make.
- It is now possible to create an <code class="code">install</code> section.
- The user could then run <code class="code">fake install</code> in a similar manner to how <code class="code">make install</code> works.
- The core reserved words are never run in this way.
- These core reserved words are <code class="code">build</code>, <code class="code">clean</code>, <code class="code">make</code>, and <code class="code">skeleton</code>.
- </p>
- <p class="p">
- Check out the project on the <a href="fll.html#release" class="link"><abbr title="Featureless Linux Library">FLL</abbr> release</a> page.
- </p>
- <p class="p">
- <a id="2023_01_14-fll_0_6_3_release-more" href="news/2023/2023_01_14-fll_0_6_3_release.html" class="content link" aria-labelledby="2023_01_14-fll_0_6_3_release-more 2023_01_14-fll_0_6_3_release-title">Continue reading…</a>
+ The <a href="news/2023.html" class="content link">news for the year 2023</a> remains available.
</p>
</div>
</article>
<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="2022.html">
+ <link type="text/html" rel="next" href="2024.html">
</head>
<body id="kevux" class="kevux no-js news">
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>Kevux Systems and Software - News - 2024</title>
+
+ <base href="../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="News posts for the year 2024.">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, News, 2024">
+ <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/2024.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="2023.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.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block">
+ <div class="nav-text notice">2024 / 02 / 24</div>
+ <a href="news/2024/2024_02_24-programming_happenings.html" class="nav-text link">Programming Happenings</a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="news/2024.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="news/2024.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">Year 2024 News</h1>
+ </header>
+
+ <article id="2024_02_24-programming_happenings" class="article">
+ <header class="article-header header">
+ <h2 id="2024_02_24-programming_happenings-title" class="article-title h h2">2024 / 02 / 24 - Programming Happenings</h2>
+ </header>
+
+ <div class="article-content">
+ <p class="p">
+ The new year has yielded a large amount of development progress in several of my projects.
+ I have also seen some bad happenings and good happenings in the technology world.
+ With my projects moving into the next stages, I have decided to begin releasing more details of my plans going forward.
+ </p>
+ <p class="p">
+ This is a longer than usual read and so let me first summarize the topics at hand.
+ The fundamentals of my ideas driving my work and life are now being formalized into what I am calling <em class="em">Project Lighthouse</em>.
+ This is itself not actually a project but instead is an idea from which one may follow with their own projects in not just software technology.
+ My programs and libraries follow these ideas represented by <em class="em">Project Lighthouse</em> and extend into what I call <em class="em">Actual Accessibility</em>.
+ That is to say, the ability to access.
+ My network related code is slowly progressing but it is progressing.
+ My <strong class="strong">TacocaT</strong> program is a small tool that I am using to help brainstorm how I am going to write the network related code.
+ This ultimately shall become the foundation for the <strong class="strong">Furl</strong> program as well as more complex projects.
+ The <strong class="strong">Controller</strong> program is going to see some major work to both utilize this network related code as well as improvements to make it a functional way to break free of the nonsense that is <strong class="strong">SystemD</strong>.
+ I finally got around to setting up <a href="https://git.kevux.org">https://git.kevux.org</a> and making all of my code available there as well as a few others that are not my projects.
+ </p>
+ <p class="p">
+ <a id="2024_02_24-programming_happenings-more" href="news/2024/2024_02_24-programming_happenings.html" class="content link" aria-labelledby="2024_02_24-programming_happenings-more 2024_02_24-programming_happenings-title">Continue reading…</a>
+ </p>
+ </div>
+ </article>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>News - 2024/02/24 - Programming Happenings</title>
+
+ <base href="../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="News post on 2024/02/24.">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, News, 2024">
+ <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/2024/2024_02_24-programming_happenings.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/2024/2024_02_24-programming_happenings.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/2024.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block highlight unlink">
+ <div class="nav-text notice">2024 / 02 / 24</div>
+ <div class="nav-text unlink">Programming Happenings</div>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="news/2024/2024_02_24-programming_happenings.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="news/2024/2024_02_24-programming_happenings.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">2024 / 02 / 24 - Programming Happenings</h1>
+ </header>
+
+ <div class="main-content">
+ <p class="p">
+ The new year has yielded a large amount of development progress in several of my projects.
+ I have also seen some bad happenings and good happenings in the technology world.
+ With my projects moving into the next stages, I have decided to begin releasing more details of my plans going forward.
+ </p>
+ <p class="p">
+ This is a longer than usual read and so let me first summarize the topics at hand.
+ The fundamentals of my ideas driving my work and life are now being formalized into what I am calling <em class="em">Project Lighthouse</em>.
+ This is itself not actually a project but instead is an idea from which one may follow with their own projects in not just software technology.
+ My programs and libraries follow these ideas represented by <em class="em">Project Lighthouse</em> and extend into what I call <em class="em">Actual Accessibility</em>.
+ That is to say, the ability to access.
+ My network related code is slowly progressing but it is progressing.
+ My <strong class="strong">TacocaT</strong> program is a small tool that I am using to help brainstorm how I am going to write the network related code.
+ This ultimately shall become the foundation for the <strong class="strong">Furl</strong> program as well as more complex projects.
+ The <strong class="strong">Controller</strong> program is going to see some major work to both utilize this network related code as well as improvements to make it a functional way to break free of the nonsense that is <strong class="strong">SystemD</strong>.
+ I finally got around to setting up <a href="https://git.kevux.org" class="link external">https://git.kevux.org</a> and making all of my code available there as well as a few others that are not my projects.
+ </p>
+ </div>
+
+ <section id="project_lighthouse" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Project Lighthouse</h2>
+ </header>
+
+ <div class="section-content">
+ <p class="p">
+ The <em class="em">Project Lighthouse</em> is the accumulation of my ideas, beliefs, and principles coalesced into a formal, written, idea.
+ The word <em class="em">Project</em> is being used a little oddly here.
+ Because <em class="em">Project Lighthouse</em> is an idea there is no actual literal project.
+ The use of project is instead intended to be used such that when someone is following the principles represented by <em class="em">Project Lighthouse</em> the could state that their project is a lighthouse project.
+ This can then be represented by a logo or a short statement of <em class="em">Project Lighthouse</em>.
+ </p>
+ <p class="p">
+ If you have been closely following any of my projects, then you might be able to put together an idea on what the <em class="em">Project Lighthouse</em> ideals are.
+ This year, the year 2024, is the year that I will be formally writing down these ideas and principles.
+ Until then, consider this a teaser for what is to come.
+ </p>
+ <p class="p">
+ At its root, the <em class="em">Project Lighthouse</em> serves one solitary purpose.
+ A become of hope.
+ Like a traditional lighthouse, it just sits there, passively, as a light in the darkness, a beacon of hope, or an icon of warning.
+ One specific principle is to not force anything on others.
+ A lighthouse project, a <em class="em">Project Lighthouse</em>, does not impose itself on others but allows others to come and go as they please.
+ Think, "Here be knowledge".
+ There is likely a close relationship to a <em class="em">Project Lighthouse</em> and a traditional library (not in the software technology sense but instead as in an actual traditional library with books and such).
+ </p>
+ </div>
+ </section>
+
+ <section id="actual_accessibility" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Actual Accessibility</h2>
+ </header>
+
+ <div class="section-content">
+ <p class="p">
+ Here and there I have mentioned the ideas of <em class="em">Actual Accessibility</em>, but I have not truly formalized them into words.
+ There is a whole slew of problems in the current day society where people fail to use words with their actual meaning.
+ This is not normally a real big deal, but then somebody turns around and popularizes mis-used terminology into what is sometimes referred t as a <em class="em">buzz word</em>.
+ Even worse, there are some words that have been hi-jacked and mis-used in the legal system.
+ Adding the word <em class="em">Actual</em> to the word <em class="em">Accessibility</em> is done to emphasize that I am not referring to the absurd non-sense that the American legal system has done to the word <em class="em">Accessibility</em>.
+ </p>
+ <p class="p">
+ Accessibility, or as I am calling it here, <em class="em">Actual Accessibility</em> is simple one thing.
+ The ability to access.
+ That is it.
+ </p>
+ <p class="p">
+ This concept of <em class="em">Actual Accessibility</em> also happens to be a necessity for <em class="em">Project Lighthouse</em> and should provide some further insight into that set of principles.
+ </p>
+ <p class="p">
+ Open-source provides great insight and ability into <em class="em">Actual Accessibility</em>.
+ If the legal gets in the way of the ability to access something, than that makes things less accessible.
+ Pretty simple.
+ </p>
+ <p class="p">
+ Proprietary software, therefore by design, cannot be actually accessible.
+ Open-source, however, by itself does not solve the problem.
+ It is only a step in the correct direction.
+ The true solution is at its root, language.
+ The ability to communicate is the core of the solution to <em class="em">Actual Accessibility</em>.
+ </p>
+ <p class="p">
+ In software, a language is defined by a standard and a standard therefore provides the <em class="em">Actual Accessibility</em>.
+ To truly do this one must have an open-standard.
+ </p>
+ <p class="p">
+ My solution to this part of the problem is the formal introduction of the <a href="licenses/oslv1.html" class="link">Open Standard License 1.0</a>.
+ Computing machinery must be capable of talking with other computer machinery as well as with humans (or even animals).
+ </p>
+ <p class="p">
+ Future news posts may contain more information on my thoughts regarding <em class="em">Actual Accessibility</em>.
+ </p>
+ </div>
+ </section>
+
+ <section id="network_projects" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Network Projects</h2>
+ </header>
+
+ <div class="section-content">
+ <p class="p">
+ I have been doing a lot of research and studying and there is yet more to come.
+ My goal is to complete a network source code library for providing the functionality that I need to go alongside or entirely replace existing network related tools.
+ </p>
+ <p class="p">
+ My goal is to write the program called <strong class="strong">Furl</strong>.
+ This is a play on the word <em class="em">curl</em> (and the program called <strong class="strong">Curl</strong>) and the <abbr title="Featureless Linux Library">FLL</abbr>.
+ Like curl, the word furl also happens to relate to curling, such as with curling a flag.
+ The naming is quite convenient.
+ </p>
+ <p class="p">
+ I acknowledge that the networking is a large task.
+ I have decided to first write a simpler program to help me brainstorm ideas on how to write <strong class="strong">Furl</strong>.
+ Introduce <strong class="strong">TacocaT</strong>.
+ And yes, that last letter <em class="em">T</em> is capitalized.
+ </p>
+ <p class="p">
+ The design purpose of <strong class="strong">TacocaT</strong> is to talk to itself.
+ This program shall perform similar functions as the existing tool, called <strong class="strong">Netcat</strong>.
+ Once again, I have found some convenient words to play with when naming the project.
+ </p>
+ <p class="p">
+ Ultimately, I want to merge some of this network related code into the <strong class="strong">Controller</strong> program so that it may better operate as an system initializer. This will further allow me to avoid what I call the nonsense that is <strong class="strong">SystemD</strong>.
+ </p>
+ <p class="p">
+ The network related code shall not stop here.
+ Implementing the networking sets up the foundation to do something even more extreme.
+ Write my own web-browser.
+ This is a crazy large task, but everything that I am already doing can lead to this anyway.
+ I won't implement a direct replacement in some ways and in others I expect to make compromises.
+ But for now, one step at a time.
+ I am simply tired of the utter trash that has become of the current day web-browsers.
+ </p>
+ </div>
+ </section>
+
+ <section id="kevux_git_server" class="section">
+ <header class="section-header header separate">
+ <h2 class="section-title h h2">Kevux Git Server</h2>
+ </header>
+
+ <div class="section-content">
+ <p class="p">
+ I finally got around to doing this.
+ I created the sub-domain a while back but nothing came up of it.
+ That has now changed.
+ Head on over to <a href="https://git.kevux.org" class="link external">https://git.kevux.org</a> to check out the repositories.
+ </p>
+ <p class="p">
+ The repositories are mostly Kevux based repositories.
+ Some others have been added for projects that I think are small, and possibly nearly forgotten, but should be preserved.
+ The <a href="https://git.kevux.org/?p=doxy2man;a=summary" class="link external">doxy2man</a> repository is one such example.
+ </p>
+ </div>
+ </section>
+
+ <div class="section-content">
+ <p class="p">
+ <strong class="strong">Kevin Day</strong>
+ </p>
+ </div>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
<li>Backup Source 1: <a href="https://github.com/thekevinday/fll/" class="link external">https://github.com/thekevinday/fll/</a></li>
<li>Backup Source 2: <a href="https://gitlab.com/kevuxer/fll/" class="link external">https://gitlab.com/kevuxer/fll/</a></li>
<li>Backup Source 3: <a href="https://codeberg.org/kevuxer/fll" class="link external">https://codeberg.org/kevuxer/fll</a></li>
+ <li>Backup Source 4: <a href="https://git.kevux.org" class="link external">https://git.kevux.org</a></li>
</ul>
</div>
</article>
<li><a href="https://github.com/thekevinday/kevux.org-website" class="link external">https://github.com/thekevinday/kevux.org-website</a></li>
<li><a href="https://gitlab.com/kevuxer/kevux.org-website" class="link external">https://gitlab.com/kevuxer/kevux.org-website</a></li>
<li><a href="https://codeberg.org/kevuxer/kevux.org-website" class="link external">https://codeberg.org/kevuxer/kevux.org-website</a></li>
+ <li><a href="https://git.kevux.org/?p=kevux.org-website;a=summary" class="link external">https://git.kevux.org/?p=kevux.org-website;a=summary</a></li>
</ul>
</div>
</article>
projects / kevux.org-website / commitdiff