23 lines
1.3 KiB
Markdown
23 lines
1.3 KiB
Markdown
# Contributing to Privacy Badger
|
|
|
|
Welcome dear contributor! There are many ways to help Privacy Badger:
|
|
|
|
* Did we break a site? We want to fix it,
|
|
so we wrote a [guide to fixing broken sites](/doc/fixing-broken-sites.md).
|
|
* Want to help translate Privacy Badger? Please see our [guide to translating Privacy Badger](/doc/Translation.md).
|
|
* To review issues we would like help with, visit our
|
|
["good first issue"](https://github.com/EFForg/privacybadger/labels/good%20first%20issue)
|
|
and
|
|
["help wanted"](https://github.com/EFForg/privacybadger/labels/help%20wanted)
|
|
labels.
|
|
* When making changes to Privacy Badger's code, please consult our [developer](/doc/develop.md) and [automated testing](/doc/tests.md) guides.
|
|
* Security vulnerabilities can be reported privately to
|
|
[vulnerabilities@eff.org](mailto:vulnerabilities@eff.org). Please see our
|
|
[Security Vulnerability Disclosure Program](https://www.eff.org/security)
|
|
for the GPG key and more information.
|
|
|
|
When interacting with us, please remember to follow [EFF's Public Projects Code of Conduct](https://www.eff.org/pages/eppcode).
|
|
|
|
If you find something confusing or frustrating, please [let us know](mailto:extension-devs@eff.org)! We believe in making Privacy Badger better by making it easier for you to contribute.
|
|
|
|
Thank you!
|