Browse Source

Principle of self-management

master
Bob Mottram 3 years ago
parent
commit
70199d2a07
3 changed files with 16 additions and 13 deletions
  1. + 1
    - 0
      code-of-conduct.md
  2. + 1
    - 0
      doc/EN/devguide.org
  3. + 14
    - 13
      website/EN/devguide.html

+ 1
- 0
code-of-conduct.md

@ -2,6 +2,7 @@ Instead of having some tedious *Code of Conduct* which tries to micro-manage how
* Enable users to help themselves to provide their own personal software infrastructure.
* Enable users to help each other to provide software infrastructure for a community.
* Principle of self-management: apps should require miniumum configuration and maintain themselves as far as possible.
* There should be no single point of failure. Assume that other servers can and will fail occasionally.
* Minimum data retention. Only store the data which users actually want or need, and within apps implement the function which allows logging to be turned off.
* Respect other users right to run their own stuff and have their own policies on their own hardware.

+ 1
- 0
doc/EN/devguide.org

@ -21,6 +21,7 @@ Instead of having some tedious /Code of Conduct/ which tries to micro-manage how
* Enable users to help themselves to provide their own personal software infrastructure.
* Enable users to help each other to provide software infrastructure for a community.
* Principle of self-management: apps should require miniumum configuration and maintain themselves as far as possible.
* There should be no single point of failure. Assume that other servers can and will fail occasionally.
* Minimum data retention. Only store the data which users actually want or need, and within apps implement the function which allows logging to be turned off.
* Respect other users right to run their own stuff and have their own policies on their own hardware.

+ 14
- 13
website/EN/devguide.html

@ -3,7 +3,7 @@
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!-- 2017-07-18 Tue 10:41 -->
<!-- 2017-07-18 Tue 11:19 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title></title>
@ -246,17 +246,17 @@ for the JavaScript code in this tag.
<center><h1>Developers Guide</h1></center>
<div id="outline-container-org320decc" class="outline-2">
<h2 id="org320decc">Introduction</h2>
<div class="outline-text-2" id="text-org320decc">
<div id="outline-container-orgeb19df0" class="outline-2">
<h2 id="orgeb19df0">Introduction</h2>
<div class="outline-text-2" id="text-orgeb19df0">
<p>
Freedombone consists of a set of bash scripts. There are a lot of them, but they're not very complicated. If you're familiar with the GNU/Linux commandline and can hack a bash script then you can probably add a new app or fix a bug in the system. There are no trendy development frameworks to learn or to get in your way.
</p>
</div>
</div>
<div id="outline-container-orgaee9f2d" class="outline-2">
<h2 id="orgaee9f2d">Substitute for a Code of Conduct</h2>
<div class="outline-text-2" id="text-orgaee9f2d">
<div id="outline-container-org70ef738" class="outline-2">
<h2 id="org70ef738">Substitute for a Code of Conduct</h2>
<div class="outline-text-2" id="text-org70ef738">
<p>
Instead of having some tedious <i>Code of Conduct</i> which tries to micro-manage how folks communicate privately with each other this project has a set of guiding principles, which are as follows:
</p>
@ -264,6 +264,7 @@ Instead of having some tedious Code of Conduct which tries to micro-manag
<ul class="org-ul">
<li>Enable users to help themselves to provide their own personal software infrastructure.</li>
<li>Enable users to help each other to provide software infrastructure for a community.</li>
<li>Principle of self-management: apps should require miniumum configuration and maintain themselves as far as possible.</li>
<li>There should be no single point of failure. Assume that other servers can and will fail occasionally.</li>
<li>Minimum data retention. Only store the data which users actually want or need, and within apps implement the function which allows logging to be turned off.</li>
<li>Respect other users right to run their own stuff and have their own policies on their own hardware.</li>
@ -274,9 +275,9 @@ Instead of having some tedious Code of Conduct which tries to micro-manag
</div>
</div>
<div id="outline-container-org350cefa" class="outline-2">
<h2 id="org350cefa">Adding extra apps</h2>
<div class="outline-text-2" id="text-org350cefa">
<div id="outline-container-orgce166ed" class="outline-2">
<h2 id="orgce166ed">Adding extra apps</h2>
<div class="outline-text-2" id="text-orgce166ed">
<p>
Suppose you have some internet application which you want to add to the system. To do this you need to create an app script which tells the system how to install/remove and also backup/restore. The script should be designed to work with the current stable version of Debian.
</p>
@ -554,9 +555,9 @@ Submit your working app to </div>
</div>
<div id="outline-container-orgc1d1e00" class="outline-2">
<h2 id="orgc1d1e00">Customising mesh images</h2>
<div class="outline-text-2" id="text-orgc1d1e00">
<div id="outline-container-org2e7b384" class="outline-2">
<h2 id="org2e7b384">Customising mesh images</h2>
<div class="outline-text-2" id="text-org2e7b384">
<p>
If you want to make your own specially branded version of the mesh images, such as for a particular event, then to change the default desktop backgrounds edit the images within <b>img/backgrounds</b> and to change the available avatars and desktop icons edit the images within <b>img/avatars</b>. Re-create disk images using the instructions shown previously.
</p>

Loading…
Cancel
Save