bob mcwhirter <[EMAIL PROTECTED]> writes:
>would like to holler DO IT NOW!, go ahead. But, we'll just sit here
>and keep writing code. If you want to write a proposale to form
>a committee to vote upon the repo structure, go head. But, we'll
>just sit here and keep writing code.
Sorry Bob, but this is the thousand monkeys approach to software
development. It explains why some parts of maven look as they do. :-)
Ok, it is called "eXtreme programming" these days and hip people do
cool talks about it, but I've learned that in the eighties as
"spaghetti coding". Yes, I do it from time to time, too. :-)
Or why the plugin language changed at least once (or twice? DVSL ->
Jelly I do remember. Wasn't there some ant involved, too? :-) )
While I don't like committees, I've learned that having some plan
where one wants to end, really helps deciding where to go (The
Odysseus approach to project management).
You wrote: "Jason has won a user base". This is at least partly not
true. I would still happily use ant to build Turbine if the Turbine
build process wouldn't have been forcefully converted to some maven
version, then the ant build being broken and then finally removed. I
don't feel being won. I still feel being at least half-assimilated
(The Microsof^wBorg approach to software development) about "having
been converted to see the light".
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
