Code of Conduct#

The standard#

Argue about the specification as hard as you like. Never about the person.

Technical disagreement is the mechanism by which a specification gets good. A proposal being wrong is a normal, expected, useful outcome — saying so directly is not rudeness, and taking it personally is not a violation. What is out of bounds is anything aimed at the human rather than the argument.

Expected#

• Critique the design, the wording, the tradeoff, the test coverage.
• Say "this is wrong, and here is the case it breaks on."
• Assume the other person read the spec and is arguing in good faith.
• Accept that the editors will sometimes decide against you, in writing, and

  that the written reason is the point.

Not accepted#

• Personal attacks, insults, or demeaning comments about a person or group.
• Harassment of any kind, publicly or privately.
• Discriminatory language or conduct regarding gender, gender identity or

  expression, sexual orientation, disability, physical appearance, body size, race, ethnicity, age, religion, or nationality.

• Publishing others' private information without explicit permission.
• Sustained disruption of discussion, or relitigating a decided HXEP without

  new information.

Scope#

Applies in the issue tracker, pull requests, HXEP discussions, and any space where someone is representing the project.

Enforcement#

Report to conduct@harnessxml.com. Reports are handled confidentially by the steward (VisML). Response is proportionate: usually a private word, and where necessary editing or removing content, or a temporary or permanent ban from project spaces.

If the report concerns the steward, and you would rather not raise it with them, say so in the report — an uninvolved third party will be asked to handle it.

Attribution#

Adapted in spirit from the Contributor Covenant, deliberately shortened. A code of conduct nobody reads protects nobody.