editing.mdwn (7211B)
1 To edit the wiki, you need to be part of the Forking Paths [[circle]]. 2 3 Style 4 ----- 5 6 Permacomputing wiki is not Wikipedia, so being neutral or encyclopedic is 7 not among our goals, and original research is encouraged. However, it is a 8 collaborative project, so if you want to make express an opinion the other editors 9 may not agree with, please use the relevant Discussion page, and make sure to 10 sign your comment with your handle. Go to the Discussion page, in the top menu 11 of this page for an example. 12 13 14 Copyediting recommendations 15 --------------------------- 16 17 18 1. explain the abbreviations before using it (ex. Operations Systems (OS) are 19 amazing. The OS are actually shit). 20 21 2. make sure the references are explained before using them. (ex. "Unix is a 22 multi-user operating system whose development was started in 1969 by Ken 23 Thompson and Dennis Ritchie, as well as an entire family of operating system 24 derived from the original Unix." First, explain the original Unix, or 25 rearrange the sentences where you explain what unix is, then explain that 26 there are multiple versions, an original and others). Same for people 27 mentioned, quotes, etc. 28 29 3. explain the relevance of a quote. 30 31 4. transition between paragraphs, quotes etc. is key. similar to the rule 32 above, make sure the paragraphs are transitioning from one point to another. 33 34 5. avoid jargon. if a technical/academic/etc term needs to be used, maybe it 35 needs its own page as well. (i.e. "it refers to a very specific kind of 36 'digital', a highly technoprogressivist and industry-defined kind that 37 became prominent in the 'digital revolution' hype of the 1990s." 38 technoprogressivist is not a common word that could be understood easily, 39 either provide a short explanation or make a page for it) 40 41 6. check if there are other pages you can crosslink in your text (i.e. you 42 mention hardware, link the hardware page there) 43 44 7. avoid using brackets (as much as possible), it breaks the reading (and 45 comprehending) flow (quite a bit) (right?). 46 47 8. avoid passive-aggresive language. rather, explain why some concepts are 48 wrong/didn't work/are bad. (i.e. "digital revolution" hype of the 1990s. why 49 was it a hype?) 50 51 9. make sure all formatting choices are unified in your text. (i.e. 52 https://permacomputing.net/Principles/ here, the sub-principles are written 53 as a paragraph first, and then as list. should be the same style). 54 55 10. use formatting sparingly and with purpose. 56 57 11. avoid repetation and redundant words, be concise, simple, clear. 58 59 12. don't forget to save! :D 60 61 62 On attribution, quotes and footnotes 63 ------------------------------------ 64 65 At the current stage of maturity of this wiki, it is often not advisable to 66 write a comprehensive articles about a topic if someone else has already done 67 it elsewhere. Put in a link to that external resource instead. (In the future, 68 we will perhaps want to host copies of all these "dependencies" in the local 69 repository as well, but not yet.) 70 71 When introducing a new term, please try to include a proper and non-biased 72 definition of the topic before proceeding to the permacomputing-specific points 73 of view. You can use [[Wikipedia]] or other sources for this, **just make sure 74 you properly attribute and quote** (we are CC0, Wikipedia is CC-BY-SA, so you 75 can't just copy-and-paste even from there). 76 77 If you rely on other sources for the writing of a section, do not be lazy or 78 mindlessly copypaste from other sources. In general, **do not invisibilize 79 people from which you took inspiration and/or learned something from**. Take 80 the opportunity of contributing to this wiki to also point to their work and 81 research. You must properly attribute your source. You have 4 options: 82 83 * **Hyperlinks:** Sometimes it's enough to point to external reference as an hyperlink if there is not much to discuss. For instance [Ursula K. Le Guin has an interesting take on technology](http://www.ursulakleguinarchive.com/Note-Technology.html). 84 * **Footnotes:** Can be handy to drift a bit[^drift] but also to give a proper footnote reference when paraphrasing and referencing the thoughts of someone else. For instance Ursula K. Le Guin has been critical of a specific usage of the work *technology* when misused to only refer to the most recent developments, which also happen to be the most problematic[^leguinref]. 85 * **Inline quotes:** Use this with footnotes when you want to quote something short inline. For instance Ursula K. Le Guin offers to understand technology more broadly as "the active human interface with the material world"[^leguinrefquote]. 86 * **Block quotes:** Finally, you may want to quote entirely a part of someone else's writing, in which case, use the block quote formatting, with a footnote for the reference. For instance here is how Ursula K. Le Guin suggests to reconsider how we use the word *technology*: 87 88 > Technology is the active human interface with the material world. 89 > But the word is consistently misused to mean only the enormously complex and specialised technologies of the past few decades, supported by massive exploitation both of natural and human resources. 90 > This is not an acceptable use of the word. [^leguinrefquote2] 91 92 [^drift]: parenthesis could be used as well, sure, or long — em dashes, but if you're going to fork the discussion to something that's too long to fit in the flow of the main text, and that does not need its own page, then a footnote can be quite handy. 93 [^leguinref]: See Ursula K. Le Guin, "A Rant About 'Technology'," 2004, [http://www.ursulakleguinarchive.com/Note-Technology.html](http://www.ursulakleguinarchive.com/Note-Technology.html). 94 [^leguinrefquote]: Ursula K. Le Guin, "A Rant About 'Technology'," 2004, [http://www.ursulakleguinarchive.com/Note-Technology.html](http://www.ursulakleguinarchive.com/Note-Technology.html). 95 [^leguinrefquote2]: Ursula K. Le Guin, "A Rant About 'Technology'," 2004, [http://www.ursulakleguinarchive.com/Note-Technology.html](http://www.ursulakleguinarchive.com/Note-Technology.html). 96 97 98 ### Limitations of the footnotes 99 100 This it not biblatex/biber. So as you can see in the examples above, you cannot 101 reuse an existing footnote, and there is not elegant handling of repetition (no 102 Ibid.). 103 104 105 Reference style 106 --------------- 107 108 When referencing, please use the [Notes and Bibliography version of The Chicago 109 Manual of 110 Style](https://www.chicagomanualofstyle.org/tools_citationguide/citation-guide-1.html). 111 However, this is not an academic paper, don't overthink it or spend ages on it, 112 try to make it work as best as you can, it's just to have some overall 113 consistency. No sweat :) 114 115 116 Acceptable content 117 ------------------ 118 119 Basically any topic is allowed as long as it can be discussed from a 120 permacomputing-relevant point of view and do not break the [[terms]]. 121 122 123 Licensing 124 --------- 125 126 While editing the Permacomputing wiki, you agree that your contribution will be 127 published and made available under the [CC0 128 Waiver](https://creativecommons.org/publicdomain/zero/1.0/legalcode-plain). If 129 you use images, photos, from other sources, please make sure to give full 130 credit and if available the license/tersm under which the image is made 131 available.