permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit 6f4239e8109b07534414a0a88b69b85b5b3bc215
parent cb37e056f30998e90d8dd8ad2693bcfcfeef403a
Author: akkartik <akkartik@web>
Date:   Fri, 24 Jun 2022 18:52:03 +0200

initial draft

Diffstat:
Aproperties.mdwn | 18++++++++++++++++++
1 file changed, 18 insertions(+), 0 deletions(-)

diff --git a/properties.mdwn b/properties.mdwn @@ -0,0 +1,18 @@ +Properties +========== + +[[Permacomputing]] is a broad idea that encompasses many concerns. This page is an ongoing attempt to enumerate concerns shared by Permacomputing and/or related [[Communities]]. They're all beneficial. Different communities may strive to get to them in different orders. + +Human use of computing will be more sustainable if: + +* software can run on any hardware architecture (portability) +* software can run on old hardware (salvage, collapse, right to repair) +* software is energy efficient +* software can be used for a long time (archival, low maintenance) +* software is easy to tailor in the field + +Some additional concerns are of indirect interest because they impose costs on the entire end-to-end process of software creation. Software will be more minimalist if: + +* it's always bootstrapped from machine code without circular reasoning (bootstrappable builds) +* it's obvious what source code went into it (reproducible builds) +* it's easy to audit its source code, including all dependencies