Code of Conduct

Our Pledge

We expect contributors, maintainers, users, and reviewers to work together respectfully. The project should remain useful for people improving MDPR presentation workflows, regardless of experience level, background, identity, or communication style.

Our Standards

Expected behavior includes:

• discussing technical disagreements with evidence and a path to resolution
• keeping issues and pull requests focused on the repository's goals
• giving credit for prior work, references, and reproduced findings
• reporting security vulnerabilities through SECURITY.md instead of public issues
• accepting maintainer decisions after concerns have been heard

Unacceptable behavior includes:

• harassment, threats, insults, or sustained personal attacks
• publishing private information without explicit permission
• derailing issues or pull requests after a maintainer asks for focus
• knowingly submitting copied, malicious, or misleading artifacts
• using project spaces for spam, impersonation, or unrelated promotion

Scope

This code applies in repository issues, pull requests, discussions, review comments, release coordination, and any project-managed communication channel. It also applies when someone represents the project in a public technical context.

Enforcement

Maintainers may remove comments, edit or close issues, decline pull requests, temporarily limit participation, or block users when behavior harms the project. Enforcement should be proportional, documented when practical, and focused on restoring useful collaboration.

For conduct concerns that require privacy, ask a maintainer for a private contact channel without posting sensitive details publicly. Security vulnerabilities must follow the reporting path in SECURITY.md.