Code of Conduct

Code of Conduct

SpecRoute is a vendor-neutral, community-curated project. Participation should be practical, respectful, and focused on making the shared templates and workflows better for everyone who uses them.

Full policy: CODE_OF_CONDUCT.md.

Standards

Behaviors that contribute to a constructive community:

• Welcoming and inclusive language.
• Respect for different viewpoints, experiences, and tool preferences.
• Giving and receiving technical feedback with care and specificity.
• Keeping discussions focused on the work, its tradeoffs, and its impact.
• Accepting responsibility, correcting mistakes, and learning from them.

Unacceptable behaviors:

• Harassment, intimidation, threats, personal attacks.
• Discriminatory language or conduct.
• Sexualized language or imagery in project spaces.
• Publishing another person's private information without permission.
• Trolling, sustained disruption, bad-faith participation.
• Any conduct that would reasonably make participation unsafe or unwelcome.

Scope

Applies in all SpecRoute project spaces — issues, pull requests, discussions, reviews, community channels, and any public setting where someone is representing the project.

Contributions must not include proprietary material, private customer data, secrets, or content that violates the dignity or safety of others. See Sanitization.

Enforcement

Maintainers may take appropriate action in response to behavior they determine to be harmful, inappropriate, threatening, or disruptive. Actions may include:

• Private clarification or warning.
• Requesting edits to comments, issues, PRs, or other contributions.
• Temporarily limiting participation.
• Removing comments, contributions, or other content.
• Permanent removal from project spaces.

Maintainers apply this policy consistently and proportionately, with attention to the safety and dignity of affected people.

Reporting

Report violations privately to the project maintainers:

• Email: TODO add conduct contact (see MAINTAINERS.md)
• GitHub: contact a maintainer directly or use the repository's private reporting channel.

Reports should include:

• What happened
• Where
• When
• Any relevant links, screenshots, or context
• Whether you need immediate confidentiality or safety considerations

Maintainers respect the privacy and safety of reporters and affected people while reviewing.

Attribution

This policy is adapted from common open-source community standards, including the Contributor Covenant, with wording tailored to SpecRoute's documentation-focused contribution model.

See also

• Contributing — contributor workflow
• Maintainers — who enforces this and how to reach them
• Security — separate channel for security vulnerabilities