data-lessons/instructor-training

Carpentries SANDBOX for testing changes to instructor training course material

instructor-training's Issues

Broken internal links in "Instructor Checkout" page

Navigation links in "Instructor Checkout" section of "Checkout Process" page are broken. This is lines 23, 24, and 25 in the 14-checkout.md file.

No Amy Form fill?

Noticed that it doesn't have them do a submission to the form for Amy any more as part of checkout. Is this on purpose?

Consider adding links to GitHub repositories for contributions in Checkout episode

In the "Checkout" episode (https://github.com/data-lessons/instructor-training/blob/gh-pages/_episodes/14-checkout.md), there are great instructions on how to navigate issues and pull requests in GitHub, but there isn't yet information on where the repositories are and how to navigate them. Either providing links or giving instructions on how to get to the "Source" from episode webpages would be helpful for learners, since there are quite a few repositories and they might be confusing for those unfamiliar with their structures.

'Choosing our Praises' exercise missing explanation of types of praises

It seems the section that explains the types of praises in the episode "Motivation and Demotivation" was removed in this commit, but the exercise "Choosing our Praises" right after that section asks to identify between "performance-based, effort-based, or improvement-based praise". These are new words with that text removed. Should it be brought back?

I don't see an obvious reason why this was removed. If I'm reading it correctly, the commit says:

#Move these items to References, then link above and delete

Maybe the edit left the exercise orphaned and it needs to be removed too?

Changelog for carpentries/instructor training May 1 - October 31

• Notes:

  • recommendations for co-instructors when teaching online

• Google Drive folder for slides + doc/form templates

Link broken in episode about checkout process

https://data-lessons.github.io/instructor-training/14-checkout/#1-lesson-contributions

In the “Help Wanted: Breaking down Barriers” section, the last sentence of the first paragraph has a broken link. The sentence mentions that there is an extensive discussion on breaking barriers for people who don’t have access to GitHub with no links to this discussion.

I am not sure what should be linked but perhaps the creators would know.

Thank you!

How We Operate update has likely inaccuracies

In particular, it needs feedback regarding branding as it relates to mix-and-match workshops as well as incubator lessons, and all the grey areas in between.

Will seek to resolve some of these on the main repo

an issue that should really be a discussion

a lofty idea

Current PR to carpentries repo does not include deleting episode on mindset,

it has two episdoes numbered 9. wasn't the plan to delete 09-mindset because that content is covered elsewhere?

How about adding resources on the proper use of pronouns? #1222

See: carpentries#1222

Based on carpentries#1237 (comment), I'm cross referencing here and sending PR now.

Referencing a Discussion in an issue (test)<!--

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

Originally posted by @karenword in #44

consider renaming "teaching as a skill" to something with feedback

We received feedback today that the first "Teaching is a Skill" section is more about feedback than it is about teaching skills.

I wonder if we can rename this section to Using Feedback in Teaching or something like that?

flagging issues more clearly

came up in previous discussion: how to flag "high priority" issues (GH sorts by time, which is not ideal) and then communicate that to trainers. Put in README or CONTRIBUTING.

Suggestion to reframe 'Do no harm' section in Motivation episode to positive actions

In 'First, Do No Harm' section in Motivation episode, there is a list of 'don't do this', but can it be reframed by listing positive actions with 'what to do to motivate/engage learners'? Our brain has a negative bias and we may actually do harm by learning those points, such as saying 'just'.
A few example suggestions are:
"Take over the learner's keyboard" -> "Let the learner type"
"Pretend to know more than you do" -> "Be authentic"
"Dive into complex or detailed technical discussion" -> "Always talk to the class with things they have learned"

Missing text, Checkout episode

In the Checkout episode (https://github.com/data-lessons/instructor-training/blob/gh-pages/_episodes/14-checkout.md), there's a section of partial text under the Lesson segment:

…you will not be asked to teach episodes that lack participatory content or that require files or other output from previous episodes. other complications to set up.

This looks like it might be an unresolved note.

Section Titles & Core Outcomes

Three core outcomes that could be considered as guiding principles for this curriculum are:

• It’s about THEM. (not you) Empathize (+that may be difficult)
• Teaching is a skill (learned, practiced, and has evidence-based best practices)
• A first tool for your toolbox: (most likely to be 'Slow Down')

Section titles should, alone, convey a narrative consistent with our desired core outcomes. They should also be easy to read, write on a white board, and should accurately apply to all content in the module.

Proposed changes:
How Learning Works: The Importance of Practice -> something catchy about skill
How Learning Works: Expertise and Instruction -> Expertise and Instruction
How Learning Works: Working Memory and Cognitive Load -> Working Memory and Cognitive Load
Building Teaching Skill: Getting Feedback -> Building Skill with Feedback
Creating a Positive Learning Environment: Motivation and Demotivation -> Motivation and Demotivation

• recommend separating detailed accessibility content into separate section as it is relevant but not entirely described by motivation. Retain references to motivational importance of minding accessibility.

Creating a Positive Learning Environment: Mindset ->

• recommend merging mindset with motivation, as it really is all about motivation.

Building Teaching Skill: The Importance of Practice -> Teaching is a skill. Let's practice! (or something shorter)
Building Teaching Skill: Lesson Study -> whatever it is after this lesson is fixed
Building Teaching Skill: Live Coding -> Live Coding
Building Teaching Skill: Performance Revised -> Live Coding II
The Carpentries: Workshop Introductions -> Starting and Ending a Workshop (with ending content).

• recommend swapping introductions with Carpentries Teaching Practices, to close out ed content and allow introductions to draw upon logistics info presented in Operations section

The Carpentries: How We Operate -> This is fine. Could be shortened as "Carpentries Operations"
The Carpentries: Teaching Practices -> Carpentries Teaching Practices. See above regarding move.
Afternoon Wrap-Up -> Create a separate section on Carpentries Instructor Checkout prior to Wrap-up?

sharing feedback should have ready to copy/paste instructions for online teaching

Here: https://data-lessons.github.io/instructor-training/11-practice-teaching/index.html

instructions for online should be ready to copy/paste instead of having to manually tweak the in-person ones.

consider demonstrating checkout activities

I wonder if it is worthwhile for trainers to prepare an example issue in order to demonstrate how to submit an issue for the checkout process? If so, would it need to be included in the curriculum here in episode 14, or an insertion into the Trainer notes .

Last week I walked instructor trainees though the process of submitting an issue, using the screengrabs and pointers provided in the curriculum. However, looking over the feedback and questions raised during the workshop, I realise that the trainees really wanted to know:

1. what is a good quality issue that is helpful, and
2. what kind of change or contribution is worthwhile?

Although I talked about these topics, and gave examples, I didn't show them the whole process in action.

I have a sense that this matches up with a recent discussion in the trainers' slack channel about the difficulty for maintainers of managing pull requests around checkout time, especially ones that are not great quality, or somewhat off the mark. Demonstrating and showing what and how in a live demo seems to me to be a better way of covering expectations surrounding checkout.

Aaaaand, now that I've arrived at the end of this issue, I think the answer for where to put this suggestion is in the Trainer notes page, under section V Curriculum teaching tips. However, I'm interested in other peoples' suggestions for approaching this episode.

HTTPS links

From carpentries#1237

Need to be sure all links are updated to https as appropriate throughout.