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 65002283bcbbb00cdcfa2560fe4390dee9204de2
parent 5fd4def760a1ad11dbd863d6b1206ad281cf54b9
Author: viznut_web <viznut_web@web>
Date:   Thu, 30 Jun 2022 19:09:30 +0200

fix link

Diffstat:
Msoftware.mdwn | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/software.mdwn b/software.mdwn @@ -3,7 +3,7 @@ When assessing software, we should pay attention to: * Is it free from blackbox dependencies such as arbitrary external servers when running, compiling or installing it? Does it tolerate a lack of network connectivity? * Is it legally possible to copy, modify and fork the software? (i.e. is it [[FLOSS]]?) * What kind of libraries, programming languages and other software components does it depend on? How mature are these components (i.e. how much [[software rot]] can be expected due to changing interfaces etc.)? How large is the dependency network? -* How much resources does it require to 1) run the software, 2) modify the software (including recompilation from scratch) and 3) [[bootstrap]] the smallest possible environment (including the [[operating system]]) that can be used to run and develop the software? +* How much resources does it require to 1) run the software, 2) modify the software (including recompilation from scratch) and 3) [[bootstrap|bootstrapping]] the smallest possible environment (including the [[operating system]]) that can be used to run and develop the software? * Are there other software that do the same job? How easy would it be to transition to one of them? * How simple and clearly-defined is the core functionality of the software? How long would it take to write an equivalent software from scratch?