# ProtonPlus Code of Conduct

ProtonPlus is a community project for managing Windows compatibility tools on
Linux. We welcome users, contributors, translators, packagers, maintainers,
and everyone else who helps the project or uses its software.

This Code of Conduct describes the behavior expected in ProtonPlus community
spaces and the process for addressing problems. It applies equally to
everyone, including maintainers and other people with decision-making
authority.

## Expected behavior

Participants are expected to:

- Be respectful, considerate, and inclusive.
- Discuss ideas and technical decisions without attacking people.
- Communicate clearly and constructively, especially across differences in
  language, culture, experience, and accessibility needs.
- Give and accept feedback in good faith, and take responsibility for mistakes
  or harm caused by our words or actions.
- Credit the work of others and respect their privacy.
- Follow the project’s contribution and moderation processes.

Disagreement about code, design, project direction, or support is welcome when
it remains professional and focused on the work.

## Unacceptable behavior

The following behavior is not acceptable in ProtonPlus spaces:

- Harassment, intimidation, stalking, or sustained unwanted contact.
- Discrimination, slurs, personal attacks, or derogatory comments based on
  identity, background, ability, experience, or any other personal
  characteristic.
- Unwelcome sexual attention, sexualized language or imagery, or other sexual
  conduct that is inappropriate for the context.
- Threats of violence, incitement, or conduct that puts someone’s safety at
  risk.
- Publishing or threatening to publish private or identifying information
  without permission, including doxxing.
- Deliberate disruption, trolling, spam, impersonation, or misrepresenting an
  affiliation with ProtonPlus.
- Plagiarism or presenting someone else’s work as your own.
- Retaliation against someone who raises a concern or participates in a
  review.
- Knowingly making a bad-faith report to harass, intimidate, or silence
  another participant.

This list is not exhaustive. Behavior that a reasonable person would consider
threatening, abusive, or seriously disruptive may also violate this Code of
Conduct.

## Scope

This Code of Conduct applies to ProtonPlus project spaces and activities,
including the GitHub repository, issues, pull requests, code reviews, commit
discussions, the Weblate translation project, project email, and any official
online or in-person event or account.

It also applies when someone is officially representing ProtonPlus in another
space. Conduct outside project spaces may be considered when it directly
affects someone’s safety or ability to participate in the ProtonPlus community.

## Reporting a concern

Report suspected violations privately to [dev@vysp3r.com](mailto:dev@vysp3r.com).
Do not use a public issue, pull request, or discussion for a conduct report.

Reports may be made by the person affected or by a witness. Include whatever
you can safely share, such as:

- What happened, and when and where it happened.
- Links, screenshots, or other relevant evidence.
- The accounts or people involved and any witnesses.
- Whether there is an immediate safety concern.
- How you would prefer to be contacted and any confidentiality concerns.

You do not need to confront the person involved before making a report. If
there is an immediate threat to someone’s safety, contact local emergency
services first and report to ProtonPlus when it is safe to do so.

Bug reports, feature requests, and technical support belong in the [issue
tracker](https://github.com/Vysp3r/ProtonPlus/issues). Security vulnerabilities
must be reported privately according to the [security
policy](SECURITY.md).

## Maintainer responsibilities

Project maintainers are responsible for clarifying and applying this Code of
Conduct. They will:

- Treat reports seriously and acknowledge receipt when practical.
- Review reports promptly, fairly, and without requiring public disclosure.
- Give the people involved an opportunity to respond when doing so is safe
  and appropriate.
- Consider the impact, context, pattern of behavior, and safety risks rather
  than relying only on stated intent.
- Recuse themselves from decisions involving a conflict of interest whenever
  possible.
- Explain decisions and any restrictions to the people directly affected,
  while protecting private information.

## Enforcement

After reviewing a report, maintainers may take any proportionate action needed
to protect the community, including:

- A private reminder or warning.
- Removal or editing of content and a request to stop the behavior.
- A temporary restriction on specific project spaces or interactions.
- A temporary suspension or permanent ban from project spaces.

The response will depend on the seriousness, impact, and pattern of the
behavior. Maintainers may skip steps when a serious violation or immediate
safety concern requires it. Enforcement may also address attempts to evade a
restriction or retaliate against a reporter. Good-faith reports that do not
result in action are not violations of this Code of Conduct.

## Privacy and confidentiality

Reports and related information will be handled privately and shared only with
people who need it to review or respond. We will not publicly identify a
reporter or disclose report details without consent unless disclosure is
necessary to protect someone, investigate the concern, or comply with a legal
obligation. Email and online services cannot guarantee absolute
confidentiality, so do not include passwords, access tokens, or unrelated
sensitive information.

## Appeals

Anyone directly involved in an enforcement decision may request an appeal by
replying to the decision email within 30 days. An appeal should identify new
information or a concern about how this Code of Conduct was applied. An appeal
does not automatically suspend safety measures already in place.

Where practical, an appeal will be reviewed by a maintainer who was not
involved in the original decision. If that is not possible, the original
decision-maker will review the new information and explain the outcome. The
appeal decision is final for the project.

## Attribution

This document is adapted from the [Contributor Covenant, version
3.0](https://www.contributor-covenant.org/version/3/0/), and informed by
community practices from [GNOME](https://conduct.gnome.org/),
[KDE](https://kde.org/code-of-conduct/), and
[Mozilla](https://www.mozilla.org/en-US/about/governance/policies/participation/).
Original ProtonPlus sections describe this project’s reporting, privacy,
enforcement, and appeals processes.

Contributor Covenant is stewarded by the Organization for Ethical Source and
licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/).
