We do have http://software-carpentry.org/workshops/previous.html, which links to the sites for most of our past workshops, assuming we ever had a link to a site for a workshop. Not all of those sites are under Software Carpentry's GitHub organization, which is an expected part of the procedure, but so long as people don't delete their workshop repos, links will not go dead. Not all of those workshop pages link to associated lessons, but I think we should make that a standard practice.
Most people don't have permission to create branches in our repos. Daisie, does your proposed workflow work for people who don't have push permissions and want to create a new branch? I don't think I've ever used a PR to create a new branch, so I'm not familiar with what happens. How big of a headache is it to create PRs for all of the lessons someone used? E.g. if they taught five different lessons in a workshop, how much work will it be for someone to open archive PRs for all of those? Especially after having merged everything into a single workshop repo? How is this going to affect the size of our lesson repos? Thanks, Matt On Mon, Mar 9, 2015 at 3:05 PM Daisie Huang <[email protected]> wrote: > Here's my proposed workflow: make a branch on the Github main repo labeled > "yyyy-mm-dd-workshop-name" and make your pull request against that branch. > That way, the repo maintainers can merge it into that archival branch, > without having an open PR that is not meant to merge gumming up the works. > I also made a label "workshop-archive" that would help for locating these > later. > > Daisie > > > Bill Mills <[email protected]> > March 9, 2015 at 2:38 PM > > Big +1 to this from me. > > One thing I've been wondering about lately, is how much of the unique ways > many of us teach the SWC material is making its way back into the > repositories. Personally, there are plenty of times when I do things a bit > differently, but am not totally ready to suggest we change the 'canonical > lesson'; branching like Daisie suggests lowers barriers to putting ideas > out there, and seeing what everyone else thinks. > > -- > Best Regards, > Bill Mills > Community Manager > Mozilla Science Lab > > Daisie Huang <[email protected]> > March 9, 2015 at 2:32 PM > > Hi all, > > I've just finished helping teach my first workshop: along with Tiffany > Timbers, I taught the version control lessons at the March 5-6 workshop at > UBC in Vancouver. I noticed, when preparing my materials, that it seemed to > be common practice to mix and match the lessons from the ones on the main > repo, but I couldn't find any reference to previous materials/versions that > other people had used to teach previous workshops. In addition, I added > some diagrams and writeups that I'd written and found helpful in other > contexts to my lessons, but I don't yet feel comfortable making a case for > those changes to be integrated into the main repository. I'm sure this must > be true for other instructors as well! > > In addition, people would refer to previous workshops they'd attended and > what was taught there, but if those materials weren't part of the main > lesson, I have no idea how to find them...I don't think they exist anywhere > central? It would be nice to have a record of what lessons were taught at > what workshops so we can all look at and refer to them, wouldn't it? > > To that end: I have a suggestion. For each lesson topic repo, wouldn't it > be nice to submit, after a workshop, your custom lessons via a pull > request, one that is not actually meant for merging directly? That way, > we'd have an archive of what was taught where, a discussion location for > instructors to leave notes about what did or did not work, and a place for > us to find (and pull, if we want) the changes that we've made for various > workshops. > > To demonstrate, I made one for the git lessons Tiffany and I taught: > https://github.com/swcarpentry/git-novice/pull/62 > > Daisie > > > -- > Sent with Postbox <http://www.getpostbox.com> > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists. > software-carpentry.org
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
