Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
66 lines (43 loc) · 2.44 KB

CODE_OF_CONDUCT.md

File metadata and controls

66 lines (43 loc) · 2.44 KB

The Go Engineer Code of Conduct

Our Pledge

The Go Engineer community exists to help people learn Go and backend engineering with rigor, clarity, and respect.

We pledge to make project spaces welcoming for learners, contributors, maintainers, and reviewers regardless of background, experience level, identity, location, or ability.

Expected Behavior

Participants are expected to:

  • use welcoming and inclusive language
  • assume good intent while still being clear about technical problems
  • give feedback on the work, not on the person
  • accept correction gracefully
  • keep discussions focused on learning, maintainability, and project quality
  • respect maintainer decisions about scope, architecture, licensing, and release process

Unacceptable Behavior

Unacceptable behavior includes:

  • harassment, intimidation, threats, or personal attacks
  • discriminatory language, jokes, or imagery
  • sexualized language or unwanted attention
  • publishing private information without permission
  • sustained disruption of issues, pull requests, discussions, or reviews
  • bad-faith participation, including repeated scope derailment after maintainer guidance

Scope

This code applies to all project-managed spaces, including GitHub issues, pull requests, discussions, reviews, documentation, and official project communication channels.

Behavior outside project spaces may affect participation when it creates a safety, trust, or maintainability risk for the project community.

Reporting

Report Code of Conduct concerns privately by using the maintainer contact path listed in SECURITY.md, or by emailing raselhossen052@gmail.com.

Include:

  • what happened
  • where it happened
  • who was involved
  • links, screenshots, or timestamps when available
  • whether immediate action is needed

Reports will be handled with as much confidentiality as practical. Maintainers may ask for more information before taking action.

Enforcement

Maintainers may take any action they consider appropriate, including:

  • clarification or correction
  • warning
  • comment deletion
  • temporary restriction from project spaces
  • permanent ban from project spaces
  • escalation to GitHub or platform moderation when needed

Enforcement decisions are based on impact, severity, history, and risk to the project community.

Attribution

This document is adapted from common open source community conduct patterns and tailored for The Go Engineer.