So what I realized I could do was create PRs like #112 that all consisted simply of adding the file players/jeffkaufman/bonuses/lose-a-point with contents -1. All of these PRs would be allowed to merge, but then the file would only be created once, and if I merged N pull requests I would expect to gain N-1 points. The key thing is that git does not consider it a merge conflict if two different PRs create the same file with the same contents.
The EA movement has a ton of programmers, many of them earning to give, and many of them interested in moving into some form of direct work.
Roles for programmers in direct work tend to sit open for a long time, and people trying to hire programmers have a really hard time finding people.
As far as I can tell, though, these really are both true!
Most of my stuff lives in the cloud: email on Gmail, docs in Google Docs, photos in Google Photos, data in Google Drive. I trust Google a lot for this sort of thing, both given their public reputation and as an employee. I think Google is extremely unlikely to lose or corrupt my data.
The next biggest place where I have things is on the server that runs jefftk.com. I back this up to my laptop with a cronjob that looks like:
This shows what PRs need review by which people. Figuring this out efficiently from GitHub's interface was one of the biggest things slowing the game down. GitHub isn't designed around the idea that all repo collaborators are interested in reviewing every PR.