This repository is small: one maintainer, and contributors who are mostly agent sessions. That is not a reason to skip a code of conduct; it is the reason this one is short. It says how people are expected to treat each other in this repository's spaces, what crosses the line, and what a report about it will do.
Conduct governs behavior in this repository's spaces: issues, pull requests, code review, and commit messages. Two neighboring subjects are deliberately out of scope. How work is claimed, priced and settled is CONTRIBUTING.md's subject. How accounts are moderated inside the running ledger is the Rules page's subject — served in-product at the deployed instance, https://overflow.nitjsefni.eu — which also defines the moderation ladder, audit → warn → recalibrate → ban, that account-level enforcement follows. Where another document owns a question, it answers it; this one is about how people treat each other, and it does not restate what they already say.
Work here is often done by agent sessions. The account that acts owns the conduct: how an agent behaves in these spaces is the conduct of whoever runs it.
- Collaborate in good faith. Argue from the record — issues, commits, review threads — because everything here is meant to be reproducible from GitHub's own data.
- Criticize work, not people. A wrong patch is a wrong patch; say so plainly and leave it there.
- Be honest about what you have verified. CONTRIBUTING.md requires pasted evidence for claims; the conduct point is that a fabricated or unverified result is a conduct problem, not a style preference.
- Respect the claim system. Do not work an issue someone else has claimed, and do not interfere with work in progress. The mechanics live in CONTRIBUTING.md; the conduct point is simply not taking other people's work.
A stranger reading this list should be able to predict what gets a report upheld. These do:
- Harassment, including continued unwanted contact after a request to stop.
- Insults and personal attacks.
- Trolling: participating to provoke rather than to work.
- Doxxing: publishing anyone's private information without their consent — contact details, an address, anything they have kept private.
- Sexualized language or imagery, and unwelcome attention of any kind.
- Spam.
- Deliberately gaming the ledger. The Rules page's Moderation section defines the ladder account-level abuse is handled with — audit → warn → recalibrate → ban, with supporting evidence at every step; the conduct point is that doing it on purpose is a conduct problem here, whatever the ledger scores.
Report conduct problems by opening an issue on this repository's public tracker: https://github.com/Nitjsefnie/Overflow/issues.
Report security vulnerabilities through GitHub private vulnerability reporting, as described in SECURITY.md.
These are the two reporting channels that exist. Do not invent an address, a form, or a private channel in anyone's name.
For conduct reports on the public tracker, keep the opening report usable:
- Describe the behavior and link the thread where it happened; the record is the evidence, and you do not need to reprint all of it.
- Keep sensitive third-party details out of the opening report. Quote what is needed to identify the behavior and link to the rest.
Conduct reports may be about anyone, and the maintainer's own conduct is in scope: a conduct report about the maintainer is decided, like every conduct report, by the maintainer.
The repository maintainer enforces this document personally. The powers are the real ones: responding to reports, editing or removing content through GitHub's moderation tools, blocking accounts from the repository, and — for conduct tied to ledger accounts — the moderation ladder the Rules page defines, which requires supporting evidence at every step.
There is no committee, no response-time promise, and no appeal process. This is a one-maintainer project: expect a human reply, not a triage pipeline.
If enforcement touched a settled credit and you believe the settlement itself was wrong, dispute it through the corrections process the Rules page describes — though only the settlement's creditor or the sponsor can ask there. That process owns settlement disputes; this document does not create a second one.