rununtil -- zsh
cd ./how-deep-we-go

rununtil --map ./stack

Most teams stop at a boundary.
We don't have one.

Product code, web platform, browser engine, system internals, compiler toolchain -- one head, whole stack. When the root cause moves down a layer, we follow it.

productapps, tooling, automation -- the thing users touch
web platformhtml / css / js apis, specs, web platform tests
browser enginechromium, blink, pdfium, v8 -- rendering, loading, lifecycle
systemnetworking, ipc, gpu, codecs, memory, sandboxing
toolchainllvm, clang, rust -- yes, the compiler itself

rununtil --trace ./true-story

How far do we actually go?

trace.log
$ rununtil fix chromium-bug [1] chromium: bug confirmed, fix written [2] build: blocked -- the compiler miscompiles the fix [3] llvm/clang: root cause found upstream [4] llvm/clang: patch written, reviewed, landed [5] chromium: original fix landed done. exit 0
We once fixed the compiler to fix a browser bug. That is what "run until" means.

rununtil --navigate ./the-gauntlet

Writing the code is half the job.
Landing it is the other half.

Big open-source trees are guarded by review culture, owners, style rules, try bots, and standards processes. We have moved hundreds of changes through them -- we know how to get things moving.

upstream review

gerrit, github, phabricator -- reviewers across chromium, llvm, and friends

owners & areas

finding the right people, splitting changes so they can say yes quickly

proof & testing

regression tests, web platform tests, fuzzers, try bots kept green

specs & process

standards positions, intents, feature flags, metrics -- shipping the official way

rununtil --start

Blocked below your codebase?
Need something the platform can't do yet?

Bring the problem. We'll tell you honestly which layer it lives in and what it takes to fix or build it -- all the way down if necessary.

helmut@januschka.com back to the terminal