--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/devel-ideal-proj.rst	Sun Nov 07 19:59:26 2010 +0200
@@ -0,0 +1,81 @@
+-*- mode: outline; coding: utf-8 -*-
+
+                      Ideal software development model.
+
+
+* Open source.
+
+Open source development have much freedom select any development model.
+
+
+* Close source.
+
+Close source sortware development restrict in using models, technic or
+software resources; restrict their public appear because of its proprietary
+nature.
+
+In many case you can not directly contact with developers (only through
+support). You can not access to product bug tracing system (you only can
+submit bug via crash report application or technical support); publicly appear
+internal bug tracing can damage product reputation. Internal
+architecture/protocol description can drop leading product position (allowing
+another party get same product and get company money).
+
+* Component.
+
+ * Docs.
+ * VCS.
+ * Bug track.
+ * News.
+
+** Docs.
+
+Documentation must provide:
+
+** Home page.
+
+Home page must provide:
+
+ * project name
+ * short info about project goal
+ * project licence (COPYING)
+ * currect project status
+ * links to binary release
+ * links to source release, how to get latest source from VCS
+ * links to online/printed docs
+ * how report bug (BUGS)
+ * where send patch
+ * contact info
+
+Additionally:
+
+ * help welcome, requirement to join to project
+ * mail/news list for users/developers, how to subscribe/unsubscribe, where
+   find archive, how search for keyword in archive
+ * project history (NEWS, ChangeLog)
+ * project policy (HACKING)
+ * how build project (README, INSTALL)
+ * list of contributor with contact info (MAINTAINERS, AUTHORS)
+ * who use project
+
+** VCS.
+
+TAGS: VCS, version control system, SCM, source code management, DVCS,
+      distributed version control system.
+
+ * CVS
+ * SVN
+ * Mercurial (hg)
+ * git
+ * bazaar
+
+*** CVS
+
+*** SVN
+
+*** Mercurial (hg)
+
+*** git
+
+*** bazaar
+

--- a/ideal-devel-proj.rst	Sun Nov 07 19:58:27 2010 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,81 +0,0 @@
--*- mode: outline; coding: utf-8 -*-
-
-                      Ideal software development model.
-
-
-* Open source.
-
-Open source development have much freedom select any development model.
-
-
-* Close source.
-
-Close source sortware development restrict in using models, technic or
-software resources; restrict their public appear because of its proprietary
-nature.
-
-In many case you can not directly contact with developers (only through
-support). You can not access to product bug tracing system (you only can
-submit bug via crash report application or technical support); publicly appear
-internal bug tracing can damage product reputation. Internal
-architecture/protocol description can drop leading product position (allowing
-another party get same product and get company money).
-
-* Component.
-
- * Docs.
- * VCS.
- * Bug track.
- * News.
-
-** Docs.
-
-Documentation must provide:
-
-** Home page.
-
-Home page must provide:
-
- * project name
- * short info about project goal
- * project licence (COPYING)
- * currect project status
- * links to binary release
- * links to source release, how to get latest source from VCS
- * links to online/printed docs
- * how report bug (BUGS)
- * where send patch
- * contact info
-
-Additionally:
-
- * help welcome, requirement to join to project
- * mail/news list for users/developers, how to subscribe/unsubscribe, where
-   find archive, how search for keyword in archive
- * project history (NEWS, ChangeLog)
- * project policy (HACKING)
- * how build project (README, INSTALL)
- * list of contributor with contact info (MAINTAINERS, AUTHORS)
- * who use project
-
-** VCS.
-
-TAGS: VCS, version control system, SCM, source code management, DVCS,
-      distributed version control system.
-
- * CVS
- * SVN
- * Mercurial (hg)
- * git
- * bazaar
-
-*** CVS
-
-*** SVN
-
-*** Mercurial (hg)
-
-*** git
-
-*** bazaar
-