tsr/dox
1
0
Fork 0
Code Releases Activity

wording

Browse Source
This commit is contained in:
notnull 2019-01-12 19:33:16 -05:00 committed by traumschule
parent 4df8600be7
commit 399350a82b
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
index.html
View File

@ -4,7 +4,7 @@
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>index</title>
<!-- 2019-01-12 Sat 15:31 -->
<!-- 2019-01-12 Sat 19:32 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="generator" content="Org-mode" />
<meta name="author" content="anarchyplanet" />
@ -187,11 +187,11 @@ Feel free to generate your own tutorial topics, with the constraint that the tut
</ol>
<p>
This project has an implicit tagline: "Can we even get one tutorial off the ground?" We've all felt the frustration of starting a project full of enthusiasm and motivation to accomplish huge goals, only for the initial excitement to wane as people get busy and drift on to other tasks. So this project is about starting small. Can we even complete one tutorial together? Can we break our grand plans into tiny projects that we can execute without requiring massive amounts of time and energy? And if we can't, how can we hope to accomplish larger and messier goals without repeating the cycle of early enthusiasm and eventual burnout?
This project has an implicit tagline: "Can we even get one tutorial off the ground?" We've all felt the frustration of starting a project full of enthusiasm and motivation to accomplish huge goals, only for the initial excitement to wane as people get busy and drift on to other tasks. So this project is about starting small. Can we even complete one tutorial together? Can we break our grand plans into tiny projects that we can execute without requiring massive amounts of people capable of devoting massive amounts of time and energy? And if we can't, how can we hope to accomplish larger and messier goals without repeating the cycle of early enthusiasm and eventual burnout?
</p>
<p>
Another motivation is to develop a process of creating documentation through 'user testing'&#x2013; that is, understanding what someone needs to know in order to accomplish a task, and then providing that information and that information only. I find this more helpful than providing someone the entire history of the internet and expecting them to develop a deep understanding of every related concept and skill every time they try to read a tutorial. Ultimately I hope this will result in building a shareable corpus of knowledge that is (1) plaintext (2) shareable and (3) useful to others, but even if this task fails we will at least have the pieces we create which should be already useful in themselves.
Another motivation is to develop a process of creating documentation through 'user testing'&#x2013; that is, understanding what someone needs to know in order to accomplish a task, and then providing that information and that information only. I find this more helpful than providing someone the entire history of the internet and expecting them to develop a deep understanding of every related concept and skill every time they try to read a tutorial. Ultimately I hope this will result in building a shareable corpus of knowledge, but even if this task fails we will at least have the pieces we create which should be already useful in themselves.
</p>
<p>
@ -451,7 +451,7 @@ as user: cd globalist ; torsocks pip3 install .
</div>
<div id="postamble" class="status">
<p class="author">Author: anarchyplanet</p>
<p class="date">Created: 2019-01-12 Sat 15:31</p>
<p class="date">Created: 2019-01-12 Sat 19:32</p>
<p class="creator"><a href="http://www.gnu.org/software/emacs/">Emacs</a> 24.5.1 (<a href="http://orgmode.org">Org</a> mode 8.2.10)</p>
<p class="validation"><a href="http://validator.w3.org/check?uri=referer">Validate</a></p>
</div>

4
index.org
View File

@ -18,9 +18,9 @@ Feel free to generate your own tutorial topics, with the constraint that the tut
2. tangible. we should have something by the end that we didn't have before, such as an email address with gpg enabled.
3. FOSS all day erry day
This project has an implicit tagline: "Can we even get one tutorial off the ground?" We've all felt the frustration of starting a project full of enthusiasm and motivation to accomplish huge goals, only for the initial excitement to wane as people get busy and drift on to other tasks. So this project is about starting small. Can we even complete one tutorial together? Can we break our grand plans into tiny projects that we can execute without requiring massive amounts of time and energy? And if we can't, how can we hope to accomplish larger and messier goals without repeating the cycle of early enthusiasm and eventual burnout?
This project has an implicit tagline: "Can we even get one tutorial off the ground?" We've all felt the frustration of starting a project full of enthusiasm and motivation to accomplish huge goals, only for the initial excitement to wane as people get busy and drift on to other tasks. So this project is about starting small. Can we even complete one tutorial together? Can we break our grand plans into tiny projects that we can execute without requiring massive amounts of people capable of devoting massive amounts of time and energy? And if we can't, how can we hope to accomplish larger and messier goals without repeating the cycle of early enthusiasm and eventual burnout?
Another motivation is to develop a process of creating documentation through 'user testing'-- that is, understanding what someone needs to know in order to accomplish a task, and then providing that information and that information only. I find this more helpful than providing someone the entire history of the internet and expecting them to develop a deep understanding of every related concept and skill every time they try to read a tutorial. Ultimately I hope this will result in building a shareable corpus of knowledge that is (1) plaintext (2) shareable and (3) useful to others, but even if this task fails we will at least have the pieces we create which should be already useful in themselves.
Another motivation is to develop a process of creating documentation through 'user testing'-- that is, understanding what someone needs to know in order to accomplish a task, and then providing that information and that information only. I find this more helpful than providing someone the entire history of the internet and expecting them to develop a deep understanding of every related concept and skill every time they try to read a tutorial. Ultimately I hope this will result in building a shareable corpus of knowledge, but even if this task fails we will at least have the pieces we create which should be already useful in themselves.
Finally, this project is about building rapport with our collaborators as we go through this process together. At the very least we will end up with onboarding documentation that can help new people who come into the process late, or who decide to go through their own process. And at best we will also have data about whether or not a group of loosely-affiliated strangers on the internet can collaborate together to work toward their goals, leveraging existing infrastructure that exists by keeping track of their process and developing strategies for sharing that process. Can we?