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 by the repository owner. https://github.com/ triage: Biweekly on Thursdays 07:00 UTC
TL;DR: A survey was conducted among the Training Team Faculty members to gain insights into their experiences and perspectives. Main takeaways are to continue improving documentation, collaboration, and communication. Improvements to Faculty onboarding are also suggested.
As we established last year, a regular check in with all Faculty members was conducted again this year to gain insight into their experiences and perspectives on the Faculty program. This also included asking their estimated amount of contribution hours they could dedicate to Faculty tasks, so we could determine if there is a need to train new Faculty members.
Faculty check-ins were accomplished by sharing a check-in survey with Faculty members. This post serves to share the findings and insight from the survey.
Training Team Faculty at a glance (as of 30 January, 2024):
Number of Faculty members: 37
Number of completed surveys: 27
Faculty roles:
13 Administrators
16 Content Creators
13 Editors
15 Subject Matter Experts (SMEs)
10 Translation Coordinators
*Note: Some Faculty members fulfill more than one role on the team, which is why the numbers add up to more than the total number of Faculty members.
Let’s explore what our Faculty members had to share. Please read on for more details!
Welcome! Please post in the #training channel or reach out to a team member to help you with contributing. Resources to check out our onboarding program, and our Guide Program.
February 1 – @aanchals09 February 8 – need volunteer February 15 – need volunteer February 22- need volunteer
We’re looking for volunteers to take notes each week through the rest of November. Would anyone like to volunteer for the team? Please post in the #training channel
WordCampWordCampWordCamps 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. Asia 2024 Help the team brainstorm contribution ideas Closes January 30.
Call for Hosts!! Who would like to facilitate an Online Workshop this year? Reach out to a team repTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts..
Congratulations to @Benjamin Zekavica for receiving the Training Contributor badge for his German translation contributions. If you would like more information on how you can receive one of the two badges the training team offers. Badge Requirements
Discussion in the thread about the review process. @sierratr question- After completing the third review if you are a faculty member can you move the issue to Preparing to Publish? Comments: @bsanevans– “If you are a Faculty member go right ahead” @psykro – ” I would welcome anyone who moves an item into the preparing to publish.”
@sierratr question- How do we handle reviews that are submitted with the review checklist? Comments: @bsanevans – Suggested pinging the person to encourage the reviewer to use the checklist and re-submit.
2024 goal planning sessions. Just another friendly reminder to add your comments. What are some goals for the training team?
Faculty Updates
Asked faculty to check in and answer the following questions.
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?
Open Discussions
@devmuhib question- Someone has translated several pieces of content, all of which seem to be directly copied and pasted from Google Translate. I have personally reviewed this content and can confirm that the translations are not good in quality and, at times, not readable. Despite multiple requests to modify the content and maintain a certain standard, the issues persist, and the content remains unreadable. What is the appropriate course of action for such translations? @bsanevans had a few suggestions
Raise some specific items in the translation
If in the same timezone, work on a translation together.
@psykro and @bsanevans have added comments on the issue 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 by the repository owner. https://github.com/.
@bsanevans brought up- Faculty members are added to the Learn Content Triage team on GitHub. This gives them access to triage issues, change statuses, and most importantly, check-off boxes automatically added by automation. (More info about this group in this handbook page.)
What do folks think about extending this permission to vetted content creators, too?
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.
Below is my proposal to kick off the discussion. Let’s discuss this in the comments below until February 5th. Team reps will then summarize the discussion by the team meeting that week.
Prioritize Learning Pathways content
The Learning Pathways project is a priority for the Training Team this year, with a scheduled launch for July 2024. Considering the limited number of content creators we have on the team right now, we do not have enough resources to meet that deadline and create a lot of release-related content at the same time.
Proposal around priorities
Continue to prioritize developing Learning Pathways content.
Identify no more than 3-5 pieces of high-impact content related to the release and clearly list these in the team.
Find opportunities to onboard additional content creators who can assist with this content development work.
Modifying 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 by the repository owner. https://github.com/ triaging processes
Historically, Training’s focus during releases has included identifying content needing updates as a result of the release. This has been done by reopening GitHub issues and, if the original assignee is unresponsive, re-assigning issues to new assignees.
As the team has started to track and analyze GitHub data (see Training Team 2023 Year In Review), we’re finding this process of reopening issues and changing assignees skews important metrics that represent team health – such as the “time to close” on an issue. To ensure the team can track and report accurate metrics, I propose the following changes.
Proposal around changes to GitHub triage processes
We should no longer re-open closed GitHub issues to report content needing updates.
Instead, if content needs notable updates, each update should be submitted as a new issue, using the Feedback issue template.
Welcome to another edition of the Training Team’s Contributor Spotlight! In this series, the Training Team introduces you to one of our many valued contributors, and you can learn more about their contribution journey.
Introducing Maya!
Today’s featured contributor is Nadia Maya Ardiani from Indonesia! Maya is a Content Translator for the Indonesian locale, an Indonesian Translation Coordinator, a Faculty team member, and is also currently trying out being a Content Creator!
All about Maya
Maya’s educational background is in English literature, and she began her career as a journalist. Starting from radio, Maya explored many mediums, including magazines and websites. She specialized in music, culture, and regional news, as well as feature writings on people and places. Maya’s fascination for media and communication brought her to various related avenues: media relations specialist, publicist, and public diplomacy officer for a foreign government representative.
However, everything changed when the pandemic hit — Maya had to find another arena that was more flexible in regards to place and time, and that was when she became a content writer in the tech industry. This was the time when Maya learned in-depth about WordPress because she had to write about it. It was quite a pivot, but a step that she is grateful she took.
Maya is currently a content specialist with Hostinger, and interviews people — from Hostinger’s clients to WordPress community members — and writes articles about their expertise and inspiring stories. She also works on social media to boost the performance of their website content.
Outside of WordPress, Maya loves going to live music. She also loves spending time with her friends, reading, experimenting with recipes, watching movies, and exploring the internet for her daily dose of memes.
Maya’s WordPress Journey
Maya has always been drawn to the Internet and its culture, as well as the people who create and use it. She first discovered WordPress during her school years and was struck by its sophistication, even though it didn’t visually captivate her at the time.
Years later, Maya’s job as a tech content writer required her to have a deep understanding of WordPress. She was surprised to find that WordPress had grown significantly, offering exciting customizations and becoming easier to understand. She started exploring WordPress more, attending her first WordCampWordCampWordCamps 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. and contributor dayContributor DayContributor 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/. It was during these experiences that Maya fell in love with the WordPress community, where everyone learns and supports each other.
Maya’s commitment to the WordPress community solidified when she volunteered as an interviewer at WordCamp Asia 2023. Being a part of something that makes the internet more accessible to everyone motivated her even further.
“It’s just so lovely to be involved in something that makes the internet more accessible for everyone.”
First Contributions
Maya’s journey as a contributor to WordPress began with her first contribution to the Polyglots teamPolyglots TeamPolyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. While she doesn’t recall the specifics, she remembers working on some strings related to the current release towards the end of 2022.
With the Training team, Maya made her initial contribution by creating a lesson plan and translating a tutorial. To her surprise and delight, she received news that the tutorial she translated was the first-ever Indonesian translation within the Training team—something she found truly awesome!
Overcoming Challenges
When Maya first began contributing to WordPress, she faced a common challenge—the feeling of knowing very little and wondering if she truly belonged on the Training team. There were moments when she questioned if she deserved to be a part of a team dedicated to helping others learn about the platform. However, Maya discovered a supportive and helpful community within the Training team.
“Everyone is a work in progress, and we’re never alone in the process, so as long as we’re willing to learn, we can learn together with everyone.”
Memorable WordPress Moments
Being welcomed into such a diverse community, even in places where Maya may not see many people who looked like her, has been a great source of joy. One significant moment was when she interviewed Michelle Frechette, who told Maya that it’s important to show up and start doing something even when you feel like you’re one of the minorities, because you might open the door for others who relate to your experience. This conversation inspired Maya and served as a reminder that her participation could create opportunities for others like her. Seeing fellow POC hijabi women participating at WordCamp US 2023 reaffirmed the idea that there is a place for her at the table. This heartwarming encounter boosted her confidence and conviction more than any inclusivity campaign had.
Maya also had incredible experiences at her first local WordCamp and her flagship WordCamp. The local event allowed her to dive into the intricacies of the project, while the flagship event provided her with a whole new scale of WordPress contributor experiences. These experiences fostered a sense of camaraderie with her fellow contributors, and Maya will always cherish those moments.
What advice would you give to someone who wants to get started with contributing to WordPress?
“You don’t have to be an expert to begin contributing. Start with what you have and improve at your own pace can always be a good idea. In the WordPress community, everyone has each other’s back, so don’t be afraid to ask, even though it might feel like a stupid question (it’s totally fine, everyone’s a newbie at some point in life).”
Thank you, Maya, for all your dedication and contributions to the Training Team and to the WordPress Open SourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. Project!
If you are interested in getting started with contributing to the Training Team, please check out our Getting Started guide and/or join the Guide Program to be mentored by an experienced contributor. We’d be happy to have you join us!
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.
Each year, the Training Team takes some time at the beginning of the year to brainstorm goals for the year. We’ll be hosting two sessions next week, so feel free to join either… or both Sessions will be recorded for folks to watch later and anyone can add feedback in the session threads in Slack
Help the team brainstorm contribution ideas for the team to work on at WordCampWordCampWordCamps 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. Asia 2024.
WordCamp Asia is almost here, and Training will be hosting a contributor table at the event. Thank you to our table leads @west7 and @digitalchild for volunteering
The Training Team continues to update and clarify the requirements of applying for a team badge. Jonathan has started a conversation for us to clarify the requirements for code contributions. Please leave your feedback on the post by January 26th
Each week, the team hosts a dev-squad triage session, where they triage website development 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 by the repository owner. https://github.com/ issues. In that process, the squad mark issues they think would be great for first-time contributors to start on.
One of the content types Training publishes on Learn WordPress is – Online Workshops. As we start the new year, we’d like to invite anyone in the team to apply to host or co-host a workshop this year.
Next week’s team meeting will be conducted over a video call and will focus on brainstorming 2024 goals. The call link will be published in the Training channel 5 minutes before the meeting starts. If you’d like to attend with audio only, or just join in on the Slack threads, that would be great, too
Open requests for review
Currently, we have 15 pieces of content in the review stage. That’s exciting! You can find the list of content here:
The team shared different holidays we celebrated over the last couple of weeks.
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.
It has been brought to my attention by the Training Team Reps that the requirements for achieving a Training Contributor Badge for code contributions to the Learn WordPress codebase are rather vague:
You should significantly contribute to the Learn website by adding or modifying features. This would include writing a feature enhancement or fixing a bug.
I would like to suggest that we update those guidelines so that it is clearer what the requirements are to achieve the badge specifically for code contributions.
I propose we update the guidelines as follows:
You have created or reviewed at least 3 pull requests, either bug fixes or enhancements, to be merged into the Learn WordPress codebase. These pull requests need to have also been reviewed and approved by at least one member of the Training Team Faculty or the WordPress MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team.
By replacing significantly contribute with at least 3 pull requests, we make the goal clearer and easier to understand.
By including the requirement of a second review from either a member of the Training Faculty or the WordPress Meta team (which we work closely with to deployDeployLaunching code from a local development environment to the production web server, so that it's available to visitors. Learn WordPress changes and updates), we can ensure that pull requests are reviewed correctly.
Updating code contribution documentation to align with these changes.
It has also been brought to my attention that we have two Handbook page that relate to contributing code to Learn WordPress:
I suggest that we merge the Code contributions page into the Developing Learn WordPress page (possibly replacing the Contributing code section, adding a section on the suggested code review process, and a note on achieving the Training Contributor Badge.
Call for feedback.
What do you think of the suggested updates? Please leave your thoughts on this post by Friday, 26 January 2023.
Sessions will be recorded for folks to watch later and anyone can add feedback in the session threads in Slack
