How to contribute?

The Apache Cocoon™ project is actively seeking new contributors to work on all aspects of the project. We need and appreciate all contributions, including documentation help, source code development and feedback.

Code

When you have found an issue or you want to propose a new feature, post a message to Cocoon User's list to discuss it.
Search existing issues to see whether someone had already encountered the same issue.
If this issue is never encountered before, create a JIRA issue for Cocoon 2.1/2.2 or 3.0.
Develop a test case to demonstrate the issue.
Attach the new test to JIRA issue.
If you have also developed a fix for the raised issue, attach a patch to it. Here are some useful guidelines about how to correctly generate a patch.

Documentation

The website is managed via the maven-site-plugin, hence contributing site content is very close to contributing source code: create a new issue on JIRA and attach there a SVN patch. See this page for more information.

The project wiki is also there to gather any other kind of documentation or contribution you would like to contribute, and does not require any SVN, Maven or other technical skills.

Quick references

Discussion occurs on the Cocoon mailing lists
Information on access to the project source code is available for Cocoon 2.2 and 3.0.
Bugs and other issues can be posted on the Cocoon 2.1/2.2 and 3.0 JIRA

How do I become a contributor or a committer?

Everyone can contribute to Cocoon as a contributor; contributors who build up a history of successful contributions over time are invited to become committers. The difference is that committers have direct write access to the project SVN repositories, while contributors post their contributions to JIRA issues where they're first reviewed, and then committed by a committer to the project's SVN repository. See http://www.apache.org/dev/contributors.html for a good overview of working as a contributor.

We ask contributors of significant amounts of code to fill out and send into Apache, an Individual Contributors License Agreement (ICLA) (and perhaps also a Corporate Contributors License Agreement (CCLA)).

If you're interested in committing to the project, you need to establish a history over time of successful contributions to the project. After that, you can be invited to become a committer.

You'll need to fill out some legal paperwork and go through a process to get an apache committer account: See New Committers Guide, Contributors, and Committers for more details.
After you've received an email from root@apache.org with your committer account information, change your initial password at Apache Account Utility. For more details see Committer Subversion Access.
Check out the Cocoon sources and test your svn account: Subversion Repository.

All Contributors and Committers should