Community made patches, bug reports and contributions are always welcome!
When contributing please ensure you follow the guidelines below so that we can keep on top of things.
- Submit a ticket for your issue, assuming one does not already exist.
- Raise it on our Issue Tracker
- Clearly describe the issue including steps to reproduce the bug.
- Make sure you fill in the earliest version that you know has the issue as well as the version of WordPress you're using.
- Fork the repository on GitHub
- Make the changes to your forked repository
- Ensure you stick to the WordPress Coding Standards
- When committing, reference your issue (if present) and include a note about the fix
- Push the changes to your fork and submit a pull request to the 'master' branch of this repository
- We ensure that every function is documented well and follows the standards set by phpDoc
- An example function can be found here
- Please make sure that every function is documented so that when we update our API Documentation things don't go awry!
- If you're adding/editing a function in a class, make sure to add
@access {private|public|protected}
- If you're adding/editing a function in a class, make sure to add
- Finally, please use tabs and not spaces. The tab indent size should be 4 for all library code.
At this point you're waiting on us to merge your pull request. We'll review all pull requests, and make suggestions and changes if necessary.