bunkerized-nginx/CONTRIBUTING.md

# Contributing to bunkerweb

First off all, thanks for being here and showing your support to the project !

We accept many types of contributions whether they are technical or not. Every community feedback, work or help is, and will always be, appreciated.

## Talk about the project

The first thing you can do is to talk about the project. You can share it on social media (by the way, you can can also follow us on [LinkedIn](https://www.linkedin.com/company/bunkerity/), [Twitter](https://twitter.com/bunkerity) and [GitHub](https://github.com/bunkerity)), make a blog post about it or simply tell your friends/colleagues that's an awesome project..

## Join the community

You can join the [Discord server](https://discord.com/invite/fTf46FmtyD), the [GitHub discussions](https://github.com/bunkerity/bunkerweb/discussions) and the [/r/BunkerWeb](https://www.reddit.com/r/BunkerWeb) subreddit to talk about the project and help others.

## Reporting bugs / ask for features

The preferred way to report bugs and asking for features is using [issues](https://github.com/bunkerity/bunkerweb/issues). Before opening a new one, please check if a related issue is already opened using the "filters" bar. When creating a new issue please select and fill the "Bug report" or "Feature request" template.

## Code contribution

The preferred way to contribute code is using [pull requests](https://github.com/bunkerity/bunkerweb/pulls). Before creating a pull request, please check if your code is related to an opened issue. If that's not the case, you should first create an issue so we can discuss about it. This procedure is here to avoid wasting your time in case the PR will be rejected. For minor changes (e.g. : typo, quick fix, ...), opening an issue might be facultative. **Don't forget to edit the documentations when needed !**
bunkerweb 1.4.0 2022-06-03 17:24:14 +02:00			`# Contributing to bunkerweb`
add contributing guidelines and license 2021-06-04 10:08:11 +02:00
			`First off all, thanks for being here and showing your support to the project !`

			`We accept many types of contributions whether they are technical or not. Every community feedback, work or help is, and will always be, appreciated.`

			`## Talk about the project`

bunkerweb 1.4.0 2022-06-03 17:24:14 +02:00			`The first thing you can do is to talk about the project. You can share it on social media (by the way, you can can also follow us on [LinkedIn](https://www.linkedin.com/company/bunkerity/), [Twitter](https://twitter.com/bunkerity) and [GitHub](https://github.com/bunkerity)), make a blog post about it or simply tell your friends/colleagues that's an awesome project..`
add contributing guidelines and license 2021-06-04 10:08:11 +02:00
bunkerweb 1.4.0 2022-06-03 17:24:14 +02:00			`## Join the community`
v1.2.7 release 2021-06-15 16:53:37 +02:00
bunkerweb 1.4.0 2022-06-03 17:24:14 +02:00			`You can join the [Discord server](https://discord.com/invite/fTf46FmtyD), the [GitHub discussions](https://github.com/bunkerity/bunkerweb/discussions) and the [/r/BunkerWeb](https://www.reddit.com/r/BunkerWeb) subreddit to talk about the project and help others.`
v1.2.7 release 2021-06-15 16:53:37 +02:00
add contributing guidelines and license 2021-06-04 10:08:11 +02:00			`## Reporting bugs / ask for features`

bunkerweb 1.4.0 2022-06-03 17:24:14 +02:00			`The preferred way to report bugs and asking for features is using [issues](https://github.com/bunkerity/bunkerweb/issues). Before opening a new one, please check if a related issue is already opened using the "filters" bar. When creating a new issue please select and fill the "Bug report" or "Feature request" template.`
add contributing guidelines and license 2021-06-04 10:08:11 +02:00
			`## Code contribution`

bunkerweb 1.4.0 2022-06-03 17:24:14 +02:00			The preferred way to contribute code is using [pull requests](https://github.com/bunkerity/bunkerweb/pulls). Before creating a pull request, please check if your code is related to an opened issue. If that's not the case, you should first create an issue so we can discuss about it. This procedure is here to avoid wasting your time in case the PR will be rejected. For minor changes (e.g. : typo, quick fix, ...), opening an issue might be facultative. Don't forget to edit the documentations when needed !