Code of Conduct
Relevant source files
The following files were used as context for generating this wiki page:
The OpenHWP project adopts a formal Code of Conduct to ensure a harassment-free and inclusive experience for all participants. This policy applies to all project spaces, including the repository, issue trackers, and official communication channels. By participating in this project, contributors agree to abide by these established standards.
Sources: CODE_OF_CONDUCT.md:3-12, CONTRIBUTING.md:5
Community Pledge and Scope
The project leadership pledges to foster an open, welcoming, and healthy community regardless of individual background, identity, or level of experience. This commitment extends beyond technical contributions to include any instance where an individual represents the community in public spaces, such as using official email addresses or social media accounts.
Sources: CODE_OF_CONDUCT.md:5-15, CODE_OF_CONDUCT.md:58-65
Behavioral Standards
The following table summarizes the behavioral expectations for all community members:
| Category | Examples of Behavior |
|---|---|
| Positive Behavior | Demonstrating empathy, being respectful of differing opinions, accepting constructive feedback, and focusing on community well-being. |
| Unacceptable Behavior | Sexualized language/imagery, trolling, personal or political attacks, public or private harassment, and doxxing. |
Sources: CODE_OF_CONDUCT.md:18-41
Enforcement Process
Community leaders are responsible for maintaining these standards. They possess the authority to moderate contributions (comments, commits, code, wiki edits, and issues) that do not align with the project's values.
Reporting Mechanisms
Reports of unacceptable behavior are handled through specific channels depending on the nature of the incident:
- General Conduct Violations: Reports should be sent to security@pleaseai.dev.
- Security Vulnerabilities: These must NOT be reported via public issues. Instead, use GitHub's private vulnerability reporting feature or email the security address directly.
Sources: CODE_OF_CONDUCT.md:68-71, SECURITY.md:14-23, CONTRIBUTING.md:73-75
Incident Handling Flow
The following diagram illustrates the lifecycle of a conduct or security report within the OpenHWP community:
The enforcement process emphasizes prompt and fair investigation while protecting the privacy of the reporter.
Sources: CODE_OF_CONDUCT.md:71-76, SECURITY.md:26-30
Enforcement Guidelines and Consequences
Community leaders follow a tiered ladder of consequences for violations, inspired by the Mozilla enforcement ladder.
| Tier | Severity/Impact | Consequence |
|---|---|---|
| 1. Correction | Unprofessional or unwelcome language. | Private written warning and potential request for public apology. |
| 2. Warning | Single incident or series of actions. | Warning with specified period of no-interaction with involved parties. |
| 3. Temporary Ban | Serious or sustained violation. | Temporary ban from all community interaction and communication. |
| 4. Permanent Ban | Pattern of violation or sustained harassment. | Permanent ban from all public interaction within the community. |
Sources: CODE_OF_CONDUCT.md:79-119
Implementation in Workflow
The Code of Conduct is integrated into the daily development and contribution workflow. For instance, external pull requests (PRs) are subject to specific review processes to maintain project quality and conduct standards.
Contributors must use English for all documentation, code comments, and commit messages, and follow Conventional Commits (e.g., feat(scope): subject) to ensure automated versioning and clarity.
Sources: CONTRIBUTING.md:5-7, CONTRIBUTING.md:33-40, CONTRIBUTING.md:43-52
Summary
The OpenHWP Code of Conduct serves as the foundational social contract for the project. By defining clear behavioral standards, reporting paths for both conduct and security, and a transparent enforcement ladder, the project ensures that its technical goal of providing an open-source HWP/HWPX viewer is supported by a professional and inclusive environment.
Sources: CODE_OF_CONDUCT.md:121-125, README.en.md:5-9