Community
We would love to welcome you in the community around Apache Zeta Components, no matter what your gender, skills, social or political interest are. You can help us with Apache Zeta Components by documenting, developing the components and by supporting other users using the components. Introduce yourself and we will find something you enjoy working on, which matches your skills and interests.
For documentation there are tutorials available for each component, as well as full API documentation. The tutorials are managed in the SVN. get in contact with us, if you like to improve them.
Getting in contact
You can get in contact with other developers and users using one of the common communication channels:
IRC
The Apache Zeta Components developers are currently using an IRC channel on the FreeNode IRC network: irc://irc.freenode.net/#zetacomponents
A tutorial describing how to use IRC for chatting with the developers can be found here: http://www.irchelp.org/irchelp/irctutorial.html
Mailing lists
There are multiple mailing lists available for Apache Zeta Components. The mailing lists most important for users are:
For questions regarding the development of Apache Zeta Components
zeta-users@incubator.apache.org
For questions regarding the usage of the components
zeta-commits@incubator.apache.org
Commit mailinglist
You can subscribe to the mailing llists by sending a mail to <name>-subscribe@incubator.apache.org.
The mailing list archives are also available:
Further resources
There are a few things to remember when you want to contribute code to the project:
To add functionality the whole development process should be followed.
All new functionality has to be documented.
Contributors must grant us the right to include their contribution. When contributing code, please submit a CLA (Contributor Licensing Agreement) to the Apache Software Foundation.
You have to keep backwards compatibility.
In order to avoid misunderstandings, we suggest you have a look at the detailed development process first.
Bugfixes are of course always welcome. If you want to help out with bugs simply pick a bug and fix it in svn trunk (or the latest supported version with the problem). When you are done, add the patch as an attachment to the bugreport. If you are planning to solve bugs, or if you just want to avoid duplicate work or need some information, send an email to the relevant mailinglist first so we know what you want to do.
Coding standards
All developers of this project adhere to coding standards, which help to maintain a clean code base.
Code repository (SVN)
Development is hosted on a subversion (SVN) server where the source code is accessible. You can clone trunk/ with Git by using the Git mirror or its Github mirror. You can also browse the source code by using the dedicated fisheye.
Reporting bugs
If you find a bug, feel free to report it in the issue tracker.