mirror of
https://github.com/pi-hole/pi-hole
synced 2024-11-18 06:08:21 +00:00
7e0aa822b6
* Update README.md * Update index.php * Update basic-install.sh * Update piholeCheckout.sh * Update update.sh * Update CONTRIBUTING.md * Update the Pi-hole brand tip in CONTRIBUTING.md Use a better formulation. * Update README.md 2
40 lines
2.4 KiB
Markdown
40 lines
2.4 KiB
Markdown
_This template was created based on the work of [`udemy-dl`](https://github.com/nishad/udemy-dl/blob/master/LICENSE)._
|
|
|
|
# Contributors Guide
|
|
|
|
Please read and understand the contribution guide before creating an issue or pull request.
|
|
|
|
## Etiquette
|
|
|
|
- Our goal for Pi-hole is **stability before features**. This means we focus on squashing critical bugs before adding new features. Often, we can do both in tandem, but bugs will take priority over a new feature.
|
|
- Pi-hole is open source and [powered by donations](https://pi-hole.net/donate/), and as such, we give our **free time** to build, maintain, and **provide user support** for this project. It would be extremely unfair for us to suffer abuse or anger for our hard work, so please take a moment to consider that.
|
|
- Please be considerate towards the developers and other users when raising issues or presenting pull requests.
|
|
- Respect our decision(s), and do not be upset or abusive if your submission is not used.
|
|
|
|
## Viability
|
|
|
|
When requesting or submitting new features, first consider whether it might be useful to others. Open source projects are used by many people, who may have entirely different needs to your own. Think about whether or not your feature is likely to be used by other users of the project.
|
|
|
|
## Procedure
|
|
|
|
**Before filing an issue:**
|
|
|
|
- Attempt to replicate and **document** the problem, to ensure that it wasn't a coincidental incident.
|
|
- Check to make sure your feature suggestion isn't already present within the project.
|
|
- Check the pull requests tab to ensure that the bug doesn't have a fix in progress.
|
|
- Check the pull requests tab to ensure that the feature isn't already in progress.
|
|
|
|
**Before submitting a pull request:**
|
|
|
|
- Check the codebase to ensure that your feature doesn't already exist.
|
|
- Check the pull requests to ensure that another person hasn't already submitted the feature or fix.
|
|
|
|
## Technical Requirements
|
|
|
|
- Submit Pull Requests to the **development branch only**.
|
|
- Before Submitting your Pull Request, merge `development` with your new branch and fix any conflicts. (Make sure you don't break anything in development!)
|
|
- Please use the [Google Style Guide for Shell](https://google.github.io/styleguide/shell.xml) for your code submission styles.
|
|
- Commit Unix line endings.
|
|
- Please use the Pi-hole brand: **Pi-hole** (Take a special look at the capitalized 'P' and a low 'h' with a hyphen)
|
|
- (Optional fun) keep to the theme of Star Trek/black holes/gravity.
|