Code of Conduct

In short

Be sharp, be direct, be useful. Don't be a jerk.

In detail

This project is opinionated. We argue about UX, code, naming, and taste. We don't argue about people.

Yes

• Sharp critique of code, designs, or specs. Be specific. Cite the file, the line, the rule.
• Pushback on a maintainer decision if you have a better proposal.
• Disagreement, articulated.
• High standards.

No

• Personal attacks. The argument is about the work, never about the person making it.
• Discriminatory language of any kind.
• Harassment, public or private.
• Trolling.
• Dismissing newcomers for not knowing what regulars know.
• Posting other people's private information.
• Sustained derailing.

If something is off

Email the maintainer directly: laith.aljunaidy.laith@gmail.com. Brief is fine — what happened, where, when. Action will be taken proportionate to the impact: a private note, a public correction, a temporary block, a permanent ban — in roughly that order, depending on severity and pattern.

Scope

This applies in every space the project occupies: GitHub issues, pull requests, discussions, the wiki, any community channels (Discord, etc.), and any in-person conversations about the project.

Source

This is intentionally short. Long codes of conduct often become harder to enforce because they cover more edge cases ambiguously. The intent is captured in the first line: be sharp, be direct, be useful. Don't be a jerk.