Change blacklist and whitelist terminology

yubiuser · June 10, 2020, 8:21pm

There is already one, but it might need some more support.

github.com/pi-hole/pi-hole

Change white/blacklist to allow/blocklist

pi-hole:development ← StefanHolmes:master

opened 06:54PM - 07 Jun 20 UTC

StefanHolmes

+114 -115

**By submitting this pull request, I confirm the following:** *please fill any… appropriate checkboxes, e.g: [X]* - [X] I have read and understood the [contributors guide](https://github.com/pi-hole/pi-hole/blob/master/CONTRIBUTING.md), as well as this entire template. - [X] I have made only one major change in my proposed changes. - [ ] I have commented my proposed changes within the code. - [ ] I have tested my proposed changes, and have included unit tests where possible. - [X] I am willing to help maintain this change if there are issues with it later. - [X] I give this submission freely and claim no ownership. - [X] It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) - [ ] I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) Please make sure you [Sign Off](https://github.com/pi-hole/pi-hole/wiki/How-to-signoff-your-commits.) all commits. Pi-hole enforces the [DCO](https://github.com/pi-hole/pi-hole/wiki/Contributing-to-the-project). --- **What does this PR aim to accomplish?:** *A detailed description, screenshots (if necessary), as well as links to any relevant GitHub issues* A change in language to eliminate any potential negative connotation caused by use of 'blacklist' versus 'whitelist'. **How does this PR accomplish the above?:** *A detailed description (such as a changelog) and screenshots (if necessary) of the implemented fix* Hand review all instances and replacing with 'allowlist' and 'blocklist'. **What documentation changes (if any) are needed to support this PR?:** *A detailed list of any necessary changes* Potentially just an acknowledgement of the change. --- * You must follow the template instructions. Failure to do so will result in your pull request being closed. * Please respect that Pi-hole is developed by volunteers, who can only reply in their spare time.