Skip to content

Latest commit

 

History

History
94 lines (69 loc) · 3.48 KB

File metadata and controls

94 lines (69 loc) · 3.48 KB

Code of Conduct

Springtale is built for people whose safety depends on privacy: trans people, POC, activists, IPV survivors, immigrants, sex workers, journalists, defectors, anyone the dominant culture treats as disposable. That commitment shapes how we run this project too.

What we expect

  • Take the threat model seriously. Don't out, don't dox, don't link pseudonyms to real identities, don't speculate about anyone's background. If someone contributes under a pseudonym, that's the name they have here.
  • Plain speech, no condescension. Junior contributors are not burdens. "RTFM" is not a code review.
  • Disagreement, not contempt. Argue against the diff, never against the person. "This is wrong because of X" lands; "you obviously don't understand X" does not.
  • Receive criticism well. When a maintainer asks you to redo something, the answer is "ok, let me try again", not "but I worked hard on this".

What we don't tolerate

  • Slurs, harassment, sustained personal attacks. One strike for slurs; a documented pattern for the rest.
  • Outing, doxxing, threats of either. Immediate and permanent ban.
  • Demanding that pseudonymous contributors reveal their real identity. No exceptions.
  • "Just asking questions" framing around any of the above.
  • Repeatedly bringing up reasons someone "shouldn't" be a target user.

Scope

This Code applies to:

  • The Springtale repo and any GitHub spaces tied to it (issues, PRs, discussions, security advisories).
  • Any official chat channels or community spaces (if we ever spin them up).
  • Off-platform behaviour that materially affects the project — if someone is harassing a contributor on a different platform because of their work here, that's in scope.

Reporting

Report Code of Conduct violations to: k1104jackson@hotmail.com

Reports should include:

  • What happened (link to the message/diff/comment if public).
  • Who was involved.
  • What outcome you'd like, if you have one in mind.

Reports are read by the maintainer. We won't share your identity with the person you're reporting unless we have your explicit consent. We won't share the report contents publicly unless we have your explicit consent.

If the maintainer is the person you're reporting, contact GitHub's abuse team directly: https://github.com/contact/report-abuse.

Response

We aim to acknowledge reports within 72 hours and decide on action within 14 days. Decisions are based on the report, any other reports on file, and the contribution history of the people involved.

Possible outcomes:

  • Direct conversation with the person.
  • Public warning.
  • Temporary suspension from issues/PRs/discussions.
  • Permanent ban.
  • Removal of contributions if they were made in bad faith.

Appeals

If you think a moderation decision is wrong, reply to the original report thread with what you want reconsidered and why. Decisions are not infinitely re-litigatable, but we'll read an appeal once.

Maintainer responsibilities

Maintainers commit to:

  • Holding ourselves to a higher standard than we hold contributors.
  • Not weaponising moderation against people we personally disagree with on technical questions.
  • Documenting bans and the reasoning, even if not publicly.

This Code is adapted from the Contributor Covenant 2.1 and from the Mozilla Community Participation Guidelines, reshaped to match Springtale's target users and threat model.