> > Pardon me for saying, but it sort of seems like you're missing the > > point. Not everyone has the expertise, time, or basic "starter" > > knowledge to know how to do what you describe. This is the real value > > of docs. > I agree. However, even those that don't have that knowledge can contribute > by detailing the sort of docs they would like to see, and helping to build > them.
<snip/> > > Ant's early docs were hard to read and incomplete. As someone who > contributed a 'frame'd set of Ant docs back in the very early days, let me > tell you it was damn hard to work things out. > <snip/> > Please help us by helping flesh out the sorts of docs we will need. > > If anyone does want to contribute, they can look at all the plugins that > are missing docs. Around half of them have no goals or properties docs. > > I'm happy to help anyone who wants to give it a go. > I absolutely agree with your stance, and understand the situation you guys are in. This software hasn't yet released 1.0, and so still has stabilization to go through. As someone who is currently going through the pain of creating documentation for a 25,000 line project which here-to-fore had none, I know what kind of pain you're talking about. Actually, this project is the source of my gripes about lack of startup documentation for maven. As I dig through maven, and get my project configured, I will keep the line open for feedback on what documents are needed to make the process easier for others. I'll also contribute documentation if I can, detailing my approach to codebase management and how maven fits in, although I'm not sure it will be the best approach. However, the last thing I would like to see is a project with this kind of potential driven into the ground by developers who don't see the value of a usable project and a solid community of developers and users. I'm glad to hear your stabilizing remarks, though. Regards, John -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
