| Server IP : 49.231.201.246 / Your IP : 216.73.216.149 Web Server : Apache/2.4.18 (Ubuntu) System : Linux 246 4.4.0-210-generic #242-Ubuntu SMP Fri Apr 16 09:57:56 UTC 2021 x86_64 User : root ( 0) PHP Version : 7.0.33-0ubuntu0.16.04.16 Disable Function : exec,passthru,shell_exec,system,proc_open,popen,pcntl_exec MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /var/www/html/water/vendor/dektrium/yii2-user/.github/ |
Upload File : |
# Contributing to Yii2-user Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved. Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features. ## Do you have a question or problem with using Yii2-user? Ask any question about how to use Yii2-user on [our forum](http://dektrium.com). ## Did you find a security issue? Please don't use forum or Github issues to report security issues. Instead contact us directly by using following email address: `dmeroff@gmail.com`. ## Did you find a bug? - Ensure the bug was not already reported by searching on GitHub under Issues. - If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring. ## Do you intend to add a new feature or change an existing one? - Suggest your change on [our forum](http://dektrium.com) and start writing code. - Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes. ## Did you write a patch that fixes a bug? - Ensure your code follows PSR-2 code style - Commit your changes in logical chunks. Please adhere to [these git commit message guidelines](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) or your code is unlikely be merged into the main project. Use Git's interactive rebase feature to tidy up your commits before making them public. - Open a new GitHub pull request with the patch. - Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable. > **IMPORTANT**: By submitting a patch, you agree to allow the project owner to license your work under the same license as that used by the project.