> From: "Chris K Chew" <[EMAIL PROTECTED]> > >> Scott: >> Much of what you are suggesting in this post is already covered by the >> documentation that is produced by maven. > > Scott, do you think we should create the Developer's Guide as a "catch-all" > to steer people towards the documents you mentioned, or forego the Dev-Guide > and hope potential developers are clever enough to find them on their own? > > Personally, I think we should expect them to figure out how turbine works > simply from the source code and build system. I think you meant to say: "I do not think..." ;-)
One of the goals of maven is to put all of this stuff in a standard place for all projects (obviously this means "all projects that use maven"). This reduces the amount of hand holding required. Seriously, a twiki is the way to go. Everyone (including non-committers) can have write access. Everyone can review/edit/reformat/reorganise the postings made by others. I have no problem with a developers guide that provides some hand holding by including links to the relevant information. What I do object to is the same information being repeated in multiple places - this is just asking for trouble. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:turbine-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:turbine-user-help@;jakarta.apache.org>
