Contributor Guide

Have something you want to contribute back? Follow this helpful guide.

In the spirit of open-source software, you can contribute as little or as much as you like: bug reports, patches, full components or documentation are all equally appreciated. The following section describes contributing for Zend Framework version 2.

If you are wanting to contribute back to version 1 of the framework, please read "Zend Framework v1 Contributions".

So, You Want to File A Bug Report ...

So, you've found what you think might be a bug. Before you file it, we'd ask that you ensure that what you have is indeed a bug, by doing a little due-diligence (which also is good information to add to the bug report):

You don't have to do all of those, but by doing a few of them, it helps ensure that your bug report is complete and will get tended to. When you're finally ready, go to our issue tracker for ZF2.

So, You Want to Contribute Code ...

By and large, this framework is built and maintained by the community. This means that process for submitting something back, be it a patch, some documentation, or new feature requires some level of community interactions. As you can see with the "Fork Me On Github" banner on the top right of this page, we proudly host our code on github.com.

If you're not already familar with git or github, take a moment to read through our README-GIT.md. Committing code is easy:

  1. Fork the zf2 project
  2. Create a local development Branch for the bugfix.
  3. Commit a change and push your local branch to your github fork.
  4. Send us a pull request for your changes to be included.

So, You Want to Hang-out With A Great Community ...

ZFers, as they are called, hang out in a number of different places. Offline hangouts:

Online, ZFers can be found (links to more information on how to connect):