Triage Squad GitHubGitHubGitHub 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/ triage: Biweekly on Thursdays 07:00 UTC
(We have alternated our weekly team meetings according to the timezone. This week we are having the Team Meeting in the APAC timezone, and a Coffee Hour was held in the Americas/EMEA timezone at Tuesday 17:00 UTC.)
Currently, the team posts very similar content on the meeting agenda and recap posts. Team reps are considering how we can streamline this better.
Here are two ideas we’ve had:
Post an agenda in GitHubGitHubGitHub 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/, and publish a recap as a blog post. (This will reduce the number of posts on the blog, too, potentially making it easier to follow the information that gets published there.).
Publishing a detailed agenda on the blog, and writing notable discussions in the comments of the post.
Regarding the above two options, @webtechpooja, @sumitsingh & @courtneypk voted for option 1(idea 1).
➡️ New team update
Each month, Training Team reps publish an update to the entire WordPress project about the progress the team made in the last month. You can read the most recent update here: What’s new on Learn WordPress in March 2023.
New handbook pages
Team reps and faculty members are always updating the team handbook to document team processes better. This week, these two new pages were published:
This new proposal is looking for your feedback by April 7th. Please leave your comments on the post by the end of the week.
News from other WordPress teams
Last week, a new version of WordPress was released – 6.2
Has everyone updated their sites to 6.2 already? What is your favorite feature from the new release?
The best part for @webtechpooja & @bsanevans was site editor BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. label removed. @sumitsingh liked the “Meet the reimagined Site Editor” under 6.2 part. @nomadskateboarding mentioned his favourite part as Style Book.
Announcement: Temporarily relocating on-hold projects from the meeting agenda to GitHub
Until last week, at the end of each meeting, we had a section titled “Other projects” where we would ask project leads for an update. However, some projects move slower than others, and we don’t want to burden folks with excess notifications.
From this week, we will exclude the on-hold projects from the meeting agenda and add them back when they are resumed. You will find a note about these paused projects on the Team’s Administration GitHub board.
Contributor badges were awarded last week
Last week, @esratpopy and @karthickmurugan were awarded Training Contributor Badges for their contribution to hosting Online Workshops, and translating content on Learn WordPress.
3. Creating content for the WordPress 6.2 release
WordPress 6.2 was released last week, and we have a few more items we’d like to get published. You can find all content labeled 6.2 on our GitHub project board. Here are some items we’re still looking for volunteers for.
A syllabus was published last week. Please comment on the post with any comments you have. We’re also looking for folks to help build the content for this syllabus
Jamie produces fantastic content for YouTube, and he’s looking for feedback about whether they’d be a good fit for Learn WordPress, too. Please check out the information in the following GitHub issue, and leave your thoughts as comments there https://github.com/WordPress/Learn/issues/1439
I just wanted to mention that next week Tuesday is the next scheduled APAC @faculty-dev-squad triage session, and he will be AFK. If anyone else in the APAC dev squad wants to lead that session, please let him know, so that I can arrange the relevant announce permissions for the #meta-learn channel. he also noticed that from what he can see the AMER dev squad has not yet been able to hold a triage session, so he wanted to check in with them and see if there’s anything he can do to assist.
@digitalchild also shared an interest to hold next weeks session.
8. Other ways to contribute
And as we come to the end of the hour, I wanted to mention a few easier ways folks can contribute to the Training Team.
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.
New handbook pages
.
