doc: Remove scripts.mdwn

Its information is merged into the online Developer Manual which will be
imported here.

LICENSES

@@ -19,7 +19,6 @@ otherwise.
 - doc/header.html :: -
 - doc/Makefile :: -
 - doc/modules.mdwn :: -
-- doc/scripts.mdwn :: -
 - doc/themes.mdwn :: -
 - static/themes/default/FreedomBox-Identity-Manual.pdf :: -
 - static/themes/default/FreedomBox-Logo.7z :: [[http://thread.gmane.org/gmane.linux.debian.freedombox.user/4124/focus=4439][GPL3+/CC-BY-SA]]

doc/Makefile

@@ -6,7 +6,7 @@ PDFLATEX=pdflatex
 
 # List text files in the order in which you want them to appear in the
 # complete manual:
-SOURCES=README.mdwn INSTALL.mdwn themes.mdwn hacking.mdwn modules.mdwn scripts.mdwn COPYING.mdwn
+SOURCES=README.mdwn INSTALL.mdwn themes.mdwn hacking.mdwn modules.mdwn COPYING.mdwn
 MAN_SOURCES=$(patsubst COPYING.mdwn,copyright_notice00,$(SOURCES))
 
 NEWLINE_SOURCES=$(patsubst %,% oneline.txt,$(SOURCES))

doc/scripts.mdwn

@@ -1,24 +0,0 @@
-# Scripts
-
-The Plinth front end should not directly change any aspect of the
-underlying operating system.  Instead, it should call upon scripts,
-either by shell command or (for python modules) via import.
-
-Scripts live in `/scripts`.  They should have the following
-characteristics:
-
-* Do only one thing
-
-* Require no interaction beyond passing parameters or commandline
-  arguments
-
-* Change the operation of the services and applications of the Freedom
-  Plug and nothing else.
-
-* If a script is a python file, it should be *both* usable from the
-  commandline and importable as a python module.
-
-The scripts should be of general utility.  They should be usable to
-admin and configure the system even in the absence of Plinth.  These
-scripts are the only supported method of making changes to a Freedom
-Plug, whtether by SSH or via Plinth.