cleanup todos (and shrink them)

Signed-off-by: Nico Schottelius <nico@kr.ethz.ch>

ROADMAP

@@ -1,20 +0,0 @@
-This document defines how to continue work on cdist:
-
-x Define how to get information from clients
-   x Create shell script that creates code to run on client (cdist-build-explorer)
-x Create configuration tree from manifest
-   x write binaries, which create the tree when called from manifest (cdist_tree_wrapper)
-x Define configuration paths (doc/internal/config-layout)
-x Redo explorers (see manpage)
-/ Write at least one type
-
-- Parse configuration tree/objects recursively
-   - can/may types modify tree?
-      - may open door for getting information from manifest / other stuff
-- generate code to be executed on client
-   - check return codes
-   - abort on first error?
-
-- Cleanup directories, cleanly document, what's possible
-
--> 1.0

TODO

@@ -1,54 +0,0 @@
-- doc:
-   - cdist manpage (main manpage)
-      - cleanup following man + their tree:
-         - cdist-language        [IMPORTANT]
-         - cdist-design.text     [IMPORTANT]
-         - cdist-push-pull
-         - cdist-quickstart
-         - cdist-types           [IMPORTANT]
-         - cdist.text            [IMPORTANT]
-      - add terminology
-      - define steps within configuration apply
-         - detect impossible/unsafe things:
-         - creating a file twice
-         - installing and removing a package
-         - and report location of occurence
-         - parse afterwards?
-      - multi master setups
-      - templating
-         - how to define templates
-            - variable substitution from shell may be problematic
-         - SHELL SCRIPTS! (executables? do not support?)
-            - stdout == output of template == what will be used
-- cdist-explore
-   - add more stuff to explore
-   - write manpage
-   - save in cache as well
-- Create usable Makefile 
-   - install
-- types needed:
-   - package management
-   - file / directory handling
-   - ssh-host-key: that uses cache / explored data from hosts!
-   - services
-   - user management
-      - including passwords
-   - file editing
-      - add_line_to_file_if_not_existing
-      - delete_line_from_file
-      - regexp replace (can probably cover all?)
-- release first public version, which includes at least:
-   - manpages
-   - only do necessary work [TYPE IMPLEMENTATION HINTS]
-      - install packages only if not existent
-      - copy file only if different
-
-Before initial release, document:
-      
-   - how to add package backends
-   - how to write a minimal host manifest
-   - create library with all functions (and their parameters)
-      - cdist_package
-      - cdist_file
-      - cdist_dir
-

TODO-1.0

@@ -0,0 +1,52 @@
+This document defines how to continue work on cdist:
+
+x Define how to get information from clients
+   x Create shell script that creates code to run on client (cdist-build-explorer)
+x Create configuration tree from manifest
+   x write binaries, which create the tree when called from manifest (cdist_tree_wrapper)
+x Define configuration paths (doc/internal/config-layout)
+x Redo explorers (see manpage)
+/ Write at least one type
+
+- Parse configuration tree/objects recursively
+   - can/may types modify tree?
+      - may open door for getting information from manifest / other stuff
+- generate code to be executed on client
+   - check return codes
+   - abort on first error?
+
+- doc 1.0:
+   - cdist manpage (main manpage)
+      - cleanup following man + their tree:
+         - cdist-language        [IMPORTANT]
+         - cdist-design.text     [IMPORTANT]
+         - cdist-push-pull
+         - cdist-quickstart
+            - how to write a minimal host manifest
+         - cdist-types           [IMPORTANT]
+            - only do necessary work [TYPE IMPLEMENTATION HINTS]
+               - install packages only if not existent
+               - copy file only if different
+         - cdist                 [IMPORTANT]
+         - cdist-explorers
+      - add terminology
+      - define steps within configuration apply
+         - detect impossible/unsafe things:
+         - creating a file twice
+         - installing and removing a package
+         - and report location of occurence
+         - parse afterwards?
+      - multi master setups
+      - templating
+         - how to define templates
+            - variable substitution from shell may be problematic
+         - SHELL SCRIPTS! (executables? do not support?)
+            - stdout == output of template == what will be used
+- Add install target to Makefile
+
+- types needed
+   - file (with directory)
+   - package
+
+- Cleanup directories, cleanly document, what's possible
+

doc/dev/todo/post-1.0

@@ -0,0 +1,9 @@
+Types:
+   - ssh-keys (host/user)
+   - services
+   - user management
+   - file editing 
+      - add_line_to_file_if_not_existing
+      - delete_line_from_file
+      - regexp replace (can probably cover all?)
+