diff --git a/code-of-conduct.md b/code-of-conduct.md index c634d6bd..253f88b1 100644 --- a/code-of-conduct.md +++ b/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. diff --git a/doc/EN/devguide.org b/doc/EN/devguide.org index 2528ba65..14c92479 100644 --- a/doc/EN/devguide.org +++ b/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. diff --git a/website/EN/devguide.html b/website/EN/devguide.html index 41dd21f6..c6077ad7 100644 --- a/website/EN/devguide.html +++ b/website/EN/devguide.html @@ -3,7 +3,7 @@ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - + @@ -246,17 +246,17 @@ for the JavaScript code in this tag.

Developers Guide

-
-

Introduction

-
+
+

Introduction

+

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.

-
-

Substitute for a Code of Conduct

-
+
+

Substitute for a Code of Conduct

+

Instead of having some tedious Code of Conduct which tries to micro-manage how folks communicate privately with each other this project has a set of guiding principles, which are as follows:

@@ -264,6 +264,7 @@ Instead of having some tedious Code of Conduct which tries to micro-manag
  • 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.
    • @@ -274,9 +275,9 @@ Instead of having some tedious Code of Conduct which tries to micro-manag
-
-

Adding extra apps

-
+
+

Adding extra apps

+

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.

@@ -554,9 +555,9 @@ Submit your working app to -

Customising mesh images

-
+
+

Customising mesh images

+

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 img/backgrounds and to change the available avatars and desktop icons edit the images within img/avatars. Re-create disk images using the instructions shown previously.