move README.Documentation to attic

It is outdated since many years now and we have the relevant info in the Development.lyx file

diff --git a/lib/doc/Makefile.am b/lib/doc/Makefile.am
index e18228cc788d15458a5c812b2aa2c49f897cd96b..5a5e36c90f40f4bb1fa5d5fc8c03991704c5e40e 100644 (file)
--- a/lib/doc/Makefile.am
+++ b/lib/doc/Makefile.am
@@ -1,7 +1,5 @@
 include $(top_srcdir)/config/common.am
 
-EXTRA_DIST = README.Documentation
-
 docdir = $(pkgdatadir)/doc
 dist_doc_DATA = \
        Additional.lyx \

diff --git a/lib/doc/README.Documentation b/lib/doc/README.Documentation
deleted file mode 100644 (file)
index 18982ee..0000000
--- a/lib/doc/README.Documentation
+++ /dev/null
@@ -1,44 +0,0 @@
-README.Documentation
-
-by John Weiss [3/2000] jpweiss@idsi.net
-
-
-================
-Introduction
-
-    The purpose of this file is *used* *to* *be* to provide a style
-    sheet and helpful hints to those wishing to help with the
-    LyX Documentation Project.  There's now a separate style-sheet for
-    that.
-
-    If you're actually looking for documentation, check out the "Help"
-    menu.  Start by reading the Introduction.
-
-================
-Why a separate documentation project?  Can't the developers do it?
-
-    In a word, no.  They're too busy adding features and squishing
-    bugs.
-
-    Also, g++ is far more forgiving of style changes than a human
-    brain.  As long as the code is correct, g++ will happilly compile
-    it, and compile it the same way from machine to machine.  Human
-    brains are far less forgiving and far more individualized.  So,
-    the documentation needs to all be in a uniform style, in addition
-    to being grammatically correct and easily readable.  That's a
-    pretty big undertaking - which is why I volunteered to
-    administrate the docs back in 1997.  Since then, I've passed the
-    duty of maintaining the docs on to others.
-
-================
-Helping Out
-
-    If you'd like to contribute to the LyX Documentation Project,
-    start by reading the file Intro.lyx.  It contains a description of
-    the style of the documentation from a reader's perspective.  After
-    that, read the LyX Documentation Style Sheet (DocStyle.lyx) and
-    commit it to memory!
-
-
-John Weiss
-March, 2000

diff --git a/lib/doc/attic/README.Documentation b/lib/doc/attic/README.Documentation
new file mode 100644 (file)
index 0000000..18982ee
--- /dev/null
+++ b/lib/doc/attic/README.Documentation
@@ -0,0 +1,44 @@
+README.Documentation
+
+by John Weiss [3/2000] jpweiss@idsi.net
+
+
+================
+Introduction
+
+    The purpose of this file is *used* *to* *be* to provide a style
+    sheet and helpful hints to those wishing to help with the
+    LyX Documentation Project.  There's now a separate style-sheet for
+    that.
+
+    If you're actually looking for documentation, check out the "Help"
+    menu.  Start by reading the Introduction.
+
+================
+Why a separate documentation project?  Can't the developers do it?
+
+    In a word, no.  They're too busy adding features and squishing
+    bugs.
+
+    Also, g++ is far more forgiving of style changes than a human
+    brain.  As long as the code is correct, g++ will happilly compile
+    it, and compile it the same way from machine to machine.  Human
+    brains are far less forgiving and far more individualized.  So,
+    the documentation needs to all be in a uniform style, in addition
+    to being grammatically correct and easily readable.  That's a
+    pretty big undertaking - which is why I volunteered to
+    administrate the docs back in 1997.  Since then, I've passed the
+    duty of maintaining the docs on to others.
+
+================
+Helping Out
+
+    If you'd like to contribute to the LyX Documentation Project,
+    start by reading the file Intro.lyx.  It contains a description of
+    the style of the documentation from a reader's perspective.  After
+    that, read the LyX Documentation Style Sheet (DocStyle.lyx) and
+    commit it to memory!
+
+
+John Weiss
+March, 2000