On Thu, 12 Dec 2002, Henning P. Schmiedehausen wrote:
> Rafal Krzewski <[EMAIL PROTECTED]> writes: > > >Henning P. Schmiedehausen wrote: > > >> Is "documentation" one of the 2-3 serious things left to do? > > >Documentation is nice but working code is better :-) My experience with > >OSS shows that docs lie on the far end of the priority list. The people > > And that's why there are bazillons of abandoned, half-finished or > simply not usable OSS projects. A full-hearted +1. Documentation is nice, working code is good, but community is better. Good documentation leads to community. Working code without a community is not good OSS. [from having sat on the sidelines on Maven for a year now] The early Maven documentation was simply amazing and along with Jason's fervent drive were the two things that turned Maven from an idea into the next generation project it is. The documentation slipped as it had to handle multiple versions at the same time and as the amount of time spent documenting was less than the amount of time spent coding new features. It reached a bad point where the online docs were just plain wrong, but has since improved so that they are correct, but new features seem to take time to fully appear, and concepts like Best-Use-Guides and multi-level tutorials are not there yet. Even as a 'user' who is sitting and waiting for documentation to appear for some features [if anyone wants to write a Reactor tutorial, I'd owe you a beer] I still think that Maven 1.0 does not need great documentation, but that the focus of work once Maven 1.0 is released should be on tutorials, documentation and books. My tuppence, Hen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
