Skip to content

vetcoders/pages-probe

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 

Repository files navigation

Code of Conduct

This applies to every public surface of the vetcoders organization — repos, issues, PRs, discussions, and any space where the org name appears.

We work small. We work direct. The conduct rules below are short on purpose.


The contract

  1. No personal attacks. Critique code. Critique decisions. Do not critique people.
  2. Assume good faith. A wrong answer is not a moral failure. Treat it as an opportunity.
  3. Be specific. "This is broken" is noise. "This crashes when X is null because Y dereferences before checking" is signal.
  4. Listen before correcting. Especially when correcting someone working in a language that is not their first.
  5. No hype, no bullshit. Performative excitement reads as dishonesty. State facts.
  6. Sensitive data does not belong in issues. Redact API keys, customer names, patient information.

Things we will not do

  • We will not tolerate harassment of any kind — sexist, racist, ableist, homophobic, transphobic, or otherwise targeting a person or a group.
  • We will not engage with bad-faith trolling. Issues that are pure noise will be closed. Repeated bad-faith behavior gets a ban.
  • We will not let "I was joking" walk back something that hurt someone.

Things we will do

  • Respond to good-faith questions, even when they reveal we got something wrong.
  • Apologise plainly when we get it wrong. No corporate dance.
  • Update the rules when reality demands it. This document is not gospel — it is a working agreement.

Reporting

If something happens that violates this conduct — to you, or that you witness — please write to:

Reports are read by humans, not bots. Expect a reply within a few days. Confidentiality is the default — we will not discuss your report publicly.


Scope

This document covers the vetcoders GitHub org. Each repository may add additional rules in its own CONTRIBUTING.md. When the two conflict, the repo-level rule wins for that repo, but the org-level conduct (no harassment, etc.) is non-negotiable.

Sister org Loctree and mother org LibraxisAI maintain their own conduct documents.


© 2024–2026 LibraxisAI

About

temporary GitHub Pages diagnostic probe - safe to delete

Code of conduct

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages