IT Curriculum Issue Curation

[brownsarahm]

Moving this to a new issue to be handled in conjunction with developing meeting policy/procedure or other creative community building instead of making it required in the IT Curriculum Maintenance Policy.

2 trainers, 1 to handle issue curation and 1 to handle the technical fiddly stuff of merging and whatnot. Specifically, the issue curation trainer should be expected to create issues as they come up in debriefs and generally have their fingers on the pulse of trainings -- which is more than enough work for any volunteer.
Originally posted by @Denubis in #126 (comment)

I really prefer to have issues submitted by people who originate ideas and often ask people to do this when things come up in meetings. However, a) this doesn't always happen and b) there are sometimes broader patterns that aren't just one person's idea. I'm realizing that there are things on my priority list that don't have issues at the moment, so I have to admit there would be a value in having someone with the designated responsibility to be sure that problems turn into issues.
Originally posted by @karenword in #126 (comment)