Inferencium/website
1
0
Fork 0
Code Issues Activity

Fix ordered and unordered lists

Browse Source 
Lists are standalone tags, not placed within paragraph tags. Also, fix
code indentation due to this change.
This commit is contained in:
inference 2024-02-15 06:36:56 +00:00
parent 078ac5e5ac
commit 30c5be1f17
Signed by: inference
SSH Key Fingerprint: SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
1 changed files with 50 additions and 61 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

111
about.xhtml
View File

@ -1,7 +1,7 @@
<!DOCTYPE html> <!DOCTYPE html>
<!-- Inferencium - Website - About --> <!-- Inferencium - Website - About -->
<!-- Version: 8.1.0 --> <!-- Version: 8.2.0-alpha.1 -->
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
@ -350,54 +350,46 @@
<h3><a href="#versioning-phases">What Are the Phases?</a></h3> <h3><a href="#versioning-phases">What Are the Phases?</a></h3>
<p>There are 4 phases of development. Each phase typically has <p>There are 4 phases of development. Each phase typically has
its own branch in each source code repository. The phases are as its own branch in each source code repository. The phases are as
follows: follows:</p>
<ol> <ol>
<li>Alpha: Pre-alpha development and alpha <li>Alpha: Pre-alpha development and alpha testing
testing occurs in this phase. Features are occurs in this phase. Features are added, modified,
added, modified, and/or removed. Fixes and and/or removed. Fixes and optimisations may also occur
optimisations may also occur if they are caught if they are caught during this phase. This is where the
during this phase. This is where the majority of majority of changes occur and where the fine-grained
changes occur and where the fine-grained commits commits can be found. Breakage is highly likely within
can be found. Breakage is highly likely within this phase as it makes no attempt to be stable or usable
this phase as it makes no attempt to be stable due to being where the most rapid development occurs.
or usable due to being where the most rapid Code is tested internally in a fine-grained manner and
development occurs. Code is tested internally in is moved to the next phase only when it is deemed
a fine-grained manner and is moved to the next feature-complete and reasonably stable for broader
phase only when it is deemed feature-complete public testing. If you would like to assist in testing
and reasonably stable for broader public code in this phase, you must use the code and/or tags
testing. If you would like to assist in testing from the source code repositories due to it not being
code in this phase, you must use the code and/or available publicly outside of them.</li>
tags from the source code repositories due to it <li>Beta: Feature-complete testing occurs in this phase.
not being available publicly outside of Only bug fixes and optimisations occur in this phase,
them.</li> such as stability and security fixes. This phase is
<li>Beta: Feature-complete testing occurs in classified as stable enough for broad public testing and
this phase. Only bug fixes and optimisations is made available publicly in many cases without having
occur in this phase, such as stability and to use the source code repositories. Since this phase
security fixes. This phase is classified as contains only feature-complete code, no features will be
stable enough for broad public testing and is added, modified, or removed in this phase.</li>
made available publicly in many cases without <li>Release candidate (RC): Feature-complete testing
having to use the source code repositories. occurs in this phase. Code in the RC phase is often
Since this phase contains only feature-complete stable enough for production usage, but is not yet
code, no features will be added, modified, or completely acceptable to be classified as stable by my
removed in this phase.</li> standards. This phase is often skipped due to most bugs
<li>Release candidate (RC): Feature-complete being caught in the beta phase, but will be used should
testing occurs in this phase. Code in the RC the need arise for finer-grained testing beyond what the
phase is often stable enough for production beta phase can provide. Like the beta phase, code in
usage, but is not yet completely acceptable to this phase is available publicly without requiring usage
be classified as stable by my standards. This of the source code repositories.</li>
phase is often skipped due to most bugs being <li>Stable: Feature-complete and well-tested code is
caught in the beta phase, but will be used moved to this phase. Code in this phase is deemed to be
should the need arise for finer-grained testing stable enough for production usage and full support is
beyond what the beta phase can provide. Like the provided.</li>
beta phase, code in this phase is available </ol>
publicly without requiring usage of the source
code repositories.</li>
<li>Stable: Feature-complete and well-tested
code is moved to this phase. Code in this phase
is deemed to be stable enough for production
usage and full support is provided.</li>
</ol>
</p>
<p>When development of a new version has begun, the code within <p>When development of a new version has begun, the code within
the alpha phase is rebased onto the most recent code from the the alpha phase is rebased onto the most recent code from the
stable phase before work commences. This cycle continues for the stable phase before work commences. This cycle continues for the
@ -767,18 +759,15 @@
to protect user keys using the device's hardware to protect user keys using the device's hardware
security module.</p> security module.</p>
<p>Molly is available in <p>Molly is available in
<a href="https://github.com/mollyim/mollyim-android#free-and-open-source">2 flavours</a>: <a href="https://github.com/mollyim/mollyim-android#free-and-open-source">2 flavours</a>:</p>
<ul> <ul>
<li>Molly, which includes the <li>Molly, which includes the same
same proprietary Google code as proprietary Google code as Signal to
Signal to support more support more features.</li>
features.</li> <li>Molly-FOSS, which removes the
<li>Molly-FOSS, which removes proprietary Google code to provide an
the proprietary Google code to entirely open-source client.</li>
provide an entirely open-source </ul>
client.</li>
</ul>
</p>
</td> </td>
<td headers="software-smartphone-source_model molly"> <td headers="software-smartphone-source_model molly">
Open-source<br/> Open-source<br/>