Ctrl K
ComunidadGuías…

CODE_OF_CONDUCT.md

Rama main · réplica de lectura del repositorio original.

Archivo original ↗Preguntar a KiBot
# Code of conduct

## Our commitment

Dreamax License Manager contributors, maintainers, and community participants
are expected to make project spaces respectful, constructive, and accessible
regardless of experience, identity, background, or level of familiarity with
WordPress, WooCommerce, or security engineering.

## Expected behavior

- Discuss ideas and code without attacking the person proposing them.
- Give specific, actionable feedback and accept correction professionally.
- Respect privacy, coordinated vulnerability disclosure, and confidential data.
- Welcome questions asked in good faith and help contributors understand project
  constraints.
- Disclose relevant conflicts of interest and avoid misleading claims.
- Focus on the project's users, maintainability, security, and public benefit.

## Unacceptable behavior

- Harassment, threats, discrimination, sexualized conduct, or personal insults.
- Publishing another person's private information without permission.
- Deliberately exposing secrets, customer data, or undisclosed vulnerabilities.
- Spam, manipulation, impersonation, or fabricated adoption/contribution
  activity.
- Sustained disruption of project discussions or review processes.

## Scope

This code applies in repository discussions, issues, pull requests, reviews,
support interactions, and other spaces where a person represents the project.

## Reporting and enforcement

Report conduct concerns privately to
[support@dreamaxsoft.com](mailto:support@dreamaxsoft.com). If that mailbox is
unavailable, use [info@dreamaxsoft.com](mailto:info@dreamaxsoft.com). A public
issue may request a private contact channel without identifying affected people
or including sensitive details.

Maintainers will review reports in context and may edit or remove content,
issue a warning, limit participation, or permanently exclude a participant.
They will seek to protect the privacy and safety of reporters and affected
participants. Maintainers who are directly involved in a report should not be
the sole decision-maker when another suitable reviewer is available.