THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| HTML |
|---|
<div id="third-parties"> |
Tapestry has an active community of users and developers. This is an overview of how to participate, along with a list of some of the great contributions of the community members.
| Table of Contents |
|---|
Getting Involved
Reporting Problems / Getting Support
| Include Page | ||||
|---|---|---|---|---|
|
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.
Contributing translations for Tapestry built-in messages
If Tapestry's built-in messages aren't available in your language, you are welcome to contribute a new translation of the message catalogs. For easy instructions, see Localization.
Source Code Access
Source code for Tapestry can be downloaded along with pre-compiled binaries.
Tapestry uses Git to manage the project's source code.
Web access to the Tapestry repository is available as GIT-WIP at Apache.
Access using Git client:
| No Format |
|---|
$ git clone http://git-wip-us.apache.org/repos/asf/tapestry-5.git
|
(See Building Tapestry from Source for more info.)
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. (See the Developer Bible for important guidance on source code formatting, class naming conventions, etc.)
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).
...
Community Contributions
| Section | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Getting Involved
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.
Contributing translations for Tapestry built-in messages
If Tapestry doesn't support your language and you would like to contribute a new translation of the message catalogs, feel free to translate the following files
- For Tapestry 5.4 and later:
- For Tapestry 5.3.x:
Then open a new feature request here, attach the translated files, and they'll be included in the next release!
| Info |
|---|
Please note that a patch is always preferred over an archive of properties files. |
Source Code Access
Source code for Tapestry can be downloaded along with pre-compiled binaries.
Tapestry uses Git to manage the project's source code.
Web access to the Tapestry repository is available as GIT-WIP at Apache.
Access using Git client:
| No Format |
|---|
$ git clone http://git-wip-us.apache.org/repos/asf/tapestry-5.git
|
(See Building Tapestry from Source for more info.)
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
...
| HTML |
|---|
</div> |