CODE_OF_CONDUCT.md

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

# Community Code of Conduct

APEX welcomes constructive participation from people of all backgrounds and experience levels. These standards apply to this repository's issues, pull requests, discussions and other project-managed community spaces, including participation by maintainers.

## Expected behavior

- Treat people with respect. Critique ideas and code with concrete reasons, and allow room for questions and mistakes.
- Keep conversations relevant and make disagreements about the work. Be considerate of language differences and accessibility needs.
- Respect privacy, confidentiality and intellectual property. Share only information you are entitled to publish.
- Accept reasonable moderation requests and help keep discussions useful to other contributors.

Harassment, discriminatory abuse, threats, sexual harassment, doxxing, impersonation and persistent unwanted contact are not acceptable. Spam and deliberate disruption are also not acceptable.

## Reporting and moderation

Use GitHub's **Report content** action on the relevant issue, comment or discussion to report a concern to repository administrators. Avoid posting personal information or allegations in a public thread. If a concern involves a repository administrator, use GitHub's abuse-reporting process instead of relying on that person to investigate their own conduct. See [GitHub's reporting guidance](https://docs.github.com/en/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).

Repository administrators assess context and severity and may ask for an edit, remove content, limit participation or block access to project community spaces. A serious incident can warrant immediate restriction. Moderators should explain decisions where appropriate and limit disclosure of report details to what is needed to address the concern. GitHub's reporting process is also available for conduct that violates its platform policies.

To request reconsideration, provide relevant new context through the same private reporting route; do not continue the dispute in unrelated public threads. These community expectations do not amend the software license or create a separate contributor agreement.