consider demonstrating checkout activities

[ragamouf]

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.