Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
47 lines (32 loc) · 2.32 KB

CODE_OF_CONDUCT.md

File metadata and controls

47 lines (32 loc) · 2.32 KB
Raw

Community Code of Conduct

VCRS exists to make software development more approachable and more trustworthy. The community should reflect the same values.

Expected behavior

Participants are expected to:

  • communicate with respect and patience;
  • welcome questions from people with different levels of technical experience;
  • give specific, constructive feedback about ideas and contributions;
  • distinguish evidence from opinion;
  • acknowledge mistakes and correct them;
  • credit sources and prior work;
  • protect private, personal, client, and employer information;
  • respect stated boundaries and requests to stop an interaction;
  • focus disagreements on the work rather than the person.

Unacceptable behavior

The following are not acceptable in project spaces:

  • harassment, threats, intimidation, or sustained unwanted attention;
  • discriminatory, demeaning, or sexualized language or imagery;
  • personal attacks, insults, or deliberate humiliation;
  • publishing another person's private information without permission;
  • impersonation or misrepresentation intended to deceive;
  • knowingly submitting secrets, private code, client data, or identifying records;
  • plagiarism or intentional removal of attribution;
  • spam, manipulation, or undisclosed promotional activity;
  • repeatedly disrupting a discussion after a moderator asks for a change in behavior.

Scope

This policy applies to repository Issues, Discussions, pull requests, reviews, release spaces, and other channels operated for the project. It also applies when someone is officially representing VCRS.

Reporting a concern

For urgent platform abuse or threats, use GitHub's reporting tools.

For a project conduct concern, do not publish sensitive incident details. Open an issue titled “Private conduct contact requested” with no additional incident information, or contact an active maintainer through a private method shown on their GitHub profile. A maintainer who is involved in the concern should not handle the report.

Response

Maintainers may request clarification, remove content, issue a warning, limit participation, or ban an account from project spaces. Actions should be proportionate to impact, documented privately where appropriate, and focused on restoring a safe environment.

Retaliation against someone who raises a good-faith concern is prohibited.