mirror of
https://github.com/billz/raspap-webgui.git
synced 2025-03-01 10:31:47 +00:00
Update CONTRIBUTING.md
This commit is contained in:
parent
c2d04a98a7
commit
77eb23b0e8
@ -1,18 +1,22 @@
|
|||||||
## How to contribute
|
## How to contribute
|
||||||
Everyone is invited and welcome to contribute to RaspAP. There's a lot to do — if you're not a developer perhaps you'd like to help with the documentation on [docs.raspap.com](https://docs.raspap.com)? If you're a devloper, the process of contributing code is straightforward.
|
Everyone is invited and welcome to contribute to RaspAP. There's a lot to do — if you're not a developer we can always use help with the official [project documentation](https://docs.raspap.com). If you have experience in Linux networking, you can share your knowledge by answering questions from RaspAP users in our [GitHub discussions](https://github.com/RaspAP/raspap-webgui/discussions) and/or the [/r/RaspAP](https://reddit.com/r/RaspAP) subreddit.
|
||||||
|
|
||||||
1. Fork the project in your account and create a new branch: `your-great-feature`.
|
If you're a devloper, the process of contributing code is straightforward:
|
||||||
2. Open an issue in the repository describing the feature contribution you'd like to make. This will help us get you started on the right foot.
|
|
||||||
3. Commit changes in your feature branch.
|
1. Fork the project in your account and create a new branch: `feat/your-feature` or `fix/your-bugfix`.
|
||||||
4. Open a pull request and reference the initial issue in the pull request message.
|
2. Open [an issue](https://github.com/RaspAP/raspap-webgui/issues) describing the feature or bug fix contribution you'd like to make.
|
||||||
|
3. Commit changes in your branch.
|
||||||
|
4. Open a pull request and reference the initial issue in the pull request message, or by linking it in GitHub.
|
||||||
|
|
||||||
### Coding standards
|
### Coding standards
|
||||||
This project follows the [PSR-2](http://www.php-fig.org/psr/psr-2/) coding style guidelines. There are many ways to check your code for PSR-2. An excellent tool is [PHP_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer). The command line tool phpcs can be run against any single file. [Phing](https://www.phing.info/), a PHP build tool, integrates nicely with `phpcs` to automate PSR-2 checks across all source files in a project.
|
This project follows the [PSR-2](http://www.php-fig.org/psr/psr-2/) coding style guidelines. There are many ways to check your code for PSR-2. An excellent tool is [PHP_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer). The command line tool phpcs can be run against any single file. [Phing](https://www.phing.info/), a PHP build tool, integrates nicely with `phpcs` to automate PSR-2 checks across all source files in a project.
|
||||||
|
|
||||||
### RaspAP community
|
### RaspAP community
|
||||||
RaspAP is made possible by a strong [community of developers](https://github.com/RaspAP/raspap-webgui/graphs/contributors). If you have any questions or would like to get involved in RaspAP's community, check out these resources:
|
RaspAP is made possible by a strong [community of developers](https://github.com/RaspAP/raspap-webgui/graphs/contributors). If you have any questions or would like to get involved in RaspAP, dive into any of these channels:
|
||||||
|
|
||||||
* [Github issues](https://github.com/RaspAP/raspap-webgui/issues)
|
* [GitHub discussions](https://github.com/RaspAP/raspap-webgui/discussions)
|
||||||
* [Gitter chat](https://app.gitter.im/#/room/#RaspAP:gitter.im)
|
* [Gitter chat](https://app.gitter.im/#/room/#RaspAP:gitter.im)
|
||||||
* [Twitter](https://twitter.com/rasp_ap)
|
* [Twitter](https://twitter.com/rasp_ap)
|
||||||
* [Reddit](https://www.reddit.com/r/RaspAP/)
|
* [Reddit](https://www.reddit.com/r/RaspAP/)
|
||||||
|
|
||||||
|
If you enjoy using RaspAP and would like to support our work financially, consider becoming an [Insider](https://github.com/sponsors/RaspAP).
|
||||||
|
Loading…
x
Reference in New Issue
Block a user