{"action":"created","issue":{"url":"https://api.github.com/repos/AstroHackWeek/AstroHackWeek2015/issues/21","labels_url":"https://api.github.com/repos/AstroHackWeek/AstroHackWeek2015/issues/21/labels{/name}","comments_url":"https://api.github.com/repos/AstroHackWeek/AstroHackWeek2015/issues/21/comments","events_url":"https://api.github.com/repos/AstroHackWeek/AstroHackWeek2015/issues/21/events","html_url":"https://github.com/AstroHackWeek/AstroHackWeek2015/issues/21","id":109626546,"number":21,"title":"Reorganize","user":{"login":"kbarbary","id":970135,"avatar_url":"https://avatars.githubusercontent.com/u/970135?v=3","gravatar_id":"","url":"https://api.github.com/users/kbarbary","html_url":"https://github.com/kbarbary","followers_url":"https://api.github.com/users/kbarbary/followers","following_url":"https://api.github.com/users/kbarbary/following{/other_user}","gists_url":"https://api.github.com/users/kbarbary/gists{/gist_id}","starred_url":"https://api.github.com/users/kbarbary/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kbarbary/subscriptions","organizations_url":"https://api.github.com/users/kbarbary/orgs","repos_url":"https://api.github.com/users/kbarbary/repos","events_url":"https://api.github.com/users/kbarbary/events{/privacy}","received_events_url":"https://api.github.com/users/kbarbary/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-03T15:01:23Z","updated_at":"2015-10-04T18:40:55Z","closed_at":null,"body":"The repo got a bit messy during the week, so I'm going to reorganize it as such:\r\n\r\n- `day1-data-exporation`\r\n- `day2-big-data`\r\n- `day3-machine-learning`\r\n- `day4-day5-inference`\r\n- `breakouts/...`\r\n- `hacks/...`\r\n\r\nBefore I do, wanted to know what the status of the `bayes-cv` branch is. I assume it should be merged into master? I can move the CV part that was a hack into `hacks`. @drphilmarshall @eggplantbren"},"comment":{"url":"https://api.github.com/repos/AstroHackWeek/AstroHackWeek2015/issues/comments/145372156","html_url":"https://github.com/AstroHackWeek/AstroHackWeek2015/issues/21#issuecomment-145372156","issue_url":"https://api.github.com/repos/AstroHackWeek/AstroHackWeek2015/issues/21","id":145372156,"user":{"login":"drphilmarshall","id":710903,"avatar_url":"https://avatars.githubusercontent.com/u/710903?v=3","gravatar_id":"","url":"https://api.github.com/users/drphilmarshall","html_url":"https://github.com/drphilmarshall","followers_url":"https://api.github.com/users/drphilmarshall/followers","following_url":"https://api.github.com/users/drphilmarshall/following{/other_user}","gists_url":"https://api.github.com/users/drphilmarshall/gists{/gist_id}","starred_url":"https://api.github.com/users/drphilmarshall/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drphilmarshall/subscriptions","organizations_url":"https://api.github.com/users/drphilmarshall/orgs","repos_url":"https://api.github.com/users/drphilmarshall/repos","events_url":"https://api.github.com/users/drphilmarshall/events{/privacy}","received_events_url":"https://api.github.com/users/drphilmarshall/received_events","type":"User","site_admin":false},"created_at":"2015-10-04T18:40:55Z","updated_at":"2015-10-04T18:40:55Z","body":"Yes - please do move the CV stuff into hacks, and don't merge with master.\nReally Joao and I should start a separate repo for that project.\n\nOn Sat, Oct 3, 2015 at 11:01 AM, Kyle Barbary <notifications@github.com>\nwrote:\n\n> The repo got a bit messy during the week, so I'm going to reorganize it as\n> such:\n>\n>    - day1-data-exporation\n>    - day2-big-data\n>    - day3-machine-learning\n>    - day4-day5-inference\n>    - breakouts/...\n>    - hacks/...\n>\n> Before I do, wanted to know what the status of the bayes-cv branch is. I\n> assume it should be merged into master? I can move the CV part that was a\n> hack into hacks. @drphilmarshall <https://github.com/drphilmarshall>\n> @eggplantbren <https://github.com/eggplantbren>\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/AstroHackWeek/AstroHackWeek2015/issues/21>.\n>\n"}}