Skip to content

CODE_OF_CONDUCT.md

Latest commit

 

History

History
50 lines (33 loc) · 3.3 KB

CODE_OF_CONDUCT.md

File metadata and controls

50 lines (33 loc) · 3.3 KB
Raw

OpenCoven community code of conduct

OpenCoven exists to build trustworthy, identity-preserving infrastructure together. Participation in Psyche Build requires mutual respect, technical honesty, and care for the people and systems affected by the work.

Expected conduct

Participants are expected to:

  • engage with people and ideas respectfully, including during disagreement or review;
  • critique the work rather than demean the person;
  • state evidence, uncertainty, tradeoffs, and conflicts of interest plainly;
  • respect consent, privacy, identity, authorship, and project boundaries;
  • avoid pressuring others to disclose personal information, credentials, private conversations, or proprietary material;
  • accept correction, repair harm where possible, and help maintain a safe, focused environment;
  • follow repository security, contribution, governance, and support policies.

Unacceptable conduct

Unacceptable behavior includes:

  • harassment, threats, stalking, intimidation, or discriminatory abuse;
  • sexualized attention or imagery directed at another participant without consent;
  • deliberate misgendering, deadnaming, doxxing, impersonation, or identity-based humiliation;
  • publishing another person's private information or communications without permission;
  • coercion, retaliation, bad-faith review obstruction, or sustained disruption;
  • knowingly false claims about implementation, evidence, support, authorship, or security status;
  • soliciting or exposing credentials, private keys, signing material, vulnerability details, private repository contents, raw prompts, or unrestricted terminal output in public project surfaces.

Scope

This policy applies in repository issues, pull requests, reviews, commits, project boards, release and security coordination, OpenCoven community spaces, and public representation of the project.

Reporting conduct concerns

Report conduct concerns privately to an OpenCoven maintainer through an already established and verified private channel. Do not publish sensitive evidence in an issue or pull request. For a suspected product vulnerability, use SECURITY.md instead.

Include only the minimum information needed to understand the incident. Maintainers will limit access to people necessary for a fair review and will avoid conflicts of interest where possible. Confidentiality cannot be absolute when disclosure is required by law or necessary to prevent imminent harm.

Enforcement

Maintainers may apply a proportionate response based on severity, pattern, impact, intent, and willingness to repair:

  1. Correction — private or public clarification and a request to change behavior.
  2. Warning — a documented boundary and consequences for repetition.
  3. Temporary restriction — limited participation, review, or repository access.
  4. Permanent removal — removal from project spaces or collaboration.

Credible threats, doxxing, credential exposure, active exploitation, or severe harassment may move directly to restriction or removal. Retaliation against a reporter, witness, or maintainer participating in a good-faith review is itself a violation.

Maintainers should document the decision, preserve only necessary evidence, communicate it to affected parties where safe, and provide an appeal route to a non-conflicted maintainer when one is available.