I took a deeper look at docs and here's what I noticed: 1. Documentation problem exists in almost all community projects for simple reason that there is no idea how to fix it <> in commercial projects it is clear and simple WHO does WHAT, WHEN and HOW. BW docs clearly shows it's community nature :)
2. It is not just an documentation problem. It's origin is in rapid development. If you change things all the time, WHY is coming up. 3. Insufficient documentation causes small community, which means that you don't have folk resource needed for documentation building... So, just making good documentation is simply not enough. You have to freeze the project at some stable point, make most (if not all) plugins running good enough and document it for both, devs and users. But primary for users (they don't read code :) There is one more thing: user manuals should be written by users, not devs. If developer writes it, one should downclock his brains to 3% and explain to him self how to do do what he is up to. Finally, I suggest to make rock stable 3.5; pass/check/update all the plugins, document it and fix as Lite version. During the time, it will grasp some users, get totally debugged, collect documentation... 4.0 is a different story - but it is easy way if you have good structured and correct documentation as a blueprint for the new one. Dan? Guys? -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
