commit 97c56294d8c0f43fcd1297584bd517dd5ddd699e
parent d36d652d74af87951b2ca426c7714d6edc6f10ac
Author: ugrnm <ultrageranium@bleu255.com>
Date: Fri, 6 Nov 2026 16:13:15 +0100
Merge branch 'master' of eik:/var/www/git.permacomputing.net/repos/permacomputing
Diffstat:
1 file changed, 20 insertions(+), 10 deletions(-)
diff --git a/editing.mdwn b/editing.mdwn
@@ -12,14 +12,25 @@ Wiki areas
We do not have fine grained permissions and would like to implement as little bureauracy as needed for wiki editing, so please be mindful of the following house rules:
-* **home page**: do not edit. Its content is the result of a few years of trying things out, and it's good enough. If something needs to be changed there beside grammar/spelling. Discuss it in orchard.
+* **[[home page|index]]**: avoid editing. Its content is the result of a few years of trying things out, and it's good enough. If something needs to be changed there beside grammar/spelling. Discuss it in orchard
-* **permacomputing design principles**: do not edit. This section is updated through collective wiki edit-a-thons organised by bitrot. It needs to remain as stable as possible to be useful for everyone. Feel free to fix grammar/spelling though :)
-* **the longer permacomputing introduction**: do not edit, same remarks as the Home page.
+* **[[permacomputing design principles|principles]]**: do not edit. This section is updated through collective wiki edit-a-thons organised by [[bitrot]]. It needs to remain as stable as possible to be useful for everyone. Feel free to fix grammar/spelling though :)
-* **charateristics**: this page is an ideal starting point to add new and improve existing entries that can help better understand limits of computational systems and highlight better approaches.
+* **[[the longer permacomputing introduction|permacomputing]]**: avoid editing, same remarks as the Home page
-* **Getting Started**: could do with a cleanup, and simplifications, and checking overlap and duplicate purpose with the
+* **[[characteristics]]**: this page is an ideal starting point to add new and improve existing entries that can help better understand limits of computational systems and highlight better approaches
+
+* **[[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
+
+* **[[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
+
+* [[Assessments]]: in dire need of cleanup, rethinking, etc
+
+* [[workshop]]: this page is an index for existing and new practical technical documentation, HOWTOs, IRL workshop scripts and material, project blueprints that could be reused by other groups, etc. The workflow is simple. For new projects 1. add/create your page in the "Work in Progress" section, 2. when finalised move it to the "Released" section. For existing released projects, feel free to update/fix/correct the material, however if you want to depart from it too much, just fork it and follow the workflow of new projects and indicate/links that this is based on previously released existing entry xyz, because it's nice.
(Copy)editing style
@@ -33,7 +44,7 @@ We do not have fine grained permissions and would like to implement as little bu
* do not line break within a paragraph
-* to keep the source text readable directly as plaintext markdown, only use two heading levels, <code><h1></code> and </code><h2></code>, using the <code>===</code> and <code>---</code> syntax. If you need to go down to <code><h3></code>, consider using **bold** headers instead, worst case, use a <code>###</code> title
+* to keep the source text readable directly as plaintext markdown, only use two heading levels, <code>h1</code> and </code>h2</code>, using the <code>===</code> and <code>---</code> syntax. If you need to go down to <code>h3</code>, consider using **bold** headers instead, worst case, use a <code>###</code> title
* explain the abbreviations before using it (ex. Operations Systems (OS) are amazing. The OS are actually shit)
@@ -57,6 +68,8 @@ We do not have fine grained permissions and would like to implement as little bu
* avoid repetation and redundant words, be concise, simple, clear.
+* if you see something, edit something :) really if you see a page could need some help with copyediting (specially those written in the early years of the wiki), just do it.
+
Saving/Submitting
-----------------
@@ -102,10 +115,7 @@ Reference style
---------------
When referencing, please use the [Notes and Bibliography version of The Chicago
-Manual of
-Style](https://www.chicagomanualofstyle.org/tools_citationguide/citation-guide-1.html).
-However, this is not an academic paper, don't overthink it or spend ages on it,
-try to make it work as best as you can, it's just to have some overall
+Manual of Style](https://www.chicagomanualofstyle.org/tools_citationguide/citation-guide-1.html). However, this is not an academic paper, don't overthink it or spend ages on it, try to make it work as best as you can, it's just to have some overall
consistency. No sweat :)
