{"action":"created","issue":{"url":"https://api.github.com/repos/ropensci/onboarding/issues/4","labels_url":"https://api.github.com/repos/ropensci/onboarding/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/ropensci/onboarding/issues/4/comments","events_url":"https://api.github.com/repos/ropensci/onboarding/issues/4/events","html_url":"https://github.com/ropensci/onboarding/issues/4","id":60931587,"number":4,"title":"Start this from the command line?","user":{"login":"karthik","id":138494,"avatar_url":"https://avatars.githubusercontent.com/u/138494?v=3","gravatar_id":"","url":"https://api.github.com/users/karthik","html_url":"https://github.com/karthik","followers_url":"https://api.github.com/users/karthik/followers","following_url":"https://api.github.com/users/karthik/following{/other_user}","gists_url":"https://api.github.com/users/karthik/gists{/gist_id}","starred_url":"https://api.github.com/users/karthik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/karthik/subscriptions","organizations_url":"https://api.github.com/users/karthik/orgs","repos_url":"https://api.github.com/users/karthik/repos","events_url":"https://api.github.com/users/karthik/events{/privacy}","received_events_url":"https://api.github.com/users/karthik/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-03-12T23:14:48Z","updated_at":"2015-03-13T00:37:04Z","closed_at":null,"body":"@sckott @richfitz\nTell me if this idea is too complicated. Instead of a user coming over to the repo, then copying a block of text into a new issue and editing in place, how about we do this programmatically? We can write a really  lightweight package that wraps the CLI for GitHub issues. Then from the working directory of a package (or passing the path) to something akin to `devtools::release`, a user does `ropensci_contribute()` (or something like that).\n\nThe function will read the description, extract author information, license, Travis integration, coveralls integration, vignette info etc. The remaining questions will be a wizard, just like `devtools::release`. At the end, all the information is formatted and an issue is programmatically pushed to the repo. \n\nPerhaps too much (I am starting to think so) but just wanted to throw this ide out (perhaps for a later time)."},"comment":{"url":"https://api.github.com/repos/ropensci/onboarding/issues/comments/78717679","html_url":"https://github.com/ropensci/onboarding/issues/4#issuecomment-78717679","issue_url":"https://api.github.com/repos/ropensci/onboarding/issues/4","id":78717679,"user":{"login":"cboettig","id":222586,"avatar_url":"https://avatars.githubusercontent.com/u/222586?v=3","gravatar_id":"","url":"https://api.github.com/users/cboettig","html_url":"https://github.com/cboettig","followers_url":"https://api.github.com/users/cboettig/followers","following_url":"https://api.github.com/users/cboettig/following{/other_user}","gists_url":"https://api.github.com/users/cboettig/gists{/gist_id}","starred_url":"https://api.github.com/users/cboettig/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cboettig/subscriptions","organizations_url":"https://api.github.com/users/cboettig/orgs","repos_url":"https://api.github.com/users/cboettig/repos","events_url":"https://api.github.com/users/cboettig/events{/privacy}","received_events_url":"https://api.github.com/users/cboettig/received_events","type":"User","site_admin":false},"created_at":"2015-03-13T00:37:04Z","updated_at":"2015-03-13T00:37:04Z","body":"Great idea.  :+1: for having options to do either way\n\nOn Thu, Mar 12, 2015, 5:31 PM Scott Chamberlain <notifications@github.com>\nwrote:\n\n> @richfitz <https://github.com/richfitz> yeah, i think we'd just register\n> an app, and they auth with ours.\n>\n> I imagine some may not want to deal with doing it from R, so would be good\n> to allow both\n>\n> don't know if there's anything in these useful wrt this if people will be\n> doing this process from R:\n>\n> https://github.com/ropensci/ropkgs (reads from the registry below, and\n> other stuff)\n> https://github.com/ropensci/roregistry (idea was to keep a machine\n> readable json registry of ropensci pkgs)\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/ropensci/onboarding/issues/4#issuecomment-78715797>.\n>\n"}}