Code of Conduct

Our commitment

Codex How To is an engineering learning community. We welcome people of every experience level, identity, background, and point of view.

Project maintainers and contributors commit to making participation professional, respectful, and free from harassment. This applies when opening issues or pull requests, joining discussions, reviewing experiments, and representing the project in public.

Expected behavior

• Discuss ideas, evidence, and tradeoffs without attacking people.
• Assume good intent while still asking for reproducible evidence.
• Give specific, constructive feedback that helps someone improve the work.
• Respect privacy, attribution, licenses, and requests to stop an interaction.
• Welcome corrections and results that disagree with the repository's current guidance.
• Keep examples safe for a public learning repository: do not share secrets, private data, exploit targets, or harmful instructions.

Unacceptable behavior

• Harassment, threats, discrimination, stalking, or unwanted sexual attention.
• Insults, personal attacks, trolling, or sustained disruption.
• Publishing another person's private information without permission.
• Plagiarism, fabricated measurements, coordinated voting, spam, or deceptive promotion.
• Retaliation against someone who reports a concern in good faith.

Reporting

For routine content or technical concerns, use the repository's issue or discussion templates.

For sensitive conduct concerns, contact the maintainer privately at nguyenvantamdk2@gmail.com. Include links, dates, and relevant context when it is safe to do so. Reports will be handled as confidentially as practical. Do not post sensitive personal information in a public issue.

If the maintainer is involved in a concern or the behavior violates GitHub's policies, use GitHub's abuse-reporting process.

Enforcement

Maintainers may edit or remove content, issue a private warning, limit participation, temporarily suspend participation, or permanently ban a participant. The response will be proportional to the behavior, its impact, and whether it continues after a warning.

Good-faith disagreement, critical review, and negative experimental results are not conduct violations. Enforcement decisions should protect people and productive technical discussion, not shield the project from criticism.

Scope

This policy applies in all project-managed spaces and when a person officially represents Codex How To. Conduct outside those spaces may be considered when it creates a clear safety risk for project participants.