Thanks for the replies Wendy and Brad! I am going to have to take a good look at the Wiki and find some places I can improve, based on my usage and experience with Maven2. I want to ask other users to do the same, so we can improve the overall level of documentation in Maven. Here's the link: http://docs.codehaus.org/display/MAVENUSER/Home
> quality control. Its something all of us developers who desire > excellence in our products despise. Its just surprising that when we are > given free pasture to roam and do things our way, we repeat the exact > same error. Unfortunate but true. I am guilty of it myself more often than not. ;-) > Its simple: consider documentation part of a feature release. If it > ain't documented, it isn't released. If a major objective of open source > is the idea of information sharing, it seems that having poor > documentation confirms a particular degree of failure, no? Which is well and good for the "leadership" of a project to force down "from above" on all developers in the project. They can refuse to "accept" contributions and code until documentation is at a certain level of completeness. But its harder for users to "force up" these same "requirements" on the development team. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
