From 45376c848eded261f90f8cd228e4a25a8c2b74e6 Mon Sep 17 00:00:00 2001 From: inference Date: Sun, 24 Mar 2024 10:06:24 +0000 Subject: [PATCH] Improve post-colon description formatting --- about.xhtml | 54 ++++++++++++++++++++++++++--------------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/about.xhtml b/about.xhtml index 7e5beba..2d0efda 100644 --- a/about.xhtml +++ b/about.xhtml @@ -1,7 +1,7 @@ - + @@ -201,7 +201,7 @@

BSD 3-Clause License

SPDX License Identifier: BSD-3-Clause

-

Type: Permissive

+

Type: Permissive

BSD 3-Clause License is a highly-permissive license which allows content licensed under it to be used in any way, whether in source or binary form, and allows sublicensing under a different @@ -213,7 +213,7 @@

GNU General Public License v2.0

SPDX License Identifier: GPL-2.0-only

-

Type: Copyleft

+

Type: Copyleft

GNU General Public License v2.0 is a strong copyleft license which restricts use of content licensed under it by requiring all source code of the content to be publicly available, making @@ -235,7 +235,7 @@

Creative Commons Attribution 4.0 International

SPDX License Identifier: CC-BY-4.0

-

Type: Permissive

+

Type: Permissive

Creative Commons Attribution 4.0 International is a highly-permissive license which allows content licensed under it to be used in any way, in any medium, with the only restriction being the original copyright @@ -282,32 +282,32 @@

There are 4 phases of development. Each phase typically has its own branch in each source code repository. The phases are as follows:

    -
  1. Alpha: Pre-alpha development and alpha-testing occurs in this phase. Features - are added, modified, and/or removed. Fixes and optimisations may also occur if they - are caught during this phase. This is where the majority of changes occur and where - the fine-grained commits can be found. Breakage is highly likely within this phase - as it makes no attempt to be stable or usable due to being where the most rapid - development occurs. Code is tested internally in a fine-grained manner and is moved - to the next phase only when it is deemed feature-complete and reasonably stable for - broader public testing. If you would like to assist in testing code in this phase, - you must use the code and/or tags from the source code repositories due to it not - being available publicly outside of them.
    2. -
  2. Beta: Feature-complete testing occurs in this phase. Only bug fixes and +
  3. Alpha: Pre-alpha development and alpha-testing occurs in this phase. + Features are added, modified, and/or removed. Fixes and optimisations may also occur + if they are caught during this phase. This is where the majority of changes occur + and where the fine-grained commits can be found. Breakage is highly likely within + this phase as it makes no attempt to be stable or usable due to being where the most + rapid development occurs. Code is tested internally in a fine-grained manner and is + moved to the next phase only when it is deemed feature-complete and reasonably + stable for broader public testing. If you would like to assist in testing code in + this phase, you must use the code and/or tags from the source code repositories due + to it not being available publicly outside of them.
    4. +
  4. Beta: Feature-complete testing occurs in this phase. Only bug fixes and optimisations occur in this phase, such as stability and security fixes. This phase is classified as stable enough for broad public testing and is made available publicly in many cases without having to use the source code repositories. Since this phase contains only feature-complete code, no features will be added, modified, or removed in this phase.
    5. -
  5. Release candidate (RC): Feature-complete testing occurs in this phase. Code in - the RC phase is often stable enough for production usage, but is not yet completely - acceptable to be classified as stable by my standards. This phase is often skipped - due to most bugs being caught in the beta phase, but will be used should the need - arise for finer-grained testing beyond what the beta phase can provide. Like the - beta phase, code in this phase is available publicly without requiring usage of the - source code repositories.
    6. -
  6. 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.
    7. +
  7. Release candidate (RC): Feature-complete testing occurs in this phase. + Code in the RC phase is often stable enough for production usage, but is not yet + completely acceptable to be classified as stable by my standards. This phase is + often skipped due to most bugs being caught in the beta phase, but will be used + should the need arise for finer-grained testing beyond what the beta phase can + provide. Like the beta phase, code in this phase is available publicly without + requiring usage of the source code repositories.
    8. +
  8. 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.

When development of a new version has begun, the code within the alpha phase is rebased onto the most recent code from the stable phase before work commences. This cycle continues @@ -723,9 +723,9 @@

Molly is available in 2 flavours:

    -
  • Molly, which includes the same proprietary Google +
  • Molly: Includes the same proprietary Google code as Signal to support more features
    • -
  • Molly-FOSS, which removes the proprietary Google +
  • Molly-FOSS: Removes the proprietary Google code to provide an entirely open-source client