Code of Conduct
Relevant source files
The following files were used as context for generating this wiki page:The Spec-Kit project adheres to the Contributor Covenant Code of Conduct to foster an open, welcoming, and harassment-free environment. This document outlines the standards of behavior expected from all contributors and maintainers, the scope of its application, and the procedures for enforcement. Participation in the project community signifies agreement to abide by these terms.
The Code of Conduct is a foundational document for community interaction, referenced by other key project guidelines such as the CONTRIBUTING.md. It ensures that all interactions, whether contributing code, reporting issues, or participating in discussions, are conducted in a professional and respectful manner.
Sources: CODE_OF_CONDUCT.md:3-9, CONTRIBUTING.md:5-6
Our Pledge and Standards
All contributors and maintainers pledge to make participation a positive experience for everyone, irrespective of personal attributes. This commitment is upheld by adhering to a set of behavioral standards.
Sources: CODE_OF_CONDUCT.md:3-9
Expected and Unacceptable Behaviors
The following table summarizes the types of behaviors that are encouraged and those that are considered unacceptable within the community.
| Behavior Type | Examples |
|---|---|
| ✅ Positive | • Using welcoming and inclusive language. • Being respectful of differing viewpoints. • Gracefully accepting constructive criticism. • Focusing on what is best for the community. • Showing empathy towards other community members. |
| ❌ Unacceptable | • Use of sexualized language or imagery and unwelcome advances. • Trolling, insulting/derogatory comments, and personal or political attacks. • Public or private harassment. • Publishing others' private information without explicit permission. • Other conduct reasonably considered inappropriate in a professional setting. |
Sources: CODE_OF_CONDUCT.md:13-31
Responsibilities of Project Maintainers
Project maintainers are responsible for clarifying and enforcing the standards of acceptable behavior. They have the right and responsibility to take corrective action in response to any instances of unacceptable behavior.
This includes the authority to:
- Remove, edit, or reject contributions that are not aligned with the Code of Conduct (e.g., comments, commits, code, wiki edits, issues).
- Temporarily or permanently ban any contributor for behaviors deemed inappropriate, threatening, offensive, or harmful.
Maintainers who do not follow or enforce the Code of Conduct in good faith may face repercussions from other members of the project's leadership.
Sources: CODE_OF_CONDUCT.md:33-40, CODE_OF_CONDUCT.md:52-54
Scope
The Code of Conduct applies in two main areas:
- Project Spaces: This includes all digital spaces managed by the project, such as the GitHub repository, issues, pull requests, and any other official communication channels. The SUPPORT.md file directs users to use GitHub issues, which are governed by this Code of Conduct.
- Public Spaces: When an individual is officially representing the project or its community. This can include using an official project e-mail, posting via an official social media account, or acting as an appointed representative at an event.
Sources: CODE_OF_CONDUCT.md:42-46, SUPPORT.md:5-6
The diagram below illustrates how various project documents guide community interaction and reporting.
This diagram shows that the Code of Conduct is central to contributions and that reporting is channeled either privately for sensitive issues (conduct, security) or publicly for project-related matters.
Sources: CODE_OF_CONDUCT.md, CONTRIBUTING.md, README.md, SUPPORT.md, SECURITY.md
Enforcement Process
Instances of abusive, harassing, or otherwise unacceptable behavior should be reported to the project team. The project provides a dedicated, private email for such reports.
The enforcement process follows these steps:
- A report of unacceptable behavior is made by a community member.
- The report is sent to the project team at
opensource@github.com. This is a private channel, similar to the one used for reporting security vulnerabilities. - The project team reviews and investigates the complaint.
- A response deemed necessary and appropriate to the circumstances is determined and enacted.
- The project team is obligated to maintain the confidentiality of the reporter.
Sources: CODE_OF_CONDUCT.md:48-51, SECURITY.md:15
The following flowchart visualizes the enforcement workflow.
This flowchart shows the process from an incident report to the potential corrective actions, emphasizing the confidentiality of the reporter.
Sources: CODE_OF_CONDUCT.md:35-40, 48-51
Attribution
This Code of Conduct is adapted from the Contributor Covenant, version 1.4.
Sources: CODE_OF_CONDUCT.md:56-59