{"action":"created","issue":{"url":"https://api.github.com/repos/swcarpentry/shell-extras/issues/3","labels_url":"https://api.github.com/repos/swcarpentry/shell-extras/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/swcarpentry/shell-extras/issues/3/comments","events_url":"https://api.github.com/repos/swcarpentry/shell-extras/issues/3/events","html_url":"https://github.com/swcarpentry/shell-extras/issues/3","id":62146179,"number":3,"title":"Define the goals and target audience for this lesson","user":{"login":"wking","id":209920,"avatar_url":"https://avatars.githubusercontent.com/u/209920?v=3","gravatar_id":"","url":"https://api.github.com/users/wking","html_url":"https://github.com/wking","followers_url":"https://api.github.com/users/wking/followers","following_url":"https://api.github.com/users/wking/following{/other_user}","gists_url":"https://api.github.com/users/wking/gists{/gist_id}","starred_url":"https://api.github.com/users/wking/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wking/subscriptions","organizations_url":"https://api.github.com/users/wking/orgs","repos_url":"https://api.github.com/users/wking/repos","events_url":"https://api.github.com/users/wking/events{/privacy}","received_events_url":"https://api.github.com/users/wking/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2015-03-16T16:59:11Z","updated_at":"2015-03-18T11:54:51Z","closed_at":null,"body":"Before we go filling it in with new content (#1), I think we should think about who would be taking this lesson, what we want them to learn, and how we'll advertize those goals to the intended audience.  Maybe this should be shell-intermediate (meaning “what to take after shell-novice”)?  Or shell-multi-host for interactions between hosts (scp, ssh), and shell-posix for the finer details of the POSIX shell and other POSIX-sepecified features (env, alias, job-control, permissions, man).  \r\n\r\nPersonally, I prefer the `shell-{area-you-want-to-learn-about}` approach, so learners/instructors can easily find the material they want.  And lesson listings can organize the by-area lessons into serial curricula as they see fit.\r\n"},"comment":{"url":"https://api.github.com/repos/swcarpentry/shell-extras/issues/comments/82929357","html_url":"https://github.com/swcarpentry/shell-extras/issues/3#issuecomment-82929357","issue_url":"https://api.github.com/repos/swcarpentry/shell-extras/issues/3","id":82929357,"user":{"login":"ChristinaLK","id":4634021,"avatar_url":"https://avatars.githubusercontent.com/u/4634021?v=3","gravatar_id":"","url":"https://api.github.com/users/ChristinaLK","html_url":"https://github.com/ChristinaLK","followers_url":"https://api.github.com/users/ChristinaLK/followers","following_url":"https://api.github.com/users/ChristinaLK/following{/other_user}","gists_url":"https://api.github.com/users/ChristinaLK/gists{/gist_id}","starred_url":"https://api.github.com/users/ChristinaLK/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ChristinaLK/subscriptions","organizations_url":"https://api.github.com/users/ChristinaLK/orgs","repos_url":"https://api.github.com/users/ChristinaLK/repos","events_url":"https://api.github.com/users/ChristinaLK/events{/privacy}","received_events_url":"https://api.github.com/users/ChristinaLK/received_events","type":"User","site_admin":false},"created_at":"2015-03-18T11:54:51Z","updated_at":"2015-03-18T11:54:51Z","body":"(Sorry @gvwilson, you replied as I was typing this up!)\r\n\r\nI would like to see `shell-extras` and `shell-intermediate`, simply because I feel like ssh, scp are \"novice\" level topics, whereas awk and sed are considerably more advanced.  The question is where to divide.  ssh and scp could *also* go in an hpc lesson, if appropriate.  What do people think of: \r\n* shell-extras: ssh, scp, aliases, environment variables, permissions, navigating man pages, (job control?)\r\n* shell-intermediate: awk, sed, job control (including cron), xargs, advanced scripting\r\n* shell-parallel: intro to parallelization, high-throughput + high performance computing, possibly what a scheduler is\r\n\r\nAlternatively, we could divide entirely by theme: soup up your shell, sysadmin tricks, advance scripting, parallelization etc.\r\n\r\nI think another important thing to consider is where/when would these be taught, and to what audience.  I like the idea of shell-extras being little stand-alone chunks that someone could insert into a novice swc lesson as desired.  "}}