Skip to content

Latest commit

 

History

History
66 lines (45 loc) · 2.11 KB

CODE_OF_CONDUCT.md

File metadata and controls

66 lines (45 loc) · 2.11 KB

Code of Conduct

Nexgit should be a respectful learning and building environment. We want new contributors to feel welcome, and we want technical discussions to stay productive.

Our standard

Participants are expected to:

  • Be respectful and patient.
  • Assume good intent when possible.
  • Give constructive technical feedback.
  • Explain context for newer contributors.
  • Accept feedback professionally.
  • Keep discussions focused on the project.

Good behavior examples

  • "I think this function could be clearer if we rename it."
  • "Can you explain why this dependency is needed?"
  • "This is a good first PR. I left a few comments about Rust style."
  • "I disagree with this approach because it duplicates core logic in the desktop app."

Unacceptable behavior

Unacceptable behavior includes:

  • Harassment or threats.
  • Discriminatory language or personal attacks.
  • Sexualized language or unwanted attention.
  • Doxxing or sharing private information.
  • Repeated bad-faith disruption.
  • Mocking people for being new or asking questions.
  • Insulting contributors instead of discussing their ideas or code.

Review and discussion norms

When reviewing code:

  • Critique the code, not the person.
  • Explain why a change is requested.
  • Mark optional suggestions clearly.
  • Be especially clear and kind with first-time contributors.

When receiving review:

  • Ask questions if feedback is unclear.
  • Do not take requested changes as personal criticism.
  • It is okay to disagree, but explain why.

Reporting conduct issues

If you experience or witness unacceptable behavior, report it to the project maintainers. If the issue is sensitive, use the private email listed in SECURITY.md until the club has a dedicated conduct contact.

Maintainers should handle reports privately and promptly.

Enforcement

Maintainers may take actions including:

  • Giving a private warning.
  • Editing, hiding, or removing comments.
  • Locking discussions.
  • Temporarily restricting participation.
  • Removing a contributor from the project community.

Enforcement should be proportional and focused on keeping the project safe and productive.