If you're feeling confused about GitHub's new review requests feature (as opposed to the existing ability to assign people to issues and pull requests) here's my take.
When review requests were first rolled out, they were not very useful because there was no way to see a list of pull requests you had been requested to review. Thankfully, that deficiency has been fixed!
Now, review requests unleash a great way to manage workflow on pull requests.
When you create a pull request, you add a review request for one or more reviewers. In addition, assign the pull request to the reviewer to signal that you are awaiting their action.
When the reviewer finishes their review, they should either merge the pull request (LGTM!) or assign it back to you (or someone else) for action -- respond to a comment, answer a question, revise code, etc.
Then when you respond to feedback, you assign the pull request back to the reviewer, and the cycle repeats.
There is additional explicit signaling in the review request workflow that you can use, too.
So, improve your pull request workflow by:
On June 11, Twitter retired version 1.0 of their REST API. It was announced well in advance, but I had other things to do; checking to see if my Twitter tools would still work was too low a priority. Until they broke.
When I refer to my "Twitter tools," I mean a Python command-line script that I use to post to Twitter from bash scripts, PHP programs, Node.js programs, etc. That Python script is little more than a wrapper around an abandoned open source library that broke when Twitter turned off API v1.0 -- twitter-oauth. The repository seems to have been emptied, too. Luckily, the library is still available in the Python Package Index: http://pypi.python.org/simple/twitter_oauth/
So, I grabbed the library, updated it so that it works again, and put it up on GitHub: danmactough/twitter-oauth.
Is there a protocol for taking over an abandoned project?