carpentries / carpentries/instructor-training

Official Carpentry workshops (covering the full curriculum) vs partial

Open
#1,234 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
189
Forks
301
Avg merge
2d 12h
Merged PRs (30d)
9

Description

In the IT material, it says that "You may only call a workshop a Data Carpentry, Library Carpentry, or Software Carpentry workshop if: it covers the core topics (see below)...".

Hosts/instructors are now also asked to report Carpentry workshops that cover only a part of the curriculum as 'mix & match/circuits' and they typically use the Carpentry workshop template and branding in these cases (which then breaks these rules we teach people at IT).

This is in conflict with the text in the IT material and needs clarifying. This seems like a policy decision that then needs to be consistently reflected in all channels.

This came up in the Instructor Training @steve-crouch and I are doing at the moment (https://anenadic.github.io/2021-03-16-ttt-ssi-online/). The official advice is to say that such workshops are based on Carpentry materials rather than official Carpentry workshops but perhaps we'd like to encourage people to report and advertise such workshops as Carpentry workshops as it gives more credit to the Carpentries and the community and also it is about brand recognition (people now recognise the name 'Carpentry' and 'Carpentries' and if workshops are advertised as such (even of they cover only a part of the curriculum) they perhaps attract more people. In any case, as mentioned, this is a policy decision but wanted to flag it up here.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the quoted IT material and the linked Instructor Training page to identify the conflicting workshop terminology. This needs an agreed policy decision before the wording can be updated consistently across the affected channels; done means the policy is decided and the guidance no longer conflicts.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.