Conduct

This is not the Contributor Covenant. Stock secureblue ships that document (v2.0, Mozilla-style enforcement ladder, identity checklist, “community leaders”). We do not. We do not mirror it. If you want a four-step inquisition, their site still has one.

Our “pledge”

We pledge to maintain an overlay. We do not pledge to make you feel seen. We do not pledge a “healthy community.” GitHub is not a parish.

Whoever shows up with a useful patch, a reproducible bug, or a clear question is welcome. Skin, church, vote, pronouns, and your blog are not admission criteria and not disqualification criteria. They are also not the subject of this repo.

What they shipped, translated

Their CoC is the stock Contributor Covenant. In practice that document does three jobs this overlay will not do:

  1. A protected-class liturgy instead of “don’t harass people.” If you need a census of identities before you can say “be decent,” you are writing HR, not an OS overlay.
  2. A vague crime of ‘unwelcome’. “Inappropriate in a professional setting,” “offensive,” “harmful,” and “disparagement of classes of individuals” are unlimited warrants. Maintainers can already close a bad issue. They do not need a theology of harm to do it.
  3. A court. Correction → warning → temporary ban → permanent ban, plus “no unsolicited interaction with the enforcers,” plus off-platform scope when you “represent the community.” That is how a CoC stops being manners and starts being a political machine. DHH’s line is enough: the legalese armed the inquisition. Never again.

The actual rules

  1. Don’t make the maintainer invent more rules.
  2. If you do, you are gone, and the extra rule can go with you after a cooldown.
  3. If you are a bigger pain in the ass than your contributions justify, you are ejected. (DHH / the Omarchy refusal of Covenant-as-default.)

Concrete, because “don’t be a pain” still has a floor:

Scope

This repo, our Issues/PRs, and this site. Not your timeline, not a conference hallway, not “you posted a take while someone might think you speak for Unwoke SecureBlue.” You don’t. There is no appointed representative program.

Enforcement

There is no Conduct Committee, no impact ladder, no mandatory public apology. The maintainer closes, locks, or blocks. GitHub’s own ToS still apply because this is GitHub.

Reports of actual crimes go to the police, not to a proton.me inbox running Mozilla’s four steps.

Attribution

Not adapted from the Contributor Covenant. Written so we would not have to host theirs. Their version remains at secureblue.dev/code-of-conduct. It is skipped by our daily mirror on purpose.