Nobody likes to do documentation. That's a problem in a volunteer effort. If Tapestry's committers reported to me, I'd be parceling out the kind of documentation you're talking about. That's not how it works.
Why don't you create JIRA issues for those documenation tasks? This would show that documentation is as important as improvements/bugfixes and enhances Tapestrys overall quality. This could also lead to the community being able to contribute something to the framework. I for one like to pick myself some simple issue like localizing message catalogs or improving documentation and contribute and I could imagine that others might do the same.
Uli --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
