Skip to content

Latest commit

 

History

History
38 lines (23 loc) · 2.04 KB

File metadata and controls

38 lines (23 loc) · 2.04 KB

Code of Conduct

We want the Ashlr Stack community to be a place where anyone can contribute — regardless of experience level, background, or identity. This document sets expectations for how we treat each other.

Expectations

Be respectful. Assume good faith. Disagreements are fine; personal attacks are not. Keep feedback focused on the code, idea, or decision — not the person.

Examples of behavior we want:

  • Welcoming newcomers and helping them onboard.
  • Giving and receiving constructive feedback gracefully.
  • Acknowledging mistakes, apologizing, and moving forward.
  • Prioritizing what's best for the community over what's best for you individually.

Examples of behavior we will not tolerate:

  • Harassment, discrimination, or slurs of any kind.
  • Personal attacks, intimidation, or threats.
  • Publishing someone's private information without their consent.
  • Sustained disruption of discussions, issues, or PRs.
  • Any other conduct that a reasonable person would consider inappropriate in a professional setting.

Scope

This applies to all community spaces connected to Ashlr Stack — GitHub issues, pull requests, discussions, and any official chat or event. It also applies when you are representing the project in public (e.g., using a project email address or posting as the project's official account).

Enforcement

Report concerns through GitHub Security Advisories with "conduct" in the title, or by emailing the maintainers if you have their direct contact.

Reports will be handled confidentially. We will acknowledge receipt within 3 business days and respond with a decision within 14 days. Depending on severity, responses range from a private warning to a permanent ban from all project spaces.

The project maintainers have final say on enforcement and may remove, edit, or reject contributions, comments, issues, or PRs that violate this policy.

Questions

If something in this policy is unclear, open a discussion. We'd rather revise the wording than have anyone guess.