Contributor Guide

Have something you want to contribute back?

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 to Zend Framework.

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:

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 interaction. We proudly host our code on GitHub.

If you're not already familar with git or GitHub, take a moment to read through our The steps to create a patch are:

  • fork the zend-name project (where name is the component you are interested);
  • create a local development branch for the bugfix;
  • commit a change and push your local branch to your github fork;
  • send us a pull request for your changes to be included.

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

Zend Framework users hang out in a number of different places. You can meet offline in conferences and in a number of user groups and meetups. Check for the ZendCon conference, each year in the USA in October, and search for Zend Framework talks on

Online, Zend Framework users and developers can be found in some of the following locations:


© 2006-2017 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.