Hello! I just wanted to point to a workshop that uses the WET strategy: https://github.com/rtfeldman/elm-workshop Each step of the lab is in a different directory, rather than branch. I went to a (shortened) workshop presented by a team member, and it was a pretty successful and enjoyable experience as a student.
The advantage would be that there's no need to separate out into a different repo, and you only need to maintain the master branch (albeit with NN different parts directories). For building/CI, packaging and distributing materials to presenters and students, this seems far simpler! The disadvantage as you mentioned, of course, is that the course developer needs to maintain NN different directories instead of NN different branches, and cherry-picks aren't available... I wonder if there's a diff/patch strategy that would be just as effective? Are you thinking of one training-labs repo for all lab-oriented material, or one repo per subject? Having one training-labs repo with many, many branches to be maintained sounds like it would be a huge maintenance burden! Best regards, Ryan On Wed, Oct 30, 2019 at 7:03 PM Dmitriy Pavlov <[email protected]> wrote: > > Hi Training Developers, > > I would like to contribute labs related to Ignite training, initially I've > placed it here > https://github.com/dspavlov/training-ignite > > In this repo there is model application, and each branch contains it's > incomplete state to be completed by student. It is easy to maintain labs > this way, so you can update something in master (completed state) and then > cherry-pick to other branches > master->lab6->...lab1. > > WDYT if we create separate repository for labs (model app)? > > Sincerely, > Dmitriy Pavlov > > PS. It is also possible to do a WET solution and place every class in > separate folder in main repository, but I feel this branch-based & separate > repo approach may be useful,as well: > https://github.com/dspavlov/training-ignite/branches
