# Contributing to Privacy Badger

Welcome and thank you for your interest in contributing to Privacy Badger!

When interacting with us, please remember to follow [EFF's Public Projects Code of Conduct](https://www.eff.org/pages/eppcode).

* To let us know of any problems, questions or concerns, [open an issue](https://github.com/EFForg/privacybadger/issues/new), or [email us](mailto:extension-devs@eff.org)
* To report a security vulnerability, visit [SECURITY.md](/.github/SECURITY.md)
* To help translate Privacy Badger:
	- Visit our [guide to translating the Privacy Badger extension](/doc/Translation.md)
	- You can also help [translate privacybadger.org](https://github.com/EFForg/privacybadger-website#translating), Privacy Badger's homepage
* To help develop Privacy Badger:
	1. See if you are interested in any ["good first issue"](https://github.com/EFForg/privacybadger/labels/good%20first%20issue) or ["help wanted"](https://github.com/EFForg/privacybadger/labels/help%20wanted) issues
	2. If you are interested in fixing a bug or contributing a feature that's not yet on our issue tracker, please [open an issue](https://github.com/EFForg/privacybadger/issues/new) first to get feedback before commencing development
	3. To fix a broken website, review our [guide to fixing broken websites](/doc/fixing-broken-sites.md)
	4. Before contributing code, review [developer](/doc/develop.md) and [automated testing](/doc/tests.md) guides
