FogHTTP should be a respectful, focused, and technically honest project space. We want contributors and users to be able to discuss bugs, design trade-offs, security concerns, performance results, and roadmap decisions without personal hostility or gatekeeping.
Everyone participating in the project is expected to help keep that space open, focused, and professional.
FogHTTP values engineers who are genuinely interested in building, debugging, measuring, and improving software. Project spaces are for engineering work: bugs, implementation details, API design, security, performance, tests, documentation, releases, and roadmap decisions.
AI tools may be used as engineering assistants, but they are not participants and they do not carry responsibility. The person submitting or arguing for a change owns the code, the reasoning, the tests, and the consequences.
Contributors who cannot write, reason about, debug, and maintain code without AI are outside the engineering standard of this project.
Political, religious, ideological, culture-war, or other unrelated social debates are out of scope for FogHTTP project spaces. Those conversations belong elsewhere, even when participants feel strongly about them.
Technical discussion may be direct, blunt, and demanding. Maintainers and contributors may challenge designs, reject patches, point out weak tests, argue about resource models, security boundaries, performance claims, API contracts, and failure modes. That directness is acceptable when it stays tied to the engineering task and technical implementation.
Direct technical criticism is not a license for harassment, discrimination, humiliation, threats, or personal attacks. The boundary is simple: be hard on the problem, not on the person.
Examples of behavior that helps the project:
- being respectful of different experience levels and backgrounds
- giving and receiving technical feedback in good faith
- focusing criticism on code, design, behavior, tests, documentation, or process rather than on people
- asking clarifying questions before assuming bad intent
- acknowledging mistakes and correcting them
- keeping discussions relevant to the project
- being careful with security-sensitive details
- giving credit for ideas, reports, and contributions
Strong technical disagreement is allowed. Personal attacks are not.
Examples of unacceptable behavior include:
- harassment, intimidation, stalking, or sustained disruption
- discriminatory language or behavior
- sexualized language, imagery, or attention in project spaces
- insults, personal attacks, or demeaning comments
- publishing private contact information without permission
- sharing private security reports or exploit details before coordinated disclosure is complete
- bringing political, religious, ideological, or other unrelated arguments into project spaces
- deliberately derailing issues, pull requests, or maintainer decisions
- other conduct that a reasonable maintainer would consider inappropriate in a professional open source project
This Code of Conduct applies in all FogHTTP project spaces, including:
- GitHub issues, pull requests, discussions, and reviews
- security reporting conversations
- release, documentation, and roadmap discussions
- any other public or private space where someone represents the project
It also applies when project-related behavior outside these spaces directly affects the safety or participation of project members.
Project maintainers are responsible for clarifying standards and responding to behavior that violates this Code of Conduct.
Maintainers may take action such as:
- asking someone to stop specific behavior
- editing or deleting comments
- closing, locking, or limiting a discussion
- declining contributions
- temporarily or permanently blocking a participant from project spaces
- escalating to platform moderation when needed
Enforcement decisions should be proportionate to the impact and pattern of the behavior.
To report a Code of Conduct concern, use the GitHub project channels:
- maintainer: GefMar
- public, non-sensitive community concerns: GitHub Discussions
Do not publish private contact information, screenshots with personal data, private security details, or other sensitive material in a public discussion. If the report requires private handling, use GitHub Discussions only to request a private coordination path and keep the public message minimal.
When reporting in a suitable channel, please include:
- what happened
- where it happened
- who was involved
- any relevant links, screenshots, or timestamps
- whether there is an immediate safety or privacy concern
Reports will be handled as privately as practical. The maintainer may need to share limited information to investigate, respond, or comply with platform rules.
This Code of Conduct is meant to protect healthy collaboration, not to prevent firm technical review. Maintainers may still close issues, reject pull requests, request tests, push back on scope, or disagree with a proposal when that is the right engineering decision for FogHTTP.
The project works best when people can be direct, precise, and serious about engineering without turning technical disagreement into personal conflict or unrelated social debate.