Getting Involved

Welcome to Apache Etch

Here are some suggestions for how you can get more involved in Apache Etch.

• Subscribe to the mailing lists. If you are interested to get involved at the user level, subscribe to the user mailing list. If you are interested in the development of Etch, then subscribe to the developer list.
• Help answer questions posted to the user mailing list for areas that you are familiar with. Your real usage experience can be very valuable to other users as well as developers on the project.
• Contribute to feature development. Just let the community know what you would like to work on. It is as easy as that.
• Identify JIRAs in the area that you are interested and provide patches
• Contribute to the user or developer documentation or website. Make your updates on the Etch Wiki, create a JIRA and attach the link for your update.
• If in doubt about where to start, send a note to the mailing list and mention your area of interest. Any questions are welcome. We would like you to be involved!
• If you are new to open source and would like to learn more about how to work in open source, check this page.
• Provide Feedback: What is working well? What is missing? Get involved in creating software that addresses real pain points. Any help is good. Be part of the community.

Source code

Subversion

The source is maintained in Apache's subversion repository at svn.apache.org. If you are a committer for the project, you should use the https url, otherwise if you are just interested in a copy http is fine.

If you do not have a Subversion client for your platform, you can get one here: http://subversion.tigris.org/.

Git

Some of us on the team (namely dixson) also use Git for source management. We publish our repositories publicly too. See Committers for details who publishes where.

If you are interested in using Git, we recommend either cloning the subversion trunk or cloning one of the public repositories of the Committers.

If you do not have a Git client for your platform, you can get one here: http://git-scm.com.

Development Model

We tend to do primary development against the Subversion trunk. Once we believe we are reaching a point of stability, we will make a branch and close out the release.

Nightly Builds

.. coming soon

We need a home for our continuous build. It needs to be able to build java as well as c# artifacts. Others are coming soon.

Making a Release

Currently James Dixson and Scott Comer are enabled to make releases. Here is the procedure:

Making a Release

Anyone can check a release, and we encourage you to test downloads before using them.

Checking a Release