Isn't this sort of a catch-22? People are saying "I don't get maven, it's too complex."
Now it's time for them to give something back and document it? How do you propose they do that? Start at the source and pore through it to explain it? Saying that is sort of a cop-out, IMO. I think that the problem is that we have "maven in 5 minutes" and then the rest of the docs assume that people are experts with it - the 2 books mentioned earlier are useful, but I think people want something more approachable and contextual. One other thing is the navigation - I find it very difficult to get around the maven site in any meaningful way. There are many inter-dependent concepts and components, and each area's documentation assumes that the reader understands the other areas. For a beginner, that is rarely if ever the case. I'm not trying to add the rants, just provide some constructive criticism. Larry On 9/24/07, Michael McCallum <[EMAIL PROTECTED]> wrote: > On Tuesday 25 September 2007 01:10, Ryan Moquin wrote: > > If people are build their core infrastructure around Maven to the point > > where they feel like they should give the project developers a hard time > > due to something as simple as documentation, don't you think then that it's > > time to contribute? > I concur wholeheartedly... > > -- > Michael McCallum > Enterprise Engineer > mailto:[EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
