CVS: lunar-doc TODO,1.2,1.3

[elaine at lunar-linux.org]

Update of /var/cvs/lunar/lunar-doc
In directory dbguin.lunar-linux.org:/home/elaine/lpcvs/lunar-doc

Modified Files:
	TODO 
Log Message:
auto-commit


Index: TODO
===================================================================
RCS file: /var/cvs/lunar/lunar-doc/TODO,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- TODO	19 Jul 2003 20:31:08 -0000	1.2
+++ TODO	20 Jul 2003 19:55:05 -0000	1.3
@@ -13,4 +13,16 @@
 depends, if wanted (secondary to lin's use). As pointed out on IRC, this could 
 be achieved by an extra field in DETAILS, for example, or in moonbase, to keep 
 things centralised.
-COMMENTS:  
+elaine/TODO:item: Start own TODO
+elaine/TODO:item: Core documents, functions, subroutines, module design
+elaine/TODO:item: kernel code hash generation tool
+elaine/TODO:item: Website re-design  
+elaine/TODO:item: Selinux module/policy & metadata tools/config
+elaine/TODO:item: NPTL module post-crash xxx
+elaine/TODO:item: coalesce individual TODO's into master && perhaps add to private web
+evildrew/TODO:item: 1. (Priority) Installation manual -- Handy guide to get people through the install and up and running.
+evildrew/TODO:item: 2. Handy stuff on the command line -- Unique commands to lunar and how to use them to your advantage.
+evildrew/TODO:item: 3. Core documentation -- The more serious version of #2.
+nestu/TODO:item: 1) Tarball size in moonbase/lunar
+sofar/TODO:item: add cpan:// urls and see if it can be made working with a default_cpan_build or something like that
+sofar/TODO:item: add a uniform verification scheme that allows us to use one scheme to verify the valitidy of sourcefiles, possible syntax would be a DETAILS entry (SOURCE_VFY[0]=MD5:1a9e1f6c2c4b5a1d2827312) (SOURCE_VFY[1]=GPG:url-to-asc-file)