doc: open-collective, move docs work to "long term vision".

Author: schettino72

doc/dictionary.txt

@@ -60,6 +60,7 @@
 0'
 2to3
 3d
+4s
 API
 ATCI
 BC3
@@ -139,6 +140,7 @@ TaskFailed
 TaskLoader
 Tpng
 Trento
+USD
 UptodateCalculator
 Uz
 VCS
@@ -292,6 +294,7 @@ pathlib
 pdb
 perl
 picklable
+pixelmap
 plugin
 plugins
 png
@@ -301,6 +304,7 @@ pos1
 pre
 prev
 printf
+procida
 programmatically
 pstats
 py
@@ -317,12 +321,15 @@ pytest
 python2
 python3
 quickstart
+refactor
 regex
 repr
 rst2s5
 runtests
 s'
 s5defs
+schettino
+schettino72
 schettino72
 scons
 selecttasks
@@ -335,6 +342,7 @@ sourcecode
 sourceforge
 sqlite3
 startswith
+stateful
 stderr
 stdlib
 stdout
@@ -344,6 +352,7 @@ sudo
 t1
 t2
 t3
+t4vKPhjcMZg
 tabcompletion
 task1
 task2
@@ -355,6 +364,7 @@ time'
 timedelta
 timestamp
 titlewithactions
+to's
 toc
 toctree
 tsetup
@@ -378,4 +388,3 @@ x'
 xxx
 xyz
 zsh
-pixelmap

doc/open_collective.md

@@ -4,23 +4,22 @@ the tool for **stateful processing of your interdependent tasks** powered by:
 - **python** batteries
 - **doit** processing engine
 
-doit is mature project started in 2008 by @shettino72 and maintained by him up to date. It already serves years in numerous projects to:
+doit is mature project started in 2008 by @schettino72 and maintained by him up to date. It already serves years in numerous projects to:
 
 - simplify cumbersome command line calls,
 - automate complex data processing or typical project related actions,
 - share unified way of doing things,
 - optimize processing time by skipping things already done.
-  
+
 People often compare `doit` to tools like `make`, `grunt` or `gulp` but they always appreciate
 
 - strong features and flexibility
 - simplicity of authoring and ease of use
 - python
-  
+
 # Current focus
-There are two current priorities:
-  
-## A: Maintain existing codebase
+
+## Maintain existing code-base
 The aim is to **keep the product in shape and usable**.
 
 Abandoned open-source project does not work for long. Thriving project requires a maintainer to keep list of issues and list of pull requests short.
@@ -29,24 +28,21 @@ Financial goal is 500 USD per month to allow the maintainer working few hours a
 
 Main capacity shall be provided by @schettino72
 
-## B: Refactor documentation
+
+# Long term vision
+
+## B: Rewrite documentation
 The aim is to **lower initial learning barrier for newcomers to get them on board** and to **help pro-users to unlock more features and earn fame**.
 
 Existing documentation is good as it served well existing users. But we can serve better.
-Inspired by great talk [What nobody tells you about documentation](https://www.youtube.com/watch?v=t4vKPhjcMZg&t=4s) by Daniele Procida we plan to refactor the documentation into following parts:
+Inspired by great talk [What nobody tells you about documentation](https://www.youtube.com/watch?v=t4vKPhjcMZg&t=4s) by Daniele Procida we plan to rewrite the documentation into following parts:
 
 - Introduction (basic features overview)
 - Quick start and tutorials
 - Reference documentation
 - Concepts
-- Howtos
-  
-Financial goal is another 500 USD per month to allow documentation writer working few hours a week on documentation refactoring and maintenance.
-
-Main capacity shall be provided by @vlcinsky.
+- How-to's
 
-# Long term vision
-Assuming the A and B priorities are fulfilled, we shall look further on into future.
 
 ## C: Promote
 We believe, many more users deserve `doit` and we shall help them to know about it.
@@ -56,16 +52,14 @@ Promotion may have form of:
 - helping selected python projects to adopt doit as internal tool
 - video presentations
 - presentation(s) at pycon(s)
-  
-This is long term priority and there is no budget set for it at the moment.
+
 
 ## D: Launch doit task libraries
 
 Grunt library has over 6000 tasks, gulp has over 3000 plug-ins.
 
 `doit` has similar potential. E.g. [doit-py](https://github.com/pydoit/doit-py) covers python code specific tasks. Few lines of code in [dodo.py](https://github.com/pydoit/doit-py/blob/master/dodo.py) to lint the code; run the tests and measure coverage; build and upload package; spell, build and publish sphinx based documentation.
 
-This is long term priority and there is no budget set for it at the moment.
 
 # Why to contribute?