From 8b68bb089c2efb7a615d07af86b668925935719c Mon Sep 17 00:00:00 2001 From: Jordan Bancino Date: Tue, 6 Sep 2022 11:53:38 -0400 Subject: [PATCH] Clean up some weird parts of the site. --- site/index.html | 29 ++--------------------------- 1 file changed, 2 insertions(+), 27 deletions(-) diff --git a/site/index.html b/site/index.html index 0de92cf..151ad80 100644 --- a/site/index.html +++ b/site/index.html @@ -58,11 +58,6 @@ database. This has a number of advantages:
  • It allows Telodendria to run on systems with fewer resources.
    • -
  • -It provides both runtime and data safety and stability. Since no -database is running, there's fewer things that could go wrong because -there's a lot less code running on the system. -
  • @@ -708,9 +703,7 @@ don't get lost.

    Developing

    The primary language used to write Telodendria code is ANSI C. -Yes, that's the original C standard from 1989. The reason this standard -is chosen, and the reason that it will not be changed, is because the -original C is the most portable. Other languages you'll find in the +Other languages you'll find in the Telodendria repository are shell scripts and HTML. If you have any experience at all with any of these languages, your contributions are valuable. Please follow the guidelines in this section to ensure @@ -1071,25 +1064,7 @@ licenses involved.

    • After the headers, but before the checkbox, write a more thorough description of the patch and why it was created. Then, send the resulting patch file to #telodendria-patches:bancino.net, -so it can be discussed and reviewed by the community. If you don't -have a Matrix account, and you really don't want to create -one—ignoring how odd it is that you are trying to contribute -to a Matrix homeserver project—you can email your -patches to jordan@bancino.net. -However, the preferred way of submitting patches is to the official -Matrix room, so I will upload your patch there along with your email -address. If you are going to send patches via email, they must -be plain text emails, and the patch must be in the main body -of the email. No MIME, base64, or printed-quotable garbage. I will -silently reject emails that are not purely plain text. I should be -able to write a raw copy of your message to an mbox -file, and then apply it onto my code right from there, with no -further processing. If you're going to be a regular contributor, -it would just be easier to create a Matrix account. It doesn't have -to be on my public homeserver, but it certainly can be. Note that -the discussion and ultimately the decision on what to do with your -patch will all happen in the Matrix room, so if you submit patches -using email, you'll miss out on any feedback. +so it can be discussed and reviewed by the community.

    Try to keep your patches on topic—make one patch file per feature