Put the other shoe on... jakarta developers have the same set of bosses/wives/children who don't accept explanations of needing to write docs.
Actually, my boss gets quite irate if I don't document things so that someone can come in and use our software. But I also see your point, as I have a wife who would rather have me spending time with her than my computer. :-)
If anything, I think it's a tribute to how good of a job the Hibernate committers are for doing this. As having been one of those lothesome Jakarta committers, who has told so many people that if they want something fix/doc'd to fix/doc it, I really appreciate how much Max, Gavin, Christian, et al do.
I think I my implicit idea was how much I appreciate how well Hibernate is documented. I have found only one place where the docs didn't live up to reality. (And I might even submit a patch to them to make it clearer)
This implies you'd prefer people didn't donate source code unless they are prepared to doc it and meet other requirements. I would rather have the code in contention and then quickly dropped rather than never had that opportunity. I agree that value(docs) >= value(code), so you try to help when you can.
I agree that having the opportunity to have access to code with no docs is much better than that code having never been available. I greatly appreciate the contributions of the Jakarta projects and use them a lot in my personal projects. I just get very frustrated when there aren't docs or the docs are wrong. Cause then convincing my boss that we should use it becomes that much harder.
Patrick
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
