Bugs and New Features
If you think you've found a bug and would like to report it or have ideas for new features or functionality, the first step would be to create an issue on Vulnero's GitHub page.
Contributing
If you'd like to submit a new feature or bug fix, create a GitHub pull request which I'll review and potentially include in the project. I do ask that all submissions adhere to a few simple guidelines:
- Following the Zend Framework coding standards as closely as you can (which includes docblocking to your files, classes and methods).
- Create new PHPUnit tests for all new functionality (though I'm happy to do this for you if the feature is in enough demand) as I'm shooting for full unit-test coverage with every release. For updates or bug fixes, make sure all existing PHPUnit tests pass.
- Please do not include any proprietary or non-open source licensed code as it may contradict my license or limit my ability to distribute the software through all current channels.
Basic Questions
If you have questions about using Vulnero, you can always email me at akandels [at] gmail.com or create a post on the GitHub project page.
Commercial Support / Custom Development
Much of why I wrote Vulnero was to help me with custom development work I do as a private contractor. If you'd like to see if I'm available for a project, or would like to leverage me as a support resource, contact me at akandels [at] gmail.com. For examples of my work, see my portfolio or my LinkedIn page
.