zlacker

>>chwtut+(OP)
"Open source has always worked on a system of trust and verify"

Not sure about the trust part. Ideally, you can evaluate the change on its own.

In my experience, I immediately know whether I want to close or merge a PR within a few seconds, and the hard part is writing the response to close it such that they don't come back again with the same stuff.

(I review a lot of PRs for openpilot - https://github.com/commaai/openpilot)

>>adeebs+1C1
When there's time, you review, when there isn't you trust...

>>ngcazz+8L1
That's the issue here.

Even if I trust you, I still need to review your work before merging it.

Good people still make mistakes.

>>999900+dN1
What is the definition of trust if you still have to verify? How does "trust" differ from "untrust" in that scenario?

>>stavro+fZ1
trust resudes the verification I suppose. Getting a PR from a trusted contributor would probably have me do a quick scan for obvious mistakes. And they'd know to keep the PR's small and on the right branch to help facilitate a scan.

a new person with a big idea on the slightly wrong (but reasonable) channel would have more work in verification.