Преглед изворни кода

Principle of self-management

Bob Mottram пре 7 година
родитељ
комит
70199d2a07
3 измењених фајлова са 16 додато и 13 уклоњено
  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
2 2
 
3 3
  * Enable users to help themselves to provide their own personal software infrastructure.
4 4
  * Enable users to help each other to provide software infrastructure for a community.
5
+ * Principle of self-management: apps should require miniumum configuration and maintain themselves as far as possible.
5 6
  * There should be no single point of failure. Assume that other servers can and will fail occasionally.
6 7
  * 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.
7 8
  * 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
21 21
 
22 22
  * Enable users to help themselves to provide their own personal software infrastructure.
23 23
  * Enable users to help each other to provide software infrastructure for a community.
24
+ * Principle of self-management: apps should require miniumum configuration and maintain themselves as far as possible.
24 25
  * There should be no single point of failure. Assume that other servers can and will fail occasionally.
25 26
  * 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.
26 27
  * 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 @@
3 3
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 4
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 5
 <head>
6
-<!-- 2017-07-18 Tue 10:41 -->
6
+<!-- 2017-07-18 Tue 11:19 -->
7 7
 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8 8
 <meta name="viewport" content="width=device-width, initial-scale=1" />
9 9
 <title></title>
@@ -246,17 +246,17 @@ for the JavaScript code in this tag.
246 246
 
247 247
 <center><h1>Developers Guide</h1></center>
248 248
 
249
-<div id="outline-container-org320decc" class="outline-2">
250
-<h2 id="org320decc">Introduction</h2>
251
-<div class="outline-text-2" id="text-org320decc">
249
+<div id="outline-container-orgeb19df0" class="outline-2">
250
+<h2 id="orgeb19df0">Introduction</h2>
251
+<div class="outline-text-2" id="text-orgeb19df0">
252 252
 <p>
253 253
 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.
254 254
 </p>
255 255
 </div>
256 256
 </div>
257
-<div id="outline-container-orgaee9f2d" class="outline-2">
258
-<h2 id="orgaee9f2d">Substitute for a Code of Conduct</h2>
259
-<div class="outline-text-2" id="text-orgaee9f2d">
257
+<div id="outline-container-org70ef738" class="outline-2">
258
+<h2 id="org70ef738">Substitute for a Code of Conduct</h2>
259
+<div class="outline-text-2" id="text-org70ef738">
260 260
 <p>
261 261
 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:
262 262
 </p>
@@ -264,6 +264,7 @@ Instead of having some tedious <i>Code of Conduct</i> which tries to micro-manag
264 264
 <ul class="org-ul">
265 265
 <li>Enable users to help themselves to provide their own personal software infrastructure.</li>
266 266
 <li>Enable users to help each other to provide software infrastructure for a community.</li>
267
+<li>Principle of self-management: apps should require miniumum configuration and maintain themselves as far as possible.</li>
267 268
 <li>There should be no single point of failure. Assume that other servers can and will fail occasionally.</li>
268 269
 <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>
269 270
 <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 <i>Code of Conduct</i> which tries to micro-manag
274 275
 </div>
275 276
 </div>
276 277
 
277
-<div id="outline-container-org350cefa" class="outline-2">
278
-<h2 id="org350cefa">Adding extra apps</h2>
279
-<div class="outline-text-2" id="text-org350cefa">
278
+<div id="outline-container-orgce166ed" class="outline-2">
279
+<h2 id="orgce166ed">Adding extra apps</h2>
280
+<div class="outline-text-2" id="text-orgce166ed">
280 281
 <p>
281 282
 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.
282 283
 </p>
@@ -554,9 +555,9 @@ Submit your working app to <b><a href="https://github.com/bashrc/freedombone/iss
554 555
 </div>
555 556
 </div>
556 557
 
557
-<div id="outline-container-orgc1d1e00" class="outline-2">
558
-<h2 id="orgc1d1e00">Customising mesh images</h2>
559
-<div class="outline-text-2" id="text-orgc1d1e00">
558
+<div id="outline-container-org2e7b384" class="outline-2">
559
+<h2 id="org2e7b384">Customising mesh images</h2>
560
+<div class="outline-text-2" id="text-org2e7b384">
560 561
 <p>
561 562
 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.
562 563
 </p>