Investigating supporting reviews from Google Docs

[kjlubick]

Expected behavior is people copy-paste reviews into a google doc, highlight things to address, optionally add comments.

Also make a milestone that encompasses all those review issues, so we can more easily monitor progress.

I don't know how data extraction from Google Docs will go, but I'll look into that.

/cc @mambocab

[kjlubick]

Possible User story
Fictious paper writer Dennis has just had his paper on cold fusion accepted! He has several comments from three reviewers that he wants to turn into GitHub issues before he submits the camera ready copy. He copy-pastes the email into a Google Doc. He identifies several things he needs to address and a few other things that he will consider (but probably not be able to address, due to space constraints). All of these comments, he highlights and then creates a comment (Ctrl + Alt + M) for 8 comments total.

He then makes this doc "viewable to anyone with the link" and then pastes it into a textbox in the pdfreview tool (perhaps under a new tab "Google Doc comments"). He also selects a repo and optionally chooses to make a new Milestone called "IJCF Camera Ready". 8 GitHub issues are created for that repo, containing the highlighted section and a bit of context from that paragraph on either side. All issues are a part of the newly-created Milestone. (Like normal comments, Dennis could have selected to tag these with custom labels)

Implementation hints: https://developers.google.com/drive/web/manage-downloads#downloading_google_documents to export as html, which can handle the text and comments. Simply look for the <span> right before the <sup>. That is the "highlighted" portion.

becomes:

Milestones can be added to issues and created via the API