--- a/devel-ideal-proj.rst	Fri Oct 21 13:12:57 2011 +0300
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,82 +0,0 @@
--*- mode: outline; coding: utf-8; -*-
-
-* Ideal software development model.
-
-This file mainly discuss about open source software project.
-
-* Open source.
-
-Open source software project have freedom how develop project and which
-development toolchains use.
-
-* Close source.
-
-Close source projects have proprietary nature because of:
-
- * interest to make money (another parties can not easily reproduce project or
-   steal realisation ideas/code, allowing another party get same product and get
-   company money)
- * low code quality (to stop stain company good name or to stop malicious
-   attacks based on code analysis)
- * security consideration (to hide protocols and data format to make harder
-   malicious attack)
- * business model (closed data formats allow vendor lock)
-
-Disadvantage of closed source project (in many case):
-
- * you can not directly contact with developers (only through support)
- * low support quality
- * paid support (and you have no enough money)
- * 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
-
-* Component of software project.
-
- * Src (sources).
- * Doc (documentation).
- * VCS (version control system).
- * BTS (bug tracking).
- * News (project news/history/changelog).
-
-* Docs.
-
-TODO
-
-* Project home page.
-
-Project home page must provide:
-
- * project name
- * short info about project goal
- * project license
- * current 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
-

--- a/devel-productivity.rst	Fri Oct 21 13:12:57 2011 +0300
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,10 +0,0 @@
--*- mode: outline; coding: utf-8; -*-
-
-* Productivity statistic.
-
-KLOC (kilo lines of code), MM (man month).
-
-41 KLOC / 119 MM  == 11 LOC/day  | 5 people | hard task, high/middle skills, new to domain
-6 KLOC / 24 MM    == 8.3 LOC/day | 6 people | hard task, high skills
-26 KLOC / 46 MM   == 19 LOC/day  | 7 people | easy task, middle skills
-155 KLOC / 20 MM  == 260 LOC/day | 7 people | middle task, high skills, high level programming