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.)
This meeting was held in the AMER/EMEA time zone.
Introductions and Welcome
There were 16 attendees: @lada7042, @sumitsingh, @webtechpooja, @chaion07, @mjaragon03, @courane01, @eboxnet, @robinwpdeveloper, @faguni22, @onealtr, @west7, @piyopiyofox, @ardianimaya, @psykro, @nahidsharifkomol, @jominney
We’ve had several new people join the channel recently. What is your interest in Learn/Training and what do you enjoy outside of WordPress: @jengodin, @ninianepress, @mharoonw12, @smaris, @anthony1015, @acchan, @Noruzzaman
Meeting recap notes are one of the best ways to get started contributing to a team, and you can find details on how to write notes in this handbook page.
Looking for feedback
Looking for volunteers
- Creating guiding documents / advising on accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) – Looking for a volunteer, who can work on a handbook page that has an accessibility checklist that can be used by content creators, editors, and meetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. note-takers.
- Join the dev-squad triage sessions held every Thursday at 07:00 UTC in the #meta-learn channel.
Updates from last week’s dev-squad triage session
Win! All current open PRs have been triaged.
See our Guidelines for reviewing content to review the following content.
- How can we make Training Team meetings more engaging and less about reporting?
– What topics/conversations would you like to share in each weekly meeting?
- Two cents from @jominney
- Some things other teams have done that I’ve seen helpful:
- ‘check in’ section where team members can share what they are working on or have recently completed.
- ‘ask for help/I’m stuck on…’ section where team members can ask any not-so-silly questions they have.
- Something I personally would love to see because there isn’t great communication between a lot of teams
- Does anyone have any relevant news they’d like to share from other teams that would be helpful for the training team?
- For example, Milana from the docs team recently did a bunch of work on automation in 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/ that @Ben Evans is now looking into as a way to improve our processes too. There is also a lot of work happening with the contributor mentor program that will be relevant to our team.
If you have topics you’d liked 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.