What does the community think about a community run, community organized, sub project for USER documentation? This type of documentation would be things like, "10 steps to configure replication", "Dumb simple Postgres backups", "5 things to NEVER do with Postgres". I imagine we would sort it by version (9.6/10.0 etc...) as well as break it down via type (Administration, Tuning, Gotchas) etc...
What do we think?
Politely tell them to buy some of the many well written books that are available on these very topics...
Politely tell them to buy a license to MSSQl...
Kind of misses the whole point doesn't it?
I'm going for practicality over idealism here. That some of the best written material for learning how to be an application developer or DBA is presently really only available in the forms of books is a fact of our existence. I frankly don't have a problem that there isn't a "free beer" resource available to complete with it.
I'm all for continual improvement but color me doubtful that there is enough desire and discipline here to invent and then maintain a high-maintenance system. So, yes, I am intentionally trying to avoid the trap that is problem that you want to solve by suggesting forgetting the revolution and instead coming at the problem from an entirely different angle and working to evolve the equilibrium that presently exists.