jverkoey looks to have implemented this himself.
Actually, looking back through the network graph (http://github.com/facebook/three20/network) and commit log (http://github.com/facebook/three20/commits/master) there really aren't ANY credits regarding merged-in patches or other contributions.
<del>I hate to say it, but the current system (i.e. all commits through jverkoey) has the major drawback of putting code accountability in nobody's hands but Joey's.</del>
---
Rescinded: http://github.com/facebook/three20/blob/master/CHANGES#L93
But everyone knows thats a daunting task, and theres no reason to review a simple thing like this to question where it originally came from. Right?
Git is awesome, because it helps prevent these situations, but it's only a tool. Different people will use it differently, and based on the comments of the blog post, once he found out that it was copyrighted code, he rectified the problem. http://github.com/facebook/three20/commit/204673eea141acf4ee...
I'm not trying to pass blame, but I do believe that jverkoey never had the intention of stealing this code. None the less, Facebook.app ended up on the sour end of a situation they could have solved months ago, but they had no idea there was a problem until now.
I've used Three20 a ton, and actually build my Hacker News iPhone app using it.[1] I've used the drag-to-refresh header a bunch. This code was added to the Three20 framework months ago via somebody on GitHub. One pull request, and it was in the main repo.
The project is currently maintained by Jeff Verkoeyen, a full-time student. Three20 makes use of a ton of other open-source projects (JSON parser, etc.). Whoever submitted this code just didn't add any attribution. When Facebook updated their app, it was probably only 2-3 lines to add. And since it's been in the codebase for months now, and a bunch of other apps use it, they probably figured it was no problem.
Although flaming blog posts feel good to write, a much more constructive action would be to call up Facebook and talk to them. Or email Jeff. Or post to the Three20 Google Group (almost 1k people). Or submit an issue on GitHub. Or anything really.
Not to mention the fact that they stole it from Loren Bricher (Tweetie) in the first place...
[1] http://michaelgrinich.com/hackernews