docs: the launch playbook, written before anything is posted - #54
Merged
Merged
Conversation
Last of the three adoption documents #43 asks for. The other two say what the project is; this one says what will and will not be claimed about it, while that is still a decision rather than a reply in a comment thread. The useful half is the list of things not to claim. "Faster than pre-commit" is the trap here: it is true for trivial hooks and false for the ones people actually wait on, and leading with the 4x rather than the 1.0x is how a port spends its credibility in the first hour. The weak points are listed with links to where each is already documented, so the answer to a comment that finds one is "yes, that is in the docs" and never a defense. Windows is on that list. Also records where not to post: upstream's tracker, discussions and chat are not launch venues for a reimplementation of their work. Refs #43
blairham
force-pushed
the
announcement
branch
from
September 8, 2026 01:37
f59cff1 to
bcdd6ec
Compare
16 of 19 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The last of the three adoption documents #43 asks for.
comparison.mdandstability.mdsay what the project is; this says what will and will not be claimed about it — while that is still a decision rather than a reply in a live comment thread.The useful half is the list of things not to claim
"Faster than pre-commit" is the trap. It is true for trivial hooks and false for the ones people actually wait on — the README benchmark already shows 4× on
trailing-whitespaceand 1.0× ongolangci-lint. Leading with the 4× is how a port spends its credibility in the first hour, so the playbook says to lead with the 1.0×.Also not claimed: "a replacement for pre-commit" (it is an independent reimplementation of someone else's design), "100% compatible" (the claim is 82 measured differential checks against a named upstream version), and anything reassuring about Windows.
Weak points, stated before someone finds them
A table of every known soft spot with a link to where it is already documented — Windows (#53), the ten unexercised language backends, the
pre-commitname collision, the shared destructive cache, whatv4.6.xmeans, and the single-maintainer reality.The rule attached to it: if a comment finds one, the answer is "yes, that is in the docs, here is the link" — never a defense.
Where not to post
Upstream's issue tracker, discussions and chat are not launch venues for a reimplementation of their work. Announcing there is how a port earns a reputation before it earns users.
Also includes the expected first comments with their answers, and a pre-flight checklist that matches the one in #43.
Refs #43