{"action":"created","issue":{"url":"https://api.github.com/repos/QuinnPhys/PythonWorkshop-science/issues/3","repository_url":"https://api.github.com/repos/QuinnPhys/PythonWorkshop-science","labels_url":"https://api.github.com/repos/QuinnPhys/PythonWorkshop-science/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/QuinnPhys/PythonWorkshop-science/issues/3/comments","events_url":"https://api.github.com/repos/QuinnPhys/PythonWorkshop-science/issues/3/events","html_url":"https://github.com/QuinnPhys/PythonWorkshop-science/issues/3","id":182395750,"number":3,"title":"Draft outline for lectures","user":{"login":"cgranade","id":31516,"avatar_url":"https://avatars.githubusercontent.com/u/31516?v=3","gravatar_id":"","url":"https://api.github.com/users/cgranade","html_url":"https://github.com/cgranade","followers_url":"https://api.github.com/users/cgranade/followers","following_url":"https://api.github.com/users/cgranade/following{/other_user}","gists_url":"https://api.github.com/users/cgranade/gists{/gist_id}","starred_url":"https://api.github.com/users/cgranade/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cgranade/subscriptions","organizations_url":"https://api.github.com/users/cgranade/orgs","repos_url":"https://api.github.com/users/cgranade/repos","events_url":"https://api.github.com/users/cgranade/events{/privacy}","received_events_url":"https://api.github.com/users/cgranade/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-11T23:00:12Z","updated_at":"2016-10-11T23:17:25Z","closed_at":null,"body":"Following the lively discussion in #1, I'm creating a new issue to split off discussion of the content of the lectures from logistical planning. I think it's worth continuing to talk about what we should and should not cover, but I want to keep that separate from figuring out things like room bookings and catering. Thanks for your help!"},"comment":{"url":"https://api.github.com/repos/QuinnPhys/PythonWorkshop-science/issues/comments/253074981","html_url":"https://github.com/QuinnPhys/PythonWorkshop-science/issues/3#issuecomment-253074981","issue_url":"https://api.github.com/repos/QuinnPhys/PythonWorkshop-science/issues/3","id":253074981,"user":{"login":"cgranade","id":31516,"avatar_url":"https://avatars.githubusercontent.com/u/31516?v=3","gravatar_id":"","url":"https://api.github.com/users/cgranade","html_url":"https://github.com/cgranade","followers_url":"https://api.github.com/users/cgranade/followers","following_url":"https://api.github.com/users/cgranade/following{/other_user}","gists_url":"https://api.github.com/users/cgranade/gists{/gist_id}","starred_url":"https://api.github.com/users/cgranade/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cgranade/subscriptions","organizations_url":"https://api.github.com/users/cgranade/orgs","repos_url":"https://api.github.com/users/cgranade/repos","events_url":"https://api.github.com/users/cgranade/events{/privacy}","received_events_url":"https://api.github.com/users/cgranade/received_events","type":"User","site_admin":false},"created_at":"2016-10-11T23:17:25Z","updated_at":"2016-10-11T23:17:25Z","body":"@Travis-S said (#1):\r\n\r\n> Workshops based on material from the Software Carpentry foundation often have pre-installation instructions for the command line, git, and Python. See here for a list of such workshops. Maybe sending out some of that material beforehand, with a \"in case you wanted to try this on your own\" disclaimer, could be useful?\r\n\r\n> 👍 for this workshop! Some of us at CQuIC are looking to do something similar, and would love to hear how your experience goes.\r\n\r\nThanks for the kind words! Duly noted about Software Carpentry, and I think that's a good point to raise. That said, we're aiming for something a little bit different in this workshop than what SC normally does. In particular, I would posit that many (but not all) physicists have had very little to no opportunity to learn computational skills in their undergraduate careers, meaning that they've had to figure a lot out on their own. There's many physicists for whom following a list of install instructions would be daunting at best and useless at the worst; in either case, we would lose them as students, which would be a missed opportunity to be of service. To address that, I think we need to be on hand to help with *any* installation problems.\r\n\r\nMoreover, I'd like to focus on more maintainable ways of installing software by focusing on package management where applicable (sorry, OS X and macOS users; I don't want to cover Homebrew or similar given the time constraints). With Chocolatey, Windows now has something almost as easy to use as ``apt-get``, which means that with a quick tutorial, we can save a lot of pain for installing (for instance) the MS-official port of OpenSSH and an HTTPS-delivered version of PuTTY (this is only approximately true, see below).\r\n\r\nIf after this, we decide to host a second workshop, I think that puts us in a much better place to recommend pre-workshop installations, as we'd already have working tried and true lecture notes as well as participants from this run of things. At that point, we could list ``choco``/``apt-get`` and ``conda``/``pip`` invocations to get up and running and focus tutorials on more subtle install procedures.\r\n\r\n--- \r\n**NB:** PuTTY is not actually installed using HTTPS by running ``choco install putty``, but the hash of the insecurely-delivered file is verified against an HTTPS-delivered list of checksums, so it's at least better off. I think the compromise of trusting Chocolatey's hash of the insecurely-delivered installer is probably a reasonable one, but I'm happy to discuss further.\r\n\r\nI'd be happy to leave PuTTY behind entirely, but we kind of need Pageant to offer an SSH agent, as the MS port of OpenSSH doesn't offer an agent that works \"nicely\" with Windows-style workflows, being a literal port to the Win32 crypto API. I don't relish the idea of getting robust and understandable instructions for getting the OpenSSH agent working well with modern text editors on Windows."}}
{"actor":{"display_login":"cgranade"}}