Craig R. McClanahan wrote: > Or, to put it another way, using Maven as a
build system will give us a website/docs publishing system for free.
Well, last I knew, TANSTAAFL. =:)
It's nice that Maven has a build system, so long as it's a build system that fits our needs. Likewise, it's nice that Maven has reports, so long as are they are reports our team will actually use. =:)
I haven't tried it, so I'm not stating an opinion here, except TANSTAAFL.
I have noticed that a lot of the Maven deployments do not seem to be using all the default features, giving the site an "unfinished" feel. This seems like a hint that Maven may be easier to deploy than to configure. Meanwhile, Maven itself is in perpetual beta, which hints that build and comprehension tools don't necessarily speed shipping times =:) (OK, like we should talk about long incubations.)
I don't actually care, and, lacking a basis of comparison, I don't even know if what we have now is broken. Will Maven or Forrest be less work? If so, great. Personally, I don't care about the "look and feel" issues. It looks the way it looks. I just want to know if it will make better use of our volunteer time.
The one thing I wouldn't want is people falling into FUD mode because at some point something might change. If someone wants to sign-up for migrating the site to Maven or Forrest, that would be great. But, a consensus without a working group starts to devolve into a roadblock.
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
