On Mon, Mar 09, 2015 at 10:56:03PM +0000, Matt Davis wrote: > On Mon, Mar 9, 2015 at 3:48 PM W. Trevor King wrote: > > On Mon, Mar 09, 2015 at 10:17:55PM +0000, Matt Davis wrote: > > > Not all of those workshop pages link to associated lessons, but > > > I think we should make that a standard practice. > > > > And even if they did link to the associated lesson, we're > > currently missing a way to show the rendered content of that > > lesson (e.g. swcarpentry/git-novice) as it was taught. I'd > > recommend we cut versioned releases of our lessons, so folks can > > link to (for example) > > https://swcarpentry.github.io/git-novice/v1.2.3/. That's also > > useful for making sure the lesson doesn't change under your feet > > the day before you teach from it ;). > > I'm up for this, though we may want to use a Subversion-like > revision number (or just the date). I don't know how to apply > semantic versioning to a lesson.
It looks like there are already issues for versioning the lesson-template [1] and downstream lessons [2]. > > > How is this going to affect the size of our lesson repos? > > > > It won't effect their size (so long as you don't merge the PRs), > > Daisie did merge her lesson: > https://github.com/swcarpentry/git-novice/pull/64 If you aren't comfortable with the size increase, you can just delete the branch she created. The PRs (swcarpentry/git-novice#62 and swcarpentry/git-novice#64) will still have her branch. It will also live in her repository unless she decides to delete it there. Even if you delete the branches from both swcarpentry/git-novice and daisieh/git-novice, I think GitHub keeps copies of the branch for the pull requests (but someone may want to check that). The only difficulty in that case would be if Daisie recycled her ‘ubc-wis’ branch name and pushed other content to it (which GitHub would interpret as updating #62 and #64). Cheers, Trevor [1]: https://github.com/swcarpentry/lesson-template/issues/76 [2]: https://github.com/swcarpentry/lesson-template/issues/62 -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
