On Mon, Mar 9, 2015 at 3:48 PM W. Trevor King <[email protected]> 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. > > Especially after having merged everything into a single workshop > > repo? > > Hmm, if folks are *merging* the lessons into their workshop > repository. I'm not sure how to track how folks have been using the > v5.3 lessons, but I was imaging them linking (via HTML/Markdown) > instead of merging (via Git). I don't see notes about either approach > here [1]. > Yeah I'm not sure what people are doing here either. Daisie, what was your procedure? (Since you heavily modified the lesson.) > 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
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
