We want contributing here to be worth someone's time regardless of who they are. Everyone taking part in this project — in issues, pull requests, discussions, reviews, and any other project space — is expected to treat other people with respect.
This applies to maintainers exactly as much as to first-time contributors. Seniority in the project is not a licence to be dismissive.
- Assume the other person is trying to help. Most friction in open source is a misread tone, not malice.
- Critique the code, the design, or the claim — not the person who wrote it. "This breaks X because Y" is useful; "this is amateur work" is not.
- Accept that maintainers may decline a contribution. A "no" with a reason is a legitimate outcome, not an insult, and the reason is the part worth arguing with.
- Accept review feedback on your own work in the same spirit.
- Be patient with people who are new to the codebase. It is a large project with non-obvious rules; the fix for someone not knowing them is to point at the documentation, not to sigh at them.
- Respect a decision once it is made and recorded, even one you argued against. Reopening a settled decision needs new information, not repetition.
- Harassment of any kind, public or private. This includes sustained disruption of discussions, deliberate intimidation, and unwelcome attention after being asked to stop.
- Insults, demeaning comments, or personal attacks — including ones dressed up as technical criticism.
- Discriminatory language or jokes, including about race, ethnicity, national origin, immigration status, gender, gender identity or expression, sexual orientation, disability, physical appearance, body size, age, caste, religion, or lack thereof.
- Sexualized language or imagery, and unwelcome sexual attention.
- Publishing someone's private information without their explicit permission.
- Deliberately submitting malicious code, a knowingly dishonest verification claim, or a "fix" designed to hide a defect. In a project whose entire value rests on validation claims being true, this is the most serious thing on this list.
- Threats or advocacy of harm against anyone.
If you experience or witness behavior that breaks this code, report it to the maintainers privately.
Email support@databounty.io with CONDUCT in the subject line. Reports go to the DataBounty
maintainers.
If you would rather not use email, GitHub's private vulnerability reporting on this repository's Security tab also reaches the maintainers and nobody else. It is built for security issues, so say up front that your report is a conduct matter, not a vulnerability.
Reports will be reviewed and investigated. We will respect the privacy of whoever reports something, and we will not retaliate against someone for reporting in good faith. Do not use this process to punish someone for disagreeing with you technically.
Maintainers decide what response fits, and are responsible for applying this consistently. Depending on severity and whether it has happened before, that may be:
- A private word — an explanation of what was wrong and why, with no public record.
- A public correction — where the behavior happened in public and left a misleading impression.
- A temporary ban from project spaces.
- A permanent ban, for sustained behavior, harassment, or anything malicious.
Maintainers may also edit, hide, or delete comments, commits, code, and issues that break this code, and will say that they did so.
This applies in all project spaces — this repository, its issues, pull requests, discussions, and reviews — and when someone is representing the project in public.
It does not extend to unrelated conduct elsewhere, with one exception: behavior outside the project that credibly threatens the safety of people in it is in scope.
This code of conduct was written for this project. If you would prefer the widely-recognized Contributor Covenant instead, adopting it verbatim in place of this file is fine — it covers the same ground in more standardized language.