Bill, Not sure if you want this kind of thing as an issue on GH or just over email, but a suggestion:
Having a knowledge of git/github that goes only slightly deeper than what we teach in SWC bootcamps, I wouldn't call myself a Git expert by any means. I'm never sure the best way to review a PR locally that comes in to SWC lessons (or any other code for that matter). It is also seemingly more complicated when multiple PRs come in against the same code, where even I may have my own local changes that haven't been merged yet. I believe there was a helpful protocol somewhere in the swcarpentry/bc repo, but I forgot where it is. A discussion of the operational aspects like this would be helpful, depending on your desired scope. Stephen On Sep 29, 2014, at 5:05 PM, Bill Mills <b...@mozillafoundation.org> wrote: > Hey all, > > Just wanted to direct your attention to some content that I'll be pulling > together over the next little while: > https://github.com/mozillascience/codeReview > > I'm building lessons, exercises and content around the idea of code review > for scientists, based on the pilot programs on the same that Mozilla Science > Lab recently supported, research from the broader community, and my own > experience in the wild. > > What's there now are just some super quick & dirty notes, but I'm hoping to > clear my schedule and build some substantial content over the next week, and > beyond; as always, MSL projects are CC-BY, so feel free to remix for SWC or > any other purpose. Pull requests, issues & comments strongly encouraged, > > -- > Bill Mills > Community Manager, Mozilla Science Lab > @billdoesphysics > > > _______________________________________________ > Discuss mailing list > Discuss@lists.software-carpentry.org > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org _______________________________________________ Discuss mailing list Discuss@lists.software-carpentry.org http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
