week 3 draft

[davanstrien]

@drjwbaker A first draft for week 3. Still some additions to be made/fleshing out. A couple of questions/options:

• how important is it to set up repo and try out commands on people's own computers. Does try.github.io give enough scope for trying things out alongside a couple of cheat sheets as handouts?
• Is it useful to make a new template for library carpentry for a Github page or is it better to use an existing one?
• should we focus on using command line to do git commands or use GUI?
• how much material for hour three. Leave discussion open or introduce some of the suggested topics for discussion.

Will continue to work on this but thought I'd get some input now.

[drjwbaker]

@davanstrien: Great job kicking this off. In order:

• it appears to be essential for Hour Two, that Hour One covers git init and remote setup et al. That said, getting the whole collaboration dynamic nailed down with EVERYONE setting this up could be a pain to manage (remember, this is a big group). My suggestion - not that you have to take it! - is as follows: in H1 use try Git et al. Go through this with people on the screen slowly, emphasising the bits that you think are important (so adapting pre-existing content to the room via a live follow along demo); then in H2 sculpt an exercise where 2 sub-teams in each group collaborate on something. This will mean you have just two machines from each group collaborating in the session, from which they can expand to more group members if all is going well
• Not sure. I've used jekyl-now before, though I found it a bit of a faff. Consider forking and amending the info to fit the session? You will also need to give a range of dummy tasks to pick from: building a bibliography, writing an event listing, maintaining an FAQ, et cetera.
• Week 2 will cover shell, so you should be able to do command line without a problem (though keep in mind folks may have forgotten some of what they learnt from W2 to W3, so will need to gently reintroduced...)
• I like what you have for H3. Perhaps aim for H1 & H2 to slip into H3 (with plenty of extra resources for those who worked fast to consult), then give a use case discussion 45 minutes or so? I'd also consider pointing the room to examples of libraries (and comparable orgs) that use Git (and asking them to volunteer their own!) to get everything thinking about what functionality is being used (eg, V&A use it for iterating data dumps, BL Labs for code and data https://github.com/BL-Labs, Gitenberg for crowdsourcing, correction, markup). This way, if the session overruns this can be used as a short summary in conclusion. I guess my point is, make H3 elastic: something that could take 10 minutes or an hour.

And don't forget to add to https://github.com/LibraryCarpentry/week-two-library-carpentry any pre-requisites for week three (sign up to Github?)