Jeff - no offense intended. My point is that open source is,
especially at ASF, about "scratching itches". Tapestry has some of
the best documentation of any open source framework out there, along
with a complete running example application or two. Howard himself
has done a fantastic job at keeping the documentation at that level.
Most committers for open source projects simply don't have that itch
to scratch and are not as keen to know what general users would need
in terms of documentation. It is helpful if the community chips in
for this kind of thing.
I'm in the "ship early, and often" category. Documentation can
evolve, as well as the code itself. Tap4 needs a final release to
start getting adopted more pervasively. I wouldn't want to hold up a
release for some missing documentation. Many of the folks that would
grab it right away are already familiar with Tap3, I suspect.
Erik
On Dec 12, 2005, at 11:52 AM, Jeff Lubetkin wrote:
You're kidding, right? Howard asked for a vote, I voted.
I like the idea of open source, and I try to contribute to the
community
by answering questions on the lists, filing bugs, and the like, but
I do
have a job with a startup, three small children, a World of Warcraft
addiction to feed, etc. Taking on the documentation of a major
subsystem that I didn't build strikes me as above and beyond the
call of
duty.
In any case, it doesn't change the fact that I don't think Tapestry
should go final with the docs in this condition, independent of the
discussion of who should write those docs.
jeff
-----Original Message-----
From: Erik Hatcher [mailto:[EMAIL PROTECTED]
Sent: Monday, December 12, 2005 5:24 AM
To: Tapestry development
Subject: Re: [VOTE] 4.0 final release
On Dec 11, 2005, at 2:00 PM, Jeff Lubetkin wrote:
The lack of decent documentation of the new (and very cool)
validation system in either the TextField component doc or user
guide makes Tapestry look unprofessional and incomplete. Rather
than having docs to point my developers to, I have to hold a little
validation class every time someone wants to use it. I've been
able to excuse this by saying "well, it's just beta, I'm sure
they'll document it before the final release".
While I agree that the code is ready, I'm registering a (non-
binding, of course) protest vote against calling T4 "final" until
this documentation issue is fixed.
Jeff - this is a classic, and often annoying, response....
How about rather than holding an internal validation class, you
write up the details as patches to Tapestry's documentation and
submit them? Then next time your developers need documentation, you
can say RTM that you helped write. :)
Erik
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
