amy
amy copied to clipboard
carpentries
Update list of lessons you're comfortable teaching
Current list of options:
dc/cloud dc/python dc/r dc/shell dc/spreadsheets dc/sql swc/git swc/hg swc/make swc/matlab swc/python swc/r swc/regexp swc/shell swc/sql swc/svn
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 issue consolidates questions raised in #1211 and #1409
@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?
I'm trying to categorize things to develop a timeline for working on AMY. I think this is an option 3 issue - but please let me know if you have other thoughs @ErinBecker @sheraaronhurt
Which of the following applies to when you want to see this fixed?
- Would like to see this fixed as soon as possible, in the next 1-2 development cycles (i.e., by September 2019)
- Would like to see this fixed later (by the end of 2019)
- Would like to see this fixed, but possibly as part of a larger project that needs more planning
- Not sure
- No longer relevant - OK to close
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 https://github.com/carpentries/amy/issues/1409#issuecomment-439128301
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.
- Depending on how time intensive it is for @sheraaronhurt to do instructor recruitment, I would like to see this discussed as a possibility for the AMY automation project for this quarter or a similar project in a later quarter.
This isn't time sensitive for me. From the WAT perspective, we look at them having an understanding of Python as a whole, not the breakdown of the specific lessons.
Closing this. We will consider this as part of changes to badging process. This will consider how we give instructors endorsements, contributions, etc. to their badge.