...

Unless your problem is clear as day, it's a good idea to discuss it on the Tapestry Users mailing list first, before adding an issue. At the same time, its it's generally unlikely that a bug will be fixed unless a JIRA Issue is created.

Eric Raymond has a detailed guide to asking questions the right way. If you are not getting a response to your problem, its it's likely because you aren't asking it the right way.

Just saying something is "broken" or "failed" is not enough. How did it fail? Did it do the wrong thing? Throw an exception? Not respond in any way? What exactly did you expect to happen? All of this information should be made available when looking for help, plus context on the general problem you were trying to solve in the first place (there may be a better solution entirely). Read Eric Raymond's guide ... its it's fun and informative.

Source Code Access

...

Tapestry uses Subversion to manage its the project's source code.

Web access to the Tapestry repository is available as http://svn.apache.org/viewvc/tapestry/tapestry5/trunk.

...

• JavaServer Faces 2.0 vs. Tapestry 5: A Head-to-Head Comparison by Igor Drobiazko at Jazoon 2010
• Tapestry 5: Java power, Scripting Ease by Howard Lewis Ship at Devoxx 2009

More presentations ...

Tapestry Wikis

• Community's Wiki (Moin Moin) contains a lot of user-generated information on different concrete web application use cases.
• Documentation Source wiki (Confluence) – the wiki used as the content editor for the official Tapestry documentation

...