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 d7106bed1c86d248db5c48fb3713c28dda381928
parent fec4f0a574676527583655df2b1c4238aa30db4f
Author: ugrnm <ugrnm@web>
Date:   Fri,  6 Nov 2026 15:25:43 +0100

bold

Diffstat:
Mediting.mdwn | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/editing.mdwn b/editing.mdwn @@ -22,9 +22,9 @@ We do not have fine grained permissions and would like to implement as little bu * **[[Getting Started]]**: in dire need of cleanup, rethinking, and simplifications. Should probably be either merged or decoupled from topics overlapping with the [[principles]] or [[onboarding]] -* **[[Community]]: to update when info about new/existing groups needs to be revised. It should also be a place where we find info about the existing circles +* **[[Community]]**: to update when info about new/existing groups needs to be revised. It should also be a place where we find info about the existing circles -* **[[Library]]: in dire need of cleanup, rethinking, and simplifications. Quite a few random things there that should be removed to focus only on key pmc texts/materials +* **[[Library]]**: in dire need of cleanup, rethinking, and simplifications. Quite a few random things there that should be removed to focus only on key pmc texts/materials * **[[Projects]]**: needs some cleanup, but workflow is stable. Basically each project should have a oneliner and an internal dedicated page. A project page needs to follow a simple template with three sections: 1. a descriptive introduction, 2. a sections explaining the relevance to permacomputing ideas and principles, 3. a section about the limits of the projects, 4. a section with relevant links. Keep it short and to the point See [[cerca]] for a good example. Only add projects that are really relevant to permacomputing, not the first thing you find that you might find remotely interesting. The project entries can be written by anyone, and it's also an option to do that with the assistance of a project's creator(s), assuming they are willing to engage with the critical part about the projects own limits and challenges