On Friday, July 1, 2022 18:00UTC, there was a meeting to discuss the needs and goals for GitHub automation. Outlined below are the notes taken from the call.
Attendees
@courane01 @azhiyadev @piyopiyofox @courtneypk
Notes
- Board overview (LearnWP Content Development)
- There has been a review process in place since early 2014.
- Instructional Design review
- Instructional Designers assess objectives, and assessment questions.
- Proofreading/grammar and style guide review.
- Are instructional designers the only ones running reviews?
- Instructional Design Experts role description from the team handbook.
- Instructional designers should help identify what objective statements should be, e.g.:
- Is this quality instruction?
- Do we have good questions?
- The Training team (any training team member) comes in on the ready to create columns.
- Original brainstorming doc (Miro board)
- Author permission is required on Learn to add a draft.
- GitHub flow (Miro board), discussed possibly back in January or February.
- GitHub Workflow (Google doc). This pulls out the current checklist that we have and the column it applies to.
- “Awaiting triage” tag
- This means that the issue needs to be moved to a new column
- Hopes for automation
- The desire is to match up reviewers (i.e., copy editors)
- Ideally, create a group ping for copy editors
- To help mitigate ping fatigue, folks can silence certain pings
- Ideally, create a group ping for copy editors
- When a card is moved into a specific column, an automated ping/comment will be added to the card which will ping a group of volunteers to take action.
- When a card moves into the “Publish’ column, it should automatically close.
- The desire is to match up reviewers (i.e., copy editors)
Action Items
- If you are experienced in creating YML files to programmatically create GitHub Actions and Automations, we’re looking for volunteers! Please let us know in the comments if you’d like to help.