Skip to main content

​
Our Pledge

We as members, contributors, and leaders pledge to make participation in the Proxmox VE Helper Scripts community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
This Code of Conduct is adapted from the Contributor Covenant, version 2.0.

​
Our Standards

​
Positive Behavior

Examples of behavior that contributes to a positive environment for our community include:

Empathy and Kindness

Demonstrating empathy and kindness toward other people, especially those new to the project or technology.

Respect

Being respectful of differing opinions, viewpoints, and experiences. Not everyone has the same background.

Constructive Feedback

Giving and gracefully accepting constructive feedback. Focus on improvement, not criticism.

Responsibility

Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience.

Community Focus

Focusing on what is best not just for us as individuals, but for the overall community.

Collaboration

Working together effectively and supporting fellow contributors with patience and understanding.

​
Unacceptable Behavior

Examples of unacceptable behavior include:
  • The use of sexualized language or imagery, and sexual attention or advances of any kind
  • Trolling, insulting or derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others’ private information, such as a physical or email address, without their explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting
  • Deliberate intimidation or stalking (online or in person)
  • Sustained disruption of community discussions or events
  • Advocating for, or encouraging, any of the above behavior

​
Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

​
Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.

​
Where This Applies

  • GitHub repositories (issues, pull requests, discussions)
  • Discord server
  • Email communications with maintainers
  • Community events (virtual or in-person)
  • Social media when representing the project
  • Any other official community channels

​
Reporting Violations

​
How to Report

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement.
Join our Discord server and send a direct message to a maintainer or moderator.
Look for users with “Maintainer” or “Moderator” roles for fastest response.
Privacy and Confidentiality: All reports will be handled with discretion. We will protect the identity of reporters to the extent possible.

​
What to Include in a Report

When reporting a violation, please provide:
  • Your contact information - So we can follow up with you
  • Description of the incident - What happened, when, and where
  • Names/usernames involved - Who was involved in the incident
  • Evidence - Links, screenshots, or other documentation
  • Impact - How this affected you or the community
  • Desired outcome - What resolution you’re hoping for (optional)

​
Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

​
1. Correction

1

Community Impact

Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
2

Consequence

A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

​
2. Warning

1

Community Impact

A violation through a single incident or series of actions.
2

Consequence

A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

​
3. Temporary Ban

1

Community Impact

A serious violation of community standards, including sustained inappropriate behavior.
2

Consequence

A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

​
4. Permanent Ban

1

Community Impact

Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
2

Consequence

A permanent ban from any sort of public interaction within the community.

​
Response Process

1

Acknowledgment (within 7 days)

We will review and acknowledge your report within 7 business days.
2

Investigation

The maintainers will:
  • Review the report and any evidence provided
  • Speak with involved parties if necessary
  • Assess the severity and impact of the incident
  • Determine appropriate action based on enforcement guidelines
3

Decision and Action

Depending on severity:
  • Minor issues: Private warning and guidance
  • Moderate issues: Public warning, temporary restrictions
  • Severe issues: Temporary or permanent ban
The reporter will be informed of the decision.
4

Appeals

Those affected by enforcement actions may appeal the decision by contacting community leaders via email within 14 days of notification.

​
Community Expectations

​
For All Community Members

Welcome newcomers and help them get started. Remember that everyone was new once.
  • Answer questions patiently
  • Point to relevant documentation
  • Encourage first-time contributors
  • Celebrate community successes
Treat everyone with respect and consideration.
  • Assume good intentions
  • Be patient with different skill levels
  • Value diverse perspectives
  • Disagree constructively
Work together to build great things.
  • Share knowledge freely
  • Give credit where due
  • Help review pull requests
  • Mentor others when possible
Think about how your words and actions affect others.
  • Consider impact before posting
  • Apologize when you make mistakes
  • Learn from feedback
  • Assume communication challenges (language barriers, cultural differences)

​
For Contributors

1

Follow Contribution Guidelines

Read and follow the contribution guidelines. This shows respect for maintainers’ time and community standards.
2

Accept Feedback Gracefully

Code reviews are about the code, not you personally. Requested changes help improve the project.
3

Be Patient

Maintainers are volunteers. Reviews may take time. Don’t demand immediate attention.
4

Test Thoroughly

Test your contributions before submitting. Don’t rely on maintainers to catch basic errors.

​
For Maintainers and Reviewers

1

Be Encouraging

Recognize effort and improvement. Celebrate contributions, especially from first-timers.
2

Give Constructive Feedback

Explain why changes are needed, not just what needs changing. Suggest alternatives when possible.
3

Be Timely

Try to respond to contributions within a reasonable timeframe. If you can’t review immediately, acknowledge receipt.
4

Mentor When Possible

Help contributors grow their skills. The time invested in teaching pays dividends for the community.

​
Scope Clarifications

​
What This Code Covers

✓ Behavior in GitHub issues, PRs, and discussions
✓ Interactions on Discord and community chat
✓ Email communications with maintainers
✓ Representing the project in public forums
✓ Community events and meetings

​
What This Code Doesn’t Cover

This Code of Conduct does not apply to:
  • Personal social media not related to the project
  • Private communications unrelated to the project
  • Off-topic discussions in personal spaces
However, harassment that starts in community spaces and continues elsewhere may still be addressed.

​
Disclaimer

Not all reported issues will be treated as Code of Conduct violations. Reports may be declined if they are deemed:
  • Outside the scope of this Code of Conduct
  • Not in violation of stated standards
  • Resolved through normal community processes
  • Made in bad faith
In such cases, reporters will receive an explanation of the decision.

​
Security Vulnerabilities

Security vulnerabilities should be reported privately, not publicly. See SECURITY.md for reporting procedures.
Reporting a vulnerability publicly before it’s fixed can put users at risk and is not aligned with responsible disclosure practices.

​
Questions and Concerns

If you have questions or concerns about this Code of Conduct:

Email Maintainers

[email protected]

GitHub Discussions

Start a discussion for policy clarifications

Discord

Ask in the community Discord server

Contributor Covenant FAQ

See general FAQ about Contributor Covenant

​
Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.

​
Changes to This Code

We may revise this Code of Conduct from time to time. When we do:
  • Changes will be committed to the repository
  • Significant changes will be announced in community channels
  • The version/date will be updated
  • Community feedback will be considered
Last Updated: March 2026For the most current version, see the repository.

​
Our Commitment

By fostering a welcoming and inclusive community, we can:
  • Build better software together
  • Learn from each other’s experiences
  • Support users more effectively
  • Grow the Proxmox VE ecosystem
  • Make open source more accessible to all
Thank you for being part of our community and helping make it a positive space for everyone!

Build docs developers (and LLMs) love

Get started for freeTalk to us