commit aa65703a10ee3605713df20afa5a0483163e92b8
parent ed44ef747b200b46e3cd4e87140fb544c315d914
Author: ugrnm <ultrageranium@bleu255.com>
Date: Fri, 6 Nov 2026 14:26:39 +0100
editing guideline update wip
Diffstat:
| M | editing.mdwn | | | 53 | ++++++++++++++++++++++++++++++++++++----------------- |
1 file changed, 36 insertions(+), 17 deletions(-)
diff --git a/editing.mdwn b/editing.mdwn
@@ -1,18 +1,34 @@
-To edit the wiki, you need to be part of the Forking Paths [[circle]].
+To edit the wiki, you need to be part of the orchad [[circle]].
-Style
------
+Intention
+---------
Permacomputing wiki is not Wikipedia, so being neutral or encyclopedic is
not among our goals, and original research is encouraged. However, it is a
-collaborative project, so if you want to make express an opinion the other editors
-may not agree with, please use the relevant Discussion page, and make sure to
-sign your comment with your handle. Go to the Discussion page, in the top menu
-of this page for an example.
+collaborative project, so if you want to express an opinion the other editors
+may not agree with, please discuss it in the orchad circle, or the bbs forum.
+It can be possible that a page or entry needs to be written to take into acount
+multiple perspectives. Keep in mind however that we aim at hosting material
+that can help us move the discourse and practice forward, so
+[https://en.wikipedia.org/wiki/Pharmakon pharmakonesque] deadlocks should be
+avoided.
+
+
+Wiki areas
+----------
+We do not have fine grained permissions and would like to implement bureauracy
+with wiki editing, so please be mindful of the following house rules:
-Copyediting recommendations
----------------------------
+* 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.
+* 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.
+* Properties: this page is an ideal starting point to document and address positive and negative aspects of computational systems.
+* Getting Started: could do with a cleanup, and simplifications, and checking overlap and duplicate purpose with the
+
+
+Copyediting style
+------------------
1. explain the abbreviations before using it (ex. Operations Systems (OS) are
@@ -24,19 +40,19 @@ Copyediting recommendations
derived from the original Unix." First, explain the original Unix, or
rearrange the sentences where you explain what unix is, then explain that
there are multiple versions, an original and others). Same for people
-mentioned, quotes, etc.
+ mentioned, quotes, etc.
3. explain the relevance of a quote.
4. transition between paragraphs, quotes etc. is key. similar to the rule
above, make sure the paragraphs are transitioning from one point to another.
-5. avoid jargon. if a technical/academic/etc term needs to be used, maybe it
+5. careful with jargon. if a technical/academic/etc term needs to be used, maybe it
needs its own page as well. (i.e. "it refers to a very specific kind of
- 'digital', a highly technoprogressivist and industry-defined kind that
- became prominent in the 'digital revolution' hype of the 1990s."
- technoprogressivist is not a common word that could be understood easily,
- either provide a short explanation or make a page for it)
+ 'digital', a highly technoprogressivist and industry-defined kind that
+ became prominent in the 'digital revolution' hype of the 1990s."
+ technoprogressivist is not a common word that could be understood easily,
+ either provide a short explanation or make a page for it)
6. check if there are other pages you can crosslink in your text (i.e. you
mention hardware, link the hardware page there)
@@ -46,7 +62,7 @@ mentioned, quotes, etc.
8. avoid passive-aggresive language. rather, explain why some concepts are
wrong/didn't work/are bad. (i.e. "digital revolution" hype of the 1990s. why
- was it a hype?)
+ was it a hype?; so-called "alternatives", why so-called? why air-qyotes?)
9. make sure all formatting choices are unified in your text. (i.e.
https://permacomputing.net/Principles/ here, the sub-principles are written
@@ -56,7 +72,10 @@ mentioned, quotes, etc.
11. avoid repetation and redundant words, be concise, simple, clear.
-12. don't forget to save! :D
+12. don't forget to save! EDITING ON THE WEB FOR LONG SESSIONS WITHOUT SAVING
+ INCREASE THE CHANCE OF SAVING RIGHT WHEN YOUR SESSION/AUTH HAS EXPIRED AND
+ YOUR BROWSER MAY NOT HAVE CACHED THE FORM BEFORE SUBMITTING IT. In doubt,
+ for long edits, just quickly copy the form contentto avoid bad surprises.
On attribution, quotes and footnotes
