[CONF] Apache Tapestry > Community

[confluence]

Community Page edited by Christophe Cordenier Comment: Rename page and move documentation on how to get involved here Changes (10) {html}<div id="third-parties">{html} h2. Tutorials Tapestry has an active community of users and developers. This page give you an overview of the great effort of all the community. {toc} h1. Tutorials * [Tapestry JumpStart|http://jumpstart.doublenegative.com.au/home.html] by Geoff Callender {quote} ... {quote} h2. Modules * [Community's Wiki|http://wiki.apache.org/tapestry/FrontPage] (Moin Moin) {quote} This contains a lot of user-generated information on different concrete web application use cases. {quote} h1. Modules * [Chenille Kit|http://www.chenillekit.org/] by Massimo Lusetti {quote} ... {quote} h21. Extensions * [Ars Machina|http://www.arsmachina.com.br/] by Thiago H. de Paula Figueiredo ... {quote} h21. IDE Integrations * [loom-t5|http://code.google.com/p/loom-t5/] by Chris Scheid ... {quote} h1. Getting Involved h2. Mailing Lists The primary method of discussion is on the Tapestry users mailing list: [mailto:us...@tapestry.apache.org]. You can subscribe by sending e-mail to [mailto:users-subscr...@tapestry.apache.org]. This is the appropriate mailing list to learn more about Tapestry, to request help, and to socialize. The second mailing list is [mailto:d...@tapestry.apache.org]. You can subscribe to this list by sending e-mail to [dev-subscr...@tapestry.apache.org|mailto: dev-subscr...@tapestry.apache.org]. This list is used by the Tapestry PMC and committers to run votes, discuss issues and fixes, and plan the future of Tapestry. Please don't use this mailing list to ask for support. Mailing list archives are available at [http://tapestry.markmail.org/]. h2. Reporting Problems / Getting Support Tapestry issues are tracked in the [Apache JIRA|https://issues.apache.org/jira/browse/TAP5]. 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, 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|http://catb.org/esr/faqs/smart-questions.html]. If you are not getting a response to your problem, 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 ... it's fun and informative. h2. Source Code Access Source code for Tapestry can be [downloaded|TAPESTRY:Download] along with pre-compiled binaries. Tapestry uses [Subversion|http://subversion.apache.org/] to manage the project's source code. Web access to the Tapestry repository is available as [http://svn.apache.org/viewvc/tapestry/tapestry5/trunk]. Access using Subversion client: {noformat} $ svn checkout https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk tapestry-project {noformat} There's also some [notes on using Git to access Tapestry|http://tapestryjava.blogspot.com/2010/04/setting-up-committer-access-git-for.html]. h2. Other Resources There is an active flow of questions and answers about Tapestry at [Stack Overflow|http://stackoverflow.com/questions/tagged/tapestry]. h2. Becoming a Contributor The best way to become a contributor is to become active on the mailing list; Tapestry is known to have an active and helpful community on the mailing list, and the more mentors we can add, the better. If you want to help out with documentation, you must sign an [Apache Contributor License Agreement|http://www.apache.org/licenses/#clas], at which point we can grant write access to the Confluence Wiki (where official documentation is created). Providing patches (with tests\!) is another way to become a contributor. h2. Becoming a Committer Active contributors may be asked to become full committers, with write access to the source code. Generally, contributors who have been consistently active and helpful for three to six months are eligible for committer access. If you think you are in that category, don't be shy about contacting members of the Tapestry PMC (Project Management Committee). {html}</div>{html} Full Content Tapestry has an active community of users and developers. This page give you an overview of the great effort of all the community. Tutorials Modules Extensions IDE Integrations Getting Involved Mailing Lists Reporting Problems / Getting Support Source Code Access Other Resources Becoming a Contributor Becoming a Committer Tutorials Tapestry JumpStart by Geoff Callender JumpStart is an easy way to learn Tapestry 4 or 5 by example, and it's free! It's an instant, working application, ready for you to explore and modify. It's built entirely on open-source items. You are welcome to use any part of JumpStart for your own applications. Shams Examples by Mohammad H. Shamsi A variety of examples of Tapestry 5 pages and components. Community's Wiki (Moin Moin) This contains a lot of user-generated information on different concrete web application use cases. Modules Chenille Kit by Massimo Lusetti Collection of modules, services, utilities and components (many of which require only tapestry-ioc). Provide integrations with Google services, LDAP, Lucene, Mail, Quartz, JasperReports, Bean Scripting Framework, and more. Equanda-tapestry5 by Joachim Van der Auwera Components useful for building enterprise applications. Includes Accordion, Tabs, Form Traversal. Amongst other things, these focus on easy input of data without the need for a mouse. Godcode Components by Chris Lewis A mixed collection of components providing simple but time-saving functionality, as well as more exotic ones; built on top of the Prototype and Script.Aculo.Us _javascript_ libraries. ioko-tapestry-commons by Ben Gidley, et al. Provides components for caching, cache control, and simple Flash movie integration. Tapx by Howard M. Lewis Ship Collection of modules and components: improved DatePicker, dynamic Tapestry templates, offline rendering using Tapestry, YUI integration, Confirm dialog mixin, Kaptcha components, and more! tacos-seam by Igor Drobiazko Intregrates with JBoss Seam to manage conversational state Extensions Ars Machina by Thiago H. de Paula Figueiredo Tapestry/Hibernate extensions for Generic DAOs, standard CRUD interfaces, and user access logging and tracking. Tynamo project by Tynamo Team / Kalle Korhonen & Alejandro Scandroli Tynamo is model-driven, full-stack web framework based on Tapestry 5, allowing you to jump directly for your Hibernate entities to a full-blown CRUD application. Tynamo provides several modules, including tapestry-model, tapestry-conversations, tapestry-hibernate-seedentity, tapestry-resteasy and tapestry-security. IDE Integrations loom-t5 by Chris Scheid Eclipse plugin for building Tapestry 5 projects Getting Involved Mailing Lists The primary method of discussion is on the Tapestry users mailing list: us...@tapestry.apache.org. You can subscribe by sending e-mail to users-subscr...@tapestry.apache.org. This is the appropriate mailing list to learn more about Tapestry, to request help, and to socialize. The second mailing list is d...@tapestry.apache.org. You can subscribe to this list by sending e-mail to dev-subscr...@tapestry.apache.org. This list is used by the Tapestry PMC and committers to run votes, discuss issues and fixes, and plan the future of Tapestry. Please don't use this mailing list to ask for support. Mailing list archives are available at http://tapestry.markmail.org/. Reporting Problems / Getting Support Tapestry issues are tracked in the Apache JIRA. 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, 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, 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 ... it's fun and informative. Source Code Access Source code for Tapestry can be downloaded along with pre-compiled binaries. Tapestry uses Subversion to manage the project's source code. Web access to the Tapestry repository is available as http://svn.apache.org/viewvc/tapestry/tapestry5/trunk. Access using Subversion client: $ svn checkout https://svn.apache.org/repos/asf/tapestry/tapestry5/trunk tapestry-project There's also some notes on using Git to access Tapestry. Other Resources There is an active flow of questions and answers about Tapestry at Stack Overflow. Becoming a Contributor The best way to become a contributor is to become active on the mailing list; Tapestry is known to have an active and helpful community on the mailing list, and the more mentors we can add, the better. If you want to help out with documentation, you must sign an Apache Contributor License Agreement, at which point we can grant write access to the Confluence Wiki (where official documentation is created). Providing patches (with tests!) is another way to become a contributor. Becoming a Committer Active contributors may be asked to become full committers, with write access to the source code. Generally, contributors who have been consistently active and helpful for three to six months are eligible for committer access. If you think you are in that category, don't be shy about contacting members of the Tapestry PMC (Project Management Committee). Change Notification Preferences View Online | View Changes