Jeff,
Well spoken. I completely agree.Everyone should realize that when you
don't get user docs, you *are still* waiting a week or two or three,
because you'll end up sinking that time into figuring it out how
everything works, so you certainly aren't coming out ahead by throwing
things out without documentation. In addition, this is going to result
in the mailing lists being flooded with questions on undocumented
feature that would otherwise not be, and is going to raise the
frustration level of every user that struggles to get the undocumented
feature to work.
Brad
Jeff Jensen wrote:
Yes you should. +1. I would rather wait another week or two or three for a
new feature with user docs than have the current path of docs not
materializing often enough.
And reject same for no tests.
Code + tests + docs = valid contribution.
Make your stance, clearly document this on the "How to Contribute" page.
Reject away.
-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, March 06, 2006 11:55 PM
To: Maven Users List
Subject: Re: Maven documentation (was Re: how to include all dependencies in
your jar)
You don't have that problem if everyone documents what they contribute.
So.. we should knock back contributions without documentation? you should
see the reaction we get when we try that!
Ideally, every contribution should have docs and tests. But I don't think
its reasonable to knock it back without it (we should be asking more
persistently though, and above all doing it ourselves).
This still doesn't address the problem that the developers perception of
what is required to understand it is different from everyone else's. It
needs iterative improvement.
---------------------------------------------------------------------
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]
