Meeting agenda for July 28th, 2026

This week’s meeting will be held on Tuesday, July 28th, 2026, at 07:00 UTC. The meeting will be held on Slack, in the #training channel. 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 incorporate these asynchronous conversations as well.

This week’s meeting will be hosted by @sumitsingh.

1. Intro/Welcome

Welcome to all the new teammates who joined the Training Team this week!

2. News

1. Meeting Note Takers
   • July 28th – @pravin1996
   • Aug 4th – @mohkatz
   • Aug 11th – @andrewssanya
   • Aug 18th – @sibokul
2. Looking for feedback
   • We are also planning an Office Hours session for August 22, 2026:
     • Topic: Note-taking and publication workflow: Who does what, and how?
       • More details are available here: https://github.com/WordPress/Learn/issues/3570
     • We have also reviewed several GitHub issues related to Office Hours. You can view all open Office Hours tickets and share your suggestions here: https://github.com/WordPress/Learn/issues?q=state%3Aopen%20label%3A%22Office%20Hours%22
   • We have discussed starting a regular GitHub triage meeting, but this has not yet been confirmed.
     • Proposed schedule: Triage Squad GitHub triage – biweekly on Thursdays at 07:00 UTC.
     • Please let us know if you would be interested in joining this Slack meeting if we decide to move forward with it.
     • https://github.com/WordPress/Learn/issues/3535. Big thank you to everyone who has shared feedback so far!
     • We’re actively updating the Training Team handbooks, and there’s still time to contribute. If you have any suggestions, improvements, or ideas, please share them – we’d greatly appreciate your input: https://github.com/WordPress/Learn/issues/3447
3. Looking for volunteers
   • We need your help in finding all the content that could be updated and consolidated. We would love to have two groups of volunteers – one that will go through all the handbook content, and one that will check the courses. Please state your interest, and we will help you organize and start working on these important issues.
   • Also, we started working on creating thumbnails for all lessons that need them. You’re very welcome to join us and contribute to this important and creative project. Here’s the issue with details on how to work on the remaining thumbnails:
     https://github.com/WordPress/Learn/issues/3428
   • We currently have around 555 open issues, and I think it would be more effective to divide them into smaller categories and work through them one by one.
     • We can start with a simple label that is suitable for everyone to review. My suggestion is:
       • Going through issues one by one
       • Identifying outdated or irrelevant issues
       • Suggesting fixes or next steps
       • Adding comments where needed (before closing or updating)
       • We labeled some of the issues as Good First Issues – if you want to start contributing, this is your starting point. Just go and find issues labeled as Good First Issue, particularly those that have Feedback in the issue title – help us verify them, and you will earn the Training Team Contributor badge in no time. Just follow this handbook article –https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/#validating-content-feedback-issues
     • For the upcoming sessions, I am proposing that we divide the open issues into smaller groups and work through one category at a time. This should make the process more organised and easier for everyone to participate in.
       • We could begin with: [Content] Needs Translation Reviewer – https://github.com/WordPress/Learn/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BContent%5D%20Needs%20Translation%20Reviewer%22
     • However, I would appreciate your suggestions on which category would be the easiest and most useful for everyone to start with. Other available categories include:
       • Issues without a label
       • Awaiting Triage
       • [Content] Feedback
       • [Type] Bug
     • Please share which category you think we should review first. Once selected, we can divide the issues and work through them together, one by one.
     • Let’s work together to clean up and keep the repository well-organized
4. Updates from last week’s Triage Squad session
   • We are planning to start, so if you would be interested, then comment or join the #Training team channel on WordPress Slack
5. Other announcements and news
   • We successfully hosted our Office Hours session on 26 July 2026 and had a productive discussion covering many valuable topics and ideas. A big thank you to everyone who attended and contributed: @rfluethi, @sumitsingh, @sibokul, @vasantrajput, and @andrewssanya
   • The Learn WordPress website is now 100% translated into Marathi! 🎉 You can explore the Marathi version here: https://learn.wordpress.org/?locale=mr. A big thank you to @makarand  & everyone who contributed to reaching this milestone.
   • We’re Looking for WCUS 2026 Contributor Day Table Leads! If you’re planning to attend and would like to represent the Training team, or know someone who would be a great fit, please submit a nomination. We’d love to have you join us!
   • Training Team Monthly update for June is published – https://make.wordpress.org/updates/2026/07/05/training-team-update-july-5th-2026/
   • How to Bring Your Community to Make WordPress Slack?
     https://make.wordpress.org/community/2026/06/09/how-to-bring-your-community-to-make-wordpress-slack/
   • WordPress Campus Connect Kishoreganj 2026 was held at Kishoreganj Polytechnic Institute. We’ve created 70+ websites to give hands-on experience to students.
     https://events.wordpress.org/campusconnect/2025/kishoreganj/

2. Come and Contribute

• Content ready for review
  • See Guidelines for reviewing content when reviewing content.
    • We have 9 issues ready for review
• Feedback awaiting validation
  • See Validating and Applying Content Feedback for step-by-step guidance on validating feedback.
    • We have 47 issues that require validation
• Topics awaiting vetting
  • See Vetting Topic Ideas for step-by-step guidance on vetting topic ideas.
    • We have 2 issues that require vetting
• Validated feedback awaiting fix
  • Contributors, see Validating and Applying Content Feedback for step-by-step guidance on applying feedback that has been validated.
    • We have 25 issues awaiting a fix

3. Contribution Acknowledgement

• Badges awarded:
  • No badges awarded this week

4. Project updates

• Building on the momentum of our last learning cohort (Block Theme Development Course cohort), we are excited to launch our next cohort focused on Plugin Development this month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem.
• Also, we are excited to launch our next cohort focused on Plugin Development next month. We look forward to helping more students expand their WordPress skills and explore new opportunities within the open-source ecosystem.

5. Upcoming Online Workshops

• No workshop scheduled for this week.

6. Contributor 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 contributors or Training Team members help you in some way?

7. Open Discussions

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

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.