Hệ thống quản lý trường học bằng PHP / MySQLi
1 # How to contribute
2
3 This project is open to many different types of contribution. You can help with improving the documentation and examples, sharing your insights on the issue tracker, adding fixes to the code, providing test cases, or just [writing about your hardware setup that you use](https://github.com/mike42/escpos-php/issues/new).
4
5 ## Issue tracker
6
7 Open issues of all sorts are tracked on the [issue tracker](https://github.com/mike42/escpos-php/issues). Please check [the FAQ](https://github.com/mike42/escpos-php/blob/development/doc/FAQ.md) before you post, and practice good [bug tracker etiquette](https://bugzilla.mozilla.org/page.cgi?id=etiquette.html) to keep it running smoothly.
8
9 Issues are [loosely categorised](https://github.com/mike42/escpos-php/labels), and will stay open while there is still something that can be resolved.
10
11 Anybody may add to the discussion on the bug tracker. Just be sure to add new questions as separate issues, and to avoid commenting on closed issues.
12
13 ## Submitting changes
14
15 Code changes may be submitted as a "[pull request](https://help.github.com/articles/about-pull-requests/)" at [mike42/escpos-php](https://github.com/mike42/escpos-php). The description should include some information about how the change improves the library.
16
17 The project is MIT-licensed (see [LICENSE.md](https://github.com/mike42/escpos-php/blob/development/LICENSE.md) for details). You are not required to assign copyright in order to submit changes, but you do need to agree for your code to be distributed under this license in order for it to be accepted.
18
19 ### Documentation changes
20
21 The official documentaton is also located in the main repository, under the [doc/](https://github.com/mike42/escpos-php/tree/development/doc) folder.
22
23 You are welcome to post any suggested improvements as pull requests.
24
25 ### Release process
26
27 Once a pull request is accepted, it usually appears in a release a few days later.
28
29 Branches:
30
31 - "development" is the most recent code, possibly containing unreleased fixes
32 - "master" contains the most recently released code (old versions are not maintained).
33
34 The release process for your changes is:
35
36 - Changes are submitted via pull request to the shared "development" branch.
37 - A new release is staged on the "master" branch via another pull request, and then tagged.
38
39 ## Code style
40
41 This project uses the [PSR-2 standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md) for all PHP source code.
42
43 ## Testing and CI
44
45 The tests are executed on [Travis CI](https://travis-ci.org/mike42/escpos-php) over PHP 5.3, 5.4, 5.5, 5.7, 7, and HHVM. Earlier versions of PHP are not supported.
46
47 For development, it's suggested that you load `imagick`, `gd` and `Xdebug` PHP exensions, and install `composer`.
48
49 Fetch a copy of this code and load dependencies with composer:
50
51 git clone https://github.com/mike42/escpos-php
52 cd escpos-php/
53 composer install
54
55 Execute unit tests via `phpunit`:
56
57 php vendor/bin/phpunit --coverage-text
58
59 Code style can be checked via [PHP_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer):
60
61 php vendor/bin/phpcs --standard=psr2 src/ -n
62
63 The developer docs are built with [doxygen](https://github.com/doxygen/doxygen). Re-build them to check for documentation warnings:
64
65 make -C doc clean && make -C doc
