Hi Belinda- I'm more confused than I was, because now we have different members of the SWC/DC leadership (steering committee members and employees) saying things that are in opposition.
In any case, from the instructor training materials <https://carpentries.github.io/instructor-training/20-carpentries/>: *A Software Carpentry workshop must include lessons on version control (e.g. git), the shell, and a programming language (e.g. R or Python).* *A Data Carpentry workshop must include a Data Carpentry lesson on data organization and three other modules in the same domain from the Data Carpentry curriculum.* *Within these guidelines, there is flexibility in which episodes of the lesson you cover, which exercises you use, and whether you include optional materials (e.g. callouts) and optional episodes.* In either case, this is something that needs to be clarified ASAP, since it sounds like instructors might be getting inconsistent guidance on what can and cannot be included in a lesson. I think the guidelines should allow for flexibility where possible. Even if you do teach the SWC Python lesson module, for example, there's no guarantee that you'll get all the way through command line programs. I'm not disagreeing on the branding issue, but I think that we need to balance that carefully between instructors meeting the needs of their learners and consistency of our branding. --a On Fri, Oct 20, 2017 at 8:18 PM, Belinda Weaver <[email protected]> wrote: > Hi everyone > > I just want to weigh in on this as I am responsible for starting this > thread in the first place when I asked about teaching R in this post: > http://lists.software-carpentry.org/pipermail/discuss/2017-October/005510. > html > > While some people might like the DC R lesson better, I feel it is > important to teach the workshop we advertised, i.e. a Software Carpentry R > workshop that will be using the R Gapminder lesson. > > If a workshop is branded Software Carpentry, then our expectation is that > it will include the shell, version control and either R, Python or MATLAB. > If a workshop does not include those three elements, then it is not really > able to be branded Software Carpentry. > > It can be called 'Based on Software Carpentry", "Inspired by Software > Carpentry" etc if it doesn't include those three elements, or if you are > using extensive personal/local adaptations of our lessons, but a Software > Carpentry workshop must teach shell, git and a programming language to be > the real deal. > > I just wanted to clarify this in case people were not aware of it. > > regards > Belinda > > Belinda Weaver > Community Development Lead > Software and Data Carpentry > e: [email protected] | p: +61 408 841 882 <+61%20408%20841%20882> | > t: @cloudaus > > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/listinfo/discuss >
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
