Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Update list of lessons you're comfortable teaching #1513
Current list of options:
This includes lessons we don't maintain (like swc/regex, swc/svn). It does not include lesson variations (like listing just swc/python even though there are two Python lessons in Software Carpentry's offerings). This does not include any Library Carpentry options. It also includes only a limited number of Data Carpentry lessons.
How specific does this need list of options need to be? Listing every lesson across all lesson programs would mean listing about 50 options (and list will continue to grow). Do we need to know just that they can teach Python, or do we need to know what Python lesson(s) across what lesson program(s)?
How much do we need to know to be able to recruit instructors to teach workshops? Why else do we need to know this information?
This was referenced
Jun 24, 2019
@ErinBecker and @fmichonneau Your perspective from a curriculum development team would be much appreciated. What reporting do we want to do, so we can do things like say X number of our Instructors are qualified to teach Y curriculum? This also relates to #1338 -- how do we identify what lessons/curricula our Instructors are qualified to teach?
@sheraaronhurt Your perspective from a workshop admin perspective will also be very useful. What do you need to know to recruit instructors for a workshop?
Which of the following applies to when you want to see this fixed?
referenced this issue
Jun 24, 2019
Two more cents from me: I still like the idea of splitting lessons into two lists: technologies (e.g. Python basics, Python Data Visualization, Git, R, OpenRefine, SQL, etc.) and curricula (what we already have: "dc-ecology-python", "dc-ecology-r", etc.), see #1409 (comment)
If at one point we are able to relate technologies with curricula, then for example we'd be able to find Python-teaching instructors in close proximity who could assist with DC-Ecology-Python workshop even though they didn't select DC-Ecology-Python on their list of curricula they feel comfortable teaching.
Additionally the list of technologies could be reused in workshops that use only part of DC/SWC/LC curriculum (the mix and match option), although I think in this case this list should be extensible.