On 3/7/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote: > Agreed. However, the barrier to entry is actually quite high in this > regard from personal experience on open source projects that place > documentation below everything else. Contributions only go so far when > made by a non-committer.
Yep, this is what I meant by this bit below, and also why I highlighted that there are other ways to contribute. > > Now, we do know there are missing pieces of documentation, and are > > correcting that over time. It's also my personal vendatta to write > > docs for new functionality at least going forward, and even if they > > are brief so that people can expand on them easily. I don't know why I called it a vendetta, its more of an ambition :) > No offense intended here. I've seen the "give us documentation" and the > "we know - we're working on it" threads. My hat's off to all the work > that's been done. None taken, it was a general comment. > *sigh* yeah... [been trying that approach - not w/ maven (yet) - and > met with limited success because of "that's documentation. we're here to > work on code" responses (or complete lack of response entirely) - hence > my ire over "have users just look at the code" opinions.] Nah, I think that's a last resort. Because then we'd need to document the code :) > This is possibly the best thing I've ever heard said about a wiki. > Taking knowledge from a wiki into documentation is great. Using a wiki > AS documentation is where my issue arises. :) - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
