Phsparak is an open-source community driven project and anyone may contribute for its improvement. We welcome contributors. These contributions are made by Pull Requests on the Phsaprk repository on GitHub.
New Features
Before sending pull requests for new features, please contact Najmul ZCE via e-mail admin@phspark.com. If the feature is found to be a good fit for the framework, you are free to make a pull request. If the feature is rejected, don't give up! You are still free to turn your feature into an extension.
Bugs
If you find a bug in Phspark then please check a few things first:
- There is not already an open Issue
- The issue has already been fixed (check the develop branch, or look for closed Issues)
Reporting issues is helpful but an even better approach is to send a Pull Request. which is done by “Forking” the main repository and committing to your own copy. This will require you to use the version control system called Git.
Also if you believe you have found a bug in the framework, but are unsure how to fix it, please send a pull request containing a failing unit test. A failing unit test provides the development team "proof" that the bug exists, and, after the development team addresses the bug, serves as a reliable indicator that the bug remains fixed.
Security Vulnerabilities
If you discover a security vulnerability within Phspark. The security issues should be reported with an email to our security team, rather than being brought up on the forum or raised as a Github issue, please send an e-mail to Najmul ZCE at admin@phspark.com. All security vulnerabilities will be promptly addressed.
Coding Style
Phspark follows the PSR-2 coding standard and the PSR-4 autoloading standard.