engineering-quality welcomes technical disagreement and expects contributors to keep it evidence-based, specific, and respectful.
Contributors should:
- discuss ideas, code, and observable behavior rather than attacking people;
- assume neither expertise nor bad intent from identity, background, or communication style;
- give concrete technical reasons for criticism and distinguish requirements from preferences;
- respect privacy, confidentiality, and coordinated vulnerability disclosure;
- stop repeated unwanted personal contact or disruptive behavior when asked;
- keep discussions relevant enough for maintainers and contributors to make progress.
Harassment, threats, discriminatory abuse, sexualized harassment, doxxing, deliberate disclosure of private information, and sustained personal attacks are not acceptable.
This policy applies to project-controlled spaces, including issues, pull requests, reviews, discussions, and project-related interactions where a participant is representing the project.
Maintainers may edit, hide, lock, or remove content; close contributions; restrict participation; or report serious abuse to the hosting platform when necessary to protect contributors and the project.
For conduct concerns, contact the repository maintainers privately when possible. Do not use a public issue to disclose another person's private information.
Enforcement decisions should be based on documented behavior in project scope, not disagreement with a contributor's technical position.
Strong review is welcome. A finding should explain the failure mode, affected contract, or evidence gap. Disagreement about implementation style alone is not misconduct and is not grounds for moderation.