[Tapestry-developer] Volume vs. Work Load vs. Life

[Howard M. Lewis Ship]

It's nice to see that the volume of list is increasing.  It's also really great to see the other Tapestry committers in there and answering questions at all levels.   I've just been noticing that my backlog of messages is getting larger and larger.  I try really hard to answer as many questions as possible, but its turning into a losing battle.   These aren't official rules or guidelines (we didn't vote on them :-) ), they are my personal considerations.   First off, don't send mail just to me, always send it to the group.   If you are having a problem with  Tapestry, provide details!  Don't say "I did this and it failed".  What is "failed"?  Provide more details off the bat for a faster response ... especially stack traces and other details from the exception report.  More information is rarely a problem.  Source code is usually helpful as well.  Basically, if we have to get in a long dialog to extract the information from you, it may not happen ... we'd all rather be coding!   If you've posted a question and gotten no response, try reposting with more description and detail.  Posting "My form broke" may not get a response, but a detailed question about how, on submit, the form submit operations didn't occur in the way you would have expected (for example), may get a fast response instead of none at all.   Also, any mail sent to me about Tapestry is likely to get a response CC'ed to the list unless YOU EXPLICITLY SAY NOT TO.   ---- Howard Lewis Ship [EMAIL PROTECTED] http://tapestry.sf.net