Match scraped elipsized emails with known Developer emails

[kaylaerdmann]

We will be parsing both the owner and commenter ids and emails from the json. This is fine temporarily, but we want to be able to match developers through their emails between code reviews and bug issues. Let's find matches and throw them into a google spreadsheet for now.

[andymeneely]

We'll need the following done for this:

• GoogleCode's UID added to the Developer table
• Figure out which emails can easily be linked, and figure out which ones we need a manual trace for.
• Load our manual tracing in the GoogleSpreadsheet BEFORE loading bug data so that when we see a UID, we can just look it up and it'll be there.

We're going to get A LOT more developers in the bug data than in code reviews, so we can't trace all of them manually. We'll need to do some automated work by looking up the ellipsized emails and seeing if there's a unique result. Or, maybe there's another way?

[andymeneely]

Ok, I'm reviving this task and assigning it to @kayladavis. Let's revisit this problem and try to come up with a creative solution, or come to a better understanding of our limitations.

One option might be that we cannot mine developers emails from the bug data unless we have the raw email to begin with, say, from the commit logs. But, I'd obviously rather get the emails if we can.

[andymeneely]

In retrospect, we now have a ton of great research questions that don't require this data. Let's shelve this and close it.