This meeting followed this meeting agenda in GitHub. You can see conversations from the meeting in this Slack Log. (If you don’t have a Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. account, you can set one up.)
Introductions and Welcome
There were 26 attendees @bsanevans, @piyopiyofox, @jagirbahesh, @lada7042, @gmrafi, @digitalchild, @huzaifaalmeabah, @freewebmentor, @sumitsingh, @zeelthakkar, @voboghure(async), @dextorlobo(async), @west7, @rfluethi(async), @amitpatelmd(async), @devmuhib(async), @psykro(async), @ironnysh(async), @cnormandigital(async), @sakibsnaz(async), @webcommsat(async), @mobarak, @zoonini, @sierratr(async), @ardianimaya(async), @backpocketACE(async)
Welcome, to all the new contributors who joined the Training Team’s Slack channel in the last week:
@moltilearn8, @azizozbek, @aleenak19, @wpfy, @arunshenoy99, @rinkuiihglobal, @jinalparekh, @manishakhileri, @hazeldrio, @josevarghese, @grahambb, @estelaris, @redfra7, @sparklabs, @newyorkerlaura, @lcf, @manoel910, @brettface, @davidfcarr, @yuriykovalenko, @naveedalam, @nicolaemorosan2, @rahmatgumilar, @tsherk86, @soie7
For those who are new here, the WordPress Training Team helps people learn to use, extend, and contribute to WordPress through educational content hosted on Learn.WordPress.org.
If you haven’t seen them yet, then I recommend checking out our onboarding program, and our Guide Program
News
- Note takers, please remember to wait until the Tuesday following the meeting to publish the notes. This allows team members time to read and provide asynchronous comments.
- After publishing the notes, please comment in the meeting agenda’s GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issue with the link to the notes and then close the issue.
- Here is our current note taker roster.
June 20 – @Jagir Bahesh
June 27 – @Arun Sharma
July 4 – @Zeel Thakkar
July 11 – @Kruti
Looking for feedback
- Training Team 2024 Half Year Review is out!
Let’s celebrate another 6 months of goals and projects accomplished! Please read through the post and share any additional thoughts in the comments.
- Do we need a separate LearnWP Topic Vetting board for vetting topics?
The team’s dynamics have changed since then, so let’s reevaluate. What is the value of having a dedicated board for topic vetting? Could we add back a column at the left of the LearnWP Content- Development board for issues waiting vetting?
- According to @bsanevans Last year, SMEs struggled to find relevant issues to vet due to all topics being in a single column, leading to a backlog of 100+ issues. The topic vetting project board, with its category The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. tabs, made it easier for SMEs to locate their issues.
Now, only 5 issues are waiting to be vetted, a significant improvement from last year. This change allows us to consider reverting to a single column in the content development project board. The backlog was primarily due to Training creating many new issues per release, but this process has paused, making the vetting board more manageable.
- @piyopiyofox closed all Lesson Plans and Tutorials unless requested to be converted into a Lesson. The team could benefit from an editorial calendar for release-related content and a general checklist to vet other content for relevancy and priority.
- @webcommsat consider using the Dev Blog model for idea planning and discussion, though the emoji thumb voting might not work due to more people involved in training. Using GitHub for planning could be effective. We can filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. the existing board for ideas and adapt some Dev Blog practices for training. This could also aid in cross-mapping and linking published items, which is increasingly important. I already consider training when reviewing new Dev Blog ideas and posts.
Looking for volunteers
At WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. EU’s Contributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., the team began creating thumbnails for Learn content, but many more are needed. @zoonini is hosting an online workshop next week to continue this effort. Click the link above to sign up and join the Thumbnail-a-thon!
Updates from last week’s dev-squad triage session
Last week, @psykro and @digitalchild triaged the following bugs
Other News
- As there has been consensus around the proposal put forward two weeks ago (Slack thread) to retire the Faculty program, we’ll be moving ahead as discussed.
- @zoonini will be leading this transition and will let the team know of next-steps soon.
- As of today, we’ll be closing the Faculty application form.
- New team meeting section – “Contributor Updates”.
Although the Faculty program is ending, the “Faculty Updates” section in team meetings has been valuable. We want to continue this tradition and invite all training team members to share their current issues or projects.
- Starting next week, the “Faculty Updates” section will be renamed “Contributor Updates” and all 2,655 Training Team members are invited to share their updates.
- @piyopiyofox has been cleaning up the Topic Vetting Board by closing non-Lesson, non-Learning Pathways, and non-Online Workshop issues. We will next close similar issues in the Content Development Project board.
- Suggestion to pause new Tutorial Presenter applications.We’re temporarily closing the Tutorial application form due to spam. We’re focusing on updating the content creator application process while keeping the Online Workshop facilitator application form open for vetted submissions. Please share any questions or thoughts in the threads above.
Contributor Acknowledgement
- Props: @cnormandigital For won the Kim Parsell Scholarship by the WordPress Foundation.
- Props: Special thanks to all the contributors who created thumbnail graphics for the new Learn WordPress site during and after WCEU Contributor Day. A particular shout-out to @sumitsingh and @bsanevans!
- Props: @agiljulio for his work on creating the final video lessons for the Beginner developer learning pathway.
- Props: @ironnysh for all her excellent reviews.
- Props: @cnormandigital for her continued work on the theme developer pathway.
- Props: @digitalchild for joining dev-squad live from WCEU.
Project Updates
Open Discussions
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.
#learn-wordpress, #meeting-recap, #training, #training-team
