Changing how contributions are scored on http://slop.cash We were focused on PRs, but this creates issues when requirements on the project change. What if the maintainer wants to make some last minute fixes to an otherwise good PR, or resolve merge conflicts? We can always kick back comments to the contributor to change on their fork, but it slows the process down a lot, and with a fast moving codebase it can be several rounds of this while many PRs stay open or go stale. Instead, the PR value will be given to the contributor of the commits, not the creator of the PR. That way, maintainers can make tweaks, reopen a new PR (since they can't easily PR onto the forks) and merge as they go. Building the plane while flying it. Thanks for the feedback sloperators!