Every single project, open source or not, needs to have a "Why Use It" page. (Now this is more of a "Testimonials" page, but for server tech it will do.) > Apache is like Microsoft Word, it has a million options but you only need six. Nginx does those six things, and it does five of them 50 times faster than Apache. This is exactly how I felt. I'm a pea-brained dolt in the server sphere, and when I was remaking my se…
Let me expand your comment (with your permission) to make it more general.
"Every project, open source or not, needs to be run with all the branches of a proper organization"
Let me flesh it out with an example: some time ago there was a flame here and on proggit about cricitisism of C++. Some arguments and counter-arguments (http://www.reddit.com/r/programming/comments/197dn1/introduc...) got me thinking (have mercy, o' HN C++ overlords)
1. Problems are due to power and flexibility Design : build simple and tight systems or get smart enough to build tight complex systems.
2. clang is fixing template error messages Execution: reasonable to demand this be done before standardization
3. This is an implementation problem Management apathy: Passing the buck
4. C++ is not one language but actually many different ones Marketing : Positioning
etc
There should be no reason why open-source projects should be 'good code, bad with everything else'.