Meeting Agenda April 18, 2024

[Piyopiyo-Kitsune]

Training Team meetings start at 00:00 UTC weekly on Thursdays. Anyone is welcome to contribute to the meeting by commenting in Slack threads during the meeting and throughout the following days. Meeting notes will be published by the following Tuesday to also incorporate these asynchronous conversations.

This week’s meeting will be hosted by @Piyopiyo-Kitsune.

1. News

1. Meeting Note Takers

• April 18 – @Arun Sharma
• April 25 – @Sancastiza
• May 2 – @Jagir Bahesh
• May 9 – @Tapan

2. Looking for feedback

• Looking for feedback: Thumbnails for the Learn redesign - Please take a moment to generate thumbnails using the provided template and provide your feedback in the comments by April 19th.
• Adding a new workflow to categorize published work -- Ben proposes setting up a workflow so that content creators would type //published to close a published issue, rather than press close. The workflow could do the following:
  • Add a new [Content] Published label
  • Remove [Content] Needs Co-host label (← this has been an outstanding request)
  • Close issue

With this new workflow, we’d then be able to filter out issues with the new [Content] Published label as those that were actually completed

3. Looking for volunteers

• We need help with reviewing lessons. If you know anyone who might want to contribute. Reviewer application Let us know.

4. Updates from last week's dev-squad triage session

Attendees: @devmuhib, @huzaifaalmesbah, @mebo

• Worked with 4 PR.
• Triaged 3 GitHub issues.

I would also like to discuss about this issue related to accessibility. Need insights from other team members that will help to increase accessibility of Learn WordPress website.

5. Other news

• WordCamp US speaker applications are now open -- we are here to help folks Speak at a WordCamp or Meetup About the Training Team and Learn WordPress

2. Come and Contribute

Content ready for review

• See Guidelines for reviewing content when reviewing content.
• We have 17 issues ready for review

Feedback awaiting validation

• See Validating and Applying Content Feedback for step-by-step guidance on validating feedback.
• We have 24 issues that require validation

Topics awaiting vetting

• See Vetting Topic Ideas for step-by-step guidance on vetting topic ideas.
• We have 31 issue that require vetting

Good first issues for developers

• See Developing Learn WordPress for instructions on contributing to the Learn WordPress code.
• We have 15 issues that need to be worked on

Validated feedback awaiting fix

• Faculty Editors, see Validating and Applying Content Feedback for step-by-step guidance on applying feedback that has been validated.
• We have 16 issues awaiting a fix

3. Contribution Acknowledgement

• Props:

4. Project updates

• Project Thread: Learning Pathways on Learn WordPress
  • Last update was on April 5 -- there are some thumbnail redesigns occurring and this work is almost complete.

5. Faculty Updates

• What have you been working on and how has it been going?
• Anything you’ve accomplished since the last meeting?
• Do you have any blockers?
• Can other Faculty or Training Team members help you in some way?

6. Open Discussions

If you have topics you’d like discussed in the meeting, please leave them as a comment on this issue.

---

You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, then come walk through our onboarding program to get to know the team and how we work. And if you have questions, feel free to reach out in the #training Slack channel at any time.

[voboghure-dev]

Hi @Piyopiyo-Kitsune I would like to volunteer as a note taker for May 9th. My wp.org user name is, voboghure

[devmuhib009]

Dev-squad meeting notes updated.

[jonathanbossenger]

I'm not sure where best to surface this, but this article on Pa11y, an open source automated accessibility tool, was shared with me recently.

https://opensource.com/article/23/2/automated-accessibility-testing

It might be useful to see if we can integrate this into the Learn WordPress codebase, to automatically check for a11y issues.

However, since we'll be working with a brand new Learn WordPress design/theme soon, it might only make sense to implement it during that process.

[dextorlobo]

Meeting recap published here: https://make.wordpress.org/training/2024/04/24/training-team-meeting-recap-18th-april-2024/