Brett Porter wrote:
discussing whether it's as bad as you say, really. It's hard not to
get drawn into that because it does feel like an attack on our work,
If requesting documentation commensurate with current maven feature, in
tandem with compliments for the maven code itself, is considered "an
attack on our work" then I give up. I think the real point, as evidenced
by the typical "we know, we know" and "if you want doc, write it
yourself" responses both on the mailing list and IRC, is that raising
the issue of documentation is a nuisance. I don't generally view things
that way -- its all opportunity, and the more voices on a particular
issue, it possibly lends more weight to the need, which I would think
would be a valuable source of direction to developers. But others I
suppose will choose to view it just as an isolated complaint, and
something they don't want to hear. Difference in people, I guess.
And again, thanks for your concern. If you have time to contribute to
this, it would be extremely welcomed.
I've contributed a new plugin, and mods to two existing plugins, and
also posted some time ago about how I could go about documenting maven
myself from beginning to end on this mailing list. Unless I missed a
helpful response, the responses I received didn't give me any direction
for doing this other than just reading code and existing doc. My
definition of "extremely welcomed" goes a little beyond this.
I'm really out of words on this, and at any rate, you've made clear you
feel this discussion is a waste of time, so I'll oblige, and drop it.
Back to using maven. I really do appreciate that you've shared your
views on this, despite your disagreement with mine.
Cheers,
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
