add draft trainers meeting guide #310
Conversation
| 1. Coordinate with the Core Team to avoid conflicts with other events. | ||
| 2. Set two meeting times to accommodate global time zones. Times are currently UTC 14:00 and UTC 23:00, on the first and third Thursday of the month. | ||
| 1. Changes to these times and dates should be based on unanimous consensus of the active trainer community. |
There was a problem hiding this comment.
| 1. Changes to these times and dates should be based on unanimous consensus of the active trainer community. | |
| 1. Changes to these times and dates should be based on consensus of the active trainer community. |
Unanimous consensus seems an unlikely target for a community as large as trainers. Guessing that was drawn from core team, which is small. There may be better language for this (or we may want to specify how we recommend asking about times to schedule).
| 1. Announce a call for topics via community channels (e.g., Slack, mailing lists). | ||
| 2. Encourage members to propose topics in the [trainers etherpad](https://pad.carpentries.org/trainers) under the "Propose a Topic" section. | ||
| 3. Collect additional ideas from recent discussions, Slack threads, and survey feedback. |
There was a problem hiding this comment.
| 3. Collect additional ideas from recent discussions, Slack threads, and survey feedback. | |
| 3. Collect additional ideas from recent discussions, Slack threads, survey feedback, and [active issues](https://github.com/carpentries/instructor-training/issues) in instructor training. |
| - **Responsibility**: TLC with input from the Trainer community. | ||
| - **Process**: | ||
| 1. Review proposed topics from the etherpad and prioritize them based on community interest and relevance. |
There was a problem hiding this comment.
Either this shouldn't say "from the etherpad" or we should specify in 3. above that the "additional ideas" are added to etherpad. Just be consistent.
| - Pre/post-training discussions (for the first monthly meeting). | ||
| - Community announcements. | ||
| - A "topic of the month." |
There was a problem hiding this comment.
Is topic of the month primarily for 2nd meetings? I haven't been able to go for a while, but if that's the case, we should specify (like line 33 does for pre/post).
| - Community announcements. | ||
| - A "topic of the month." | ||
| 3. Publish the finalized agenda on the etherpad and community channels. |
There was a problem hiding this comment.
| 3. Publish the finalized agenda on the etherpad and community channels. | |
| 3. Publish the finalized agenda on the etherpad and share highlights on community channels. |
Presumably, we won't send the whole agenda out in duplicate through multiple channels? I'd assume we do highlights then link them to the pad for full agenda.
| - **After the Meeting**: | ||
| 1. Submit meeting notes and attendance to the [Trainers repo](https://github.com/carpentries/trainers/tree/main/minutes). | ||
| 2. Add attendance to the Core Team's spreadsheet. |
There was a problem hiding this comment.
Does the meeting host always have access to this spreadsheet and know where it is?
| - Ensure at least one annual discussion to share updates on the Trainer program, as per committee guidelines. | ||
| - Facilitate special meetings for significant changes or decisions requiring trainer input. | ||
|
|
There was a problem hiding this comment.
| - Introduce candidates for trainer leadership with time for Q&A. | |
This is normally an annual part of a meeting in Jan or Feb.
To replace the current outline in the policy directory.