Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
59 lines (44 loc) · 2.24 KB

CODE_OF_CONDUCT.md

File metadata and controls

59 lines (44 loc) · 2.24 KB
Raw

Code of conduct

BattleCommand Forge is a small, solo-maintained open-source project. We keep the conduct rules short — practical, not legalistic.

Core expectation

Be kind. Treat fellow contributors, users, and maintainers with respect in issues, pull requests, code reviews, and any other project-related discussion.

This applies to everyone who participates in the project space, whether they're a first-time contributor asking a basic question, a long-time user filing a bug, or a maintainer reviewing your PR.

In practice

  • Assume good faith. People asking questions aren't testing you; people pushing back on your PR aren't attacking you.
  • Be concrete and constructive. "This doesn't work" isn't helpful; "This errors with X when I run Y" is.
  • Skip insults, personal attacks, and derogatory remarks about individuals or groups. There's no place for them here.
  • Respect "no." If a maintainer declines a feature proposal or closes an issue, that's the answer — re-opening the same discussion repeatedly isn't going to change the outcome.
  • Keep the conversation about the work. Off-topic tangents (politics, unrelated disputes) don't belong in the issue tracker.

If something goes wrong

If someone's behaviour in the project space is making you uncomfortable or seems out of line, contact the maintainer directly through a GitHub DM or the email on the profile page. Include links to the specific comments or exchanges.

Reports are handled privately. The maintainer will review, decide whether action is warranted, and communicate the outcome to the reporter. Possible actions range from a private conversation to blocking a user from the project.

Scope

This applies wherever the project's community gathers:

  • The GitHub repository (issues, pull requests, discussions, code reviews, commit messages).
  • Any future official project communication channel.

It does not apply to unrelated interactions between contributors outside these spaces.

Why short?

The Contributor Covenant and similar documents exist and work well for many projects. BCF's scale doesn't need one — if we grow to a point where more detailed rules help, this page will grow with it. For now: be kind, and handle the rare exception through direct conversation.