Vote for Training Team Rep 2024

The WordPress Training Team Rep nomination was closed on November 14, 2023. We got some great names nominated as the next Training Team reps. Our two team reps @piyopiyofox and @bsanevans, will be staying for next term, and we need one more team repTeam Rep A 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. to join them.

Once the nomination had been closed, we contacted all nominees and accepted nominations of those who responded positively.

Nominees

A Team Rep is a person who represents the Make WordPress team to the rest of the project, makes sure issues are raised and addressed as needed, and coordinates cross-team efforts. Learn more about the responsibilities of a Team rep. The following Training team members are nominated for 2024:

Courtney Robertson: (PA – North America)
Profile: https://profiles.wordpress.org/courane01/
Timezone: UTC – 5

Jamie Madden: (Vietnam – Southern APAC)
Profile: https://profiles.wordpress.org/digitalchild/
Timezone: UTC + 7

Laura Adamonis: (East Coast – USA)
Profile: https://profiles.wordpress.org/lada7042/
Timezone: UTC – 5

Voting

Training team members are requested to vote to select one Training team reps by online poll in the following link:

Click here to Vote

The voting is open until December 6, 2023.

Results

Once voting is concluded, we will announce the result on December 8, 2023, in the Training team slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.

Thanks to @bsanevans and @piyopiyofox for the peer review.

#team-reps, #training-team

Nomination for 2024 Training Team Reps

In the WordPress open-source project, each team has team representatives, abbreviated as reps. It’s time again to nominate the next round of Training Team Reps. (For a quick refresher of Team RepTeam Rep A 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. roles across the WordPress project, see the Team Reps post on Team Updates.)

The Role

Historically, with the Training team, the team rep duration was around two years, and we had three reps at the time. They represent the team, collaborate with other teams, raise, manage, and address any issues. The time commitment in the role has averaged two to five hours per week.

The Training team has recently updated its documentation, clarifying the team rep role’s responsibilities. Please take a moment to read the handbook page “Team Rep (Representative).”

Clarifications to the Training Team’s Reps Structure

The mechanics of Team Reps vary from team to team. Each team will choose a selection process, the number of years of service, etc., that best serves the team’s needs.

In the handbook updates, this year’s Team Reps ( Benjamin Evans, Destiny Kanno, and Pooja Derashri ) clarified the following points regarding the team rep role. These were things the team had been doing for a while but weren’t well documented:

  1. The team strives to have 3 team reps representing diversity, as evaluated through the Team Values.
  2. Team Reps generally serve for 2 consecutive years, using the first year to get familiar and the second to train the incoming rep(s).

We also clarified with the Training Team Faculty members that with this 2 year guideline, Benjamin Evans and Destiny Kanno will automatically stay on as Team Reps for 2024.

Timeline for Training Team Rep Selection

We will follow the process documented in the team handbook.

Step 1: Call for Nominations

Anyone can nominate a Training team rep! Self-nominations are welcome, too. To nominate someone or yourself, please comment on this post. If you would like to nominate someone in private, please reach out to @webtechpooja, @bsanevans, or @piyopiyofox.

Note that this is Pooja’s second year in the role, and is not eligible for reelection next year. Since Benjamin Evans and Destiny Kanno will be staying on to complete their second year and onboard the newest Training Team Representative, only one Team Rep spot will be filled for 2024.

  • Nomination Opens: 23 October 2023
  • Nomination Closes: 14 November 2023

Team reps will confirm each person nominated meets the vetting criteria at our weekly meeting on November 16th. They’ll then reach out to those nominated to confirm if they would like to accept the nomination. Only those who accept their nomination will be added to the poll, so feel free to decline a nomination if you don’t feel like this is the right fit for any reason.

Step 2: Vote for Team Reps

If there is more than 1 nomination, we will organize a poll to select the Team Reps.

Training team members can vote to select new Team Reps. 

  • Voting Opens: 17 November 2023
  • Voting Closes: 6 December 2023

Step 3: Announce Team Reps

New Team reps will be announced on December 8, 2023. 

Time to Nominate!

Are you ready? It’s time to nominate folks to serve as our Test Team Reps for the new term! If you have any questions, please feel free to ask in the comments.

Thank you, @bsanevans and @piyopiyofox, for reviewing this post.

Note: Comments are closed now.

#nominations, #training-team

Looking for feedback: Updates to GitHub issue templates and labels

Summary: In an effort to streamline the team’s GitHub repo, the Next steps for GitHub updates project is looking to reduce the number of GitHubGitHub 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 templates in the repo from 9 to 5. The project is also looking for input as the current list of 119 labels is reassessed and reduced. Please leave your feedback on the proposed changes by October 17th (Tuesday).

Please review the new list of GitHub issue templates

In an effort to streamline the team’s GitHub repo, the Next steps for GitHub updates project has identified a need to reduce the number of GitHub issue templates. The expected benefits from this change include:

  • Less confusion for contributors creating new issues.
  • Less redundancy during topic vetting. (Currently, Subject Matter Experts (SMEs) must vet the same topic for multiple content types.) 
  • Reduction in quantity and complexity of automations that will get set up.
  • Preparation for the consolidation of content types, as proposed in Looking for Feedback: Learn Website Information Architecture.

Below is a table listing the current 9 issue templates, and the 5 proposed templates they’ll correspond to. Each of the new templates have already been created and can be previewed from https://github.com/WordPress/Learn/issues/new/choose. (Scroll to the bottom of the list, and you’ll see these new templates prefaced with “_do-not-use_”.) Please leave any questions, suggestions, or other comments about these templates below.

Current issue templatesProposed issue templates
Bug Report Template
Content Feedback
Feedback
Topic IdeaContent Development (general)
Lesson Plan Template
Tutorial Template
Online Workshop Template
Course Template
Content Development (for Faculty)
Content Translation TemplateContent Translation
Meeting Agenda TemplateMeeting Agenda

Some points to note in these changes:

  • All feedback pertaining to Learn WordPress, regardless of whether it is regarding the website itself or the content, will be submitted in one issue. Automation similar to what the Docs team has will be set up, allowing any contributor (regardless of GitHub access) to triage and send these to their respective projects where they’ll be actioned on.
  • The current “Topic Idea” template will be renamed to clarify this is actually the issue content creators should use when creating content. These issues will be highlighted to SMEs to be prioritized in their topic vetting process.
  • Faculty who will immediately create content themselves may skip the vetting process. The four content templates the repo currently have are designed for this process, but weren’t labeled as such, and were therefore confusing general contributors. These will be consolidated into a single template marked “for faculty”. Automation similar to what the Docs team has will be set up, allowing Faculty to call the respective development checklist for their content type with a command.

Help us review the current list of GitHub labels

The project has exported the current list of GitHub labels into this Google Spreadsheet. We’re looking for Training Team contributors with experience in labeling issues in the team’s repo to help us document the purpose of each label.

Once completed, the project will:

  • Reassess labels based on their current use.
    • Similar labels may be consolidated.
    • Labels may be renamed for clarity.
    • Some project-specific labels may be replaced with custom fields.
  • Document the purpose of each label in the handbook.
    • Documentation will also include how new labels should be added and which labels are used in automation and, therefore, should not be modified.

Thank you for your feedback!

We’re looking for feedback on the proposed changes to issue templates and documentation regarding the repo’s current list of labels, by October 17th (Tuesday).


@webtechpooja and @jominney were co-authors of this post. Thanks also go to @yuli-yang for exporting the list of GitHub labels for the project!

#feedback, #github

Let’s share our notes from the Community Summit

A handful of folks who regularly contribute to the Training Team attended the recent Community Summit. Anyone can read the official notes from each session on https://make.wordpress.org/summit/. With almost 30 sessions that took place, though, there is a lot of information to consume there.

Training Team reps discussed how it would be great if those who attended the Community Summit could share their observations and learnings that pertain specifically to the Training Team with the team. The goal is to highlight important information to Training Team members who were not at the summit, and may also not have the time to read through the different notes.

  • If you attended the Community Summit: Come leave a comment below with any observations you came home from the summit with that would pertain specifically to the Training Team.
  • If you did not attend the Community Summit: Follow this post from the button below to receive an email notification anytime someone comments.

Anyone is welcome to add questions or additional comments on what other people have written also. Thanks!

#community-summit

Looking for feedback: Learning pathway outlines

The Learning Pathways project is a significant initiative geared towards enhancing the educational experience on Learn WordPress. The primary objective of the Learning Pathways project is to develop and launch dynamic, user-centric learning pathways tailored to diverse learner profiles. By catering to the unique needs of different user groups, we aim to create a more intuitive and effective learning environment on the Learn WordPress platform.

For those who may not have had the opportunity yet, I would like to direct your attention to the Project Thread: Learning Pathways on Learn WordPress, where you can find information about the project’s goals and strategies.

We have started the process of drafting rough outlines for learning pathways intended for Users, Designers, and Developers.

Outlines

  1. Rough outline: User learning pathways
  2. Rough outline: Designer learning pathways
  3. Rough outline: Developer learning pathways

These outlines are a starting point, and we’re excited to get your thoughts and ideas to help shape them further. Please complete the quick feedback form below!

Due date: 15 September

Thanks in advance

WCUS Contributor Day: Tutorials Workshop (In-Person & Remote)

TL-DR – Tutorials are incredibly daunting work–at least, they can be if you’ve never done it before. I would like to demystify the tutorial creation process for interested training team contributors, both for those who attend in-person and with a follow-up remote session for team members who will not be in attendance at WCUS.

Objectives for this workshop:

Contributors will be able to…

Part One:

-Write strong learning objectives and descriptions
-Write tutorial scripts either on their own or through utilizing (and spot-checking) AI
-Revise each other’s work for accuracy and voice

Part Two:
-Utilize technology to record strong screencasts and visuals
-Create video tutorials for learn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/
-Review tutorials for learn.wordpress.org in public (in person and online)

Pre-Contributor DayContributor 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/.Prepwork

1. Generate or identify a list of potential easy (and high value) tutorials people could write, add to the GithubGitHub 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/ repo. TagTag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. them explicitly with “Contributor Day” to allow us to follow up on these topics at a later date.

2. Create a sample website that can be downloaded from our Github repo and installed (using Local or WordPress playground) to save time on people creating sample sites of their own.

3. Create a community repo / Google Drive (for simplicity) to create folders for the resources created for each in-progress tutorial, which will be linked to in each Github issue.

4. Create a dedicated tools list from the handbook page with the specific tech we will be using.

5. Optionally: We could see who might be interested in doing this ahead of time– who may plan to attend contributor day.

On Contributor Day:

Morning Session 

1. Building Background Knowledge – Onboarding Session: Welcome to the team, how we use the Github board for tutorials, join the team for the day (or longer!)

2. Topic selection! Contributors will pick a topic from the list and/or suggest a topic [and get it approved]. We will go over expectations for what and how to write on Github.

2. I Do / We Do / You Do: Once topics have been chosen, we will start by writing our learning objectives and topic descriptions on the Github issues. As an ID, I will walk around and ensure topics are bite-sized and that the objectives are measurable. We will discuss the importance of strong learning objectives and how they help learners and educators alike.

3. Collaborative Script-Writing: Contributors will write scripts about their chosen topics, potentially using AI to help generate content. They will collaborate with each other and spot-check their work for accuracy. They will add their scripts to their Github pages.

Afternoon Session

4. Tool time! Contributors will download pre-selected screen recording technology (Descript and Openshot most likely), the pre-created sample website (so that work can continue on their tutorial with or without them in the future), install Local (or utilize WordPress Playground), make a copy of the team’s Google Slides, learn where to find visuals, and get started making screen recordings.

5. Direct Instruction: I will teach contributors one process for recording tutorials. As people work, they can upload their work to whatever repository / Google Drive folder, and update their Github comments as they work.

6. Screen Recording Time: Contributors work on recording screencasts to match the scripts for their tutorials. They will upload and link their screen recordings so they can be utilized at a later date and potentially polished if we run out of time.

7. Review time: Contributors who finish will review each other’s work and add reviews to Github.

If they finish entirely, we will have them write quizzes for tutorials.

For Remote Contributors

These same sessions will be adapted for and offered in shorter, recorded online workshops the week after contributor day, and posted on the Learn Online Workshops Calendar. They will also be recorded and added to Learn’s recorded online workshops.

The Ultimate Goal: 

Have contributors record rough drafts of tutorials–and potentially finish them! Since we are in person, we may be able to review work as soon as it is finished (in public on Github, but also in-person)

At any point, a contributor can walk away from the table, leaving a note in their Github issue of where they finished their day, suggestions for next steps, and if they plan to continue working on the tutorial. We will explicitly let people know a deadline for when we may open their tutorial up to others to work on to ensure their lovely content makes it to learn.wordpress.org. They can let us know if they plan to come back and work on it async over WCUS or later, but we will let them know that if they do not come back, another contributor may pick up their work to finish it.

While I know that in the past, people haven’t followed up on finishing their content, I believe we can tag it and leave topics better than we started, complete with strong learning objectives, instructor-approved descriptions, a well-written and spot-checked script, potentially strong materials for recording, or even totally finished tutorials.

Post-Contributor Day

1. Sort content into finished / in progress work, create publishing calendar.

2. Follow-up: For contributors who noted they would like to continue to work on tutorials, we will check to see that they have done so. If they have not completed their work by a certain deadline, we will aggregate their work and allow general content creators to continue working on their topics.

What I need from you:

  1. We need ideas! What are some learning topics that you think might be great for first-time contributors to make a video about? A topic that we can learn about WordPress in 3-5 minutes or less. These can come from the Ready to Create – You Can Help section of our Github or be entirely new–as long as they’re not on learn.wordpress.org at the moment.
  2. Are you interested? Let me know here! If you’d be interested in attending these sessions either in-person or in a workshop, please let me know in a comment below. This doesn’t mean you’re locked into attending, it will just give me a good idea of how many people I might expect so I can plan efficiently.

Thank you, team!

#contributor-days, #learn-wordpress

Proposal: Creating Learning Pathways for Learn WordPress

Learning Pathways for Learn WordPress

Learning pathways are a structured sequence of educational experiences or courses that are designed to help individuals acquire knowledge and skills in a specific field or discipline. By creating a series of learning pathways for WordPress, we can provide learners with a comprehensive understanding of the platform and its open sourceOpen Source Open 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. contribution methods. There are many benefits to using learning pathways to create curriculum, including:

  • Increased Engagement: Learning pathways provide a clear roadmap for learners, which can help to keep them engaged and motivated throughout the learning process.
  • Personalization: Learning pathways can be customized to meet the individual needs and interests of learners, which can help to make the learning experience more effective and relevant. (as suggested for future development in Learn WordPress Needs Assessment Results)
  • Better Outcomes: By providing learners with a structured and comprehensive learning experience, we can help them to achieve their learning goals more efficiently and effectively.
  • Better Collaboration: Learning pathways can encourage collaboration and knowledge sharing among learners, promoting teamwork and problem-solving skills.
  • Improved Retention: Learning pathways can help learners retain information better by breaking down complex topics into smaller, manageable sections, making it easier for them to remember what they’ve learned.
  • Unifying Strategy:  By unifying a learner-based strategy around curated content will make Learn.WordPress.org more sustainable and reduce maintenance overload. It will also help enhance and provide additional needed resources for WordPress users, rather than duplicating the efforts of others, including the Documentation team and the Dev CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Blog.

To implement this proposal, we suggest that the WordPress community work together to develop a series of learning pathways for WordPress. These learning pathways could cover topics such as WordPress basics, theme and pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party development, and ways to contribute to the WordPress open source project. We will 

  1. Establish our baseline audiences 
  2. Charter and create their Beginner ➡️ Expert learning journeys. 

Example: As a Beginner-level WordPress Frontend Developer, what is the content you need to master to move on to Intermediate competency? What is the content you need to master to move on to Expert competency and so on? If we can break down each audience and outline the core competencies for each level we focus our content creation around that and build out their pathways.

The WordPress Training Team will seek opportunities to collaborate with hiring managers in the WordPress ecosystem, independent freelancers and contractors, as well as educational institutions and other organizations to develop and promote these learning pathways. Next steps might include partnering with educational institutions to that offer WordPress courses or collaborating with industry organizations to create certification programs

By embracing learning pathways, we can help to create a more structured and effective learning experience for individuals who want to learn about WordPress. We believe that this will benefit both learners and the WordPress community as a whole.

Our first learning pathway for consideration is Introduction to WordPress Development: A proposed learning path

This post will remain open until May 1.

Initial reviews by @bsanevans @west7 @webcommsat

#learn-wordpress

Vote for Training Team Rep 2023

On Friday, December 9, we noticed the Team RepTeam Rep A 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. poll was not receiving new vote submissions. We have reset the poll (erasing previous results) and the timeline for voting. If you previously submitted, please resubmit only once.

The WordPress Training Team Rep nomination was closed on December 2, 2022. We got some great names nominated to be the next Training Team reps to replace the outgoing team reps @courane01, @azhiyadev, and @webtechpooja.

Once the nomination has been closed, we contacted all nominees and accepted nominations of those who responded positively.

Nominees

A Team Rep is a person who represents the Make WordPress team to the rest of the project, makes sure issues are raised and addressed as needed, and coordinates cross-team efforts. The following Training team members are nominated for 2023.

AMIT PATEL –  (India – Southern APAC)

Profile: https://profiles.wordpress.org/amitpatelmd/

BENJAMIN EVANS – (Japan – Eastern APAC)

Profile: https://profiles.wordpress.org/bsanevans/

CARLOS – (US West Coast)

Profile: https://profiles.wordpress.org/caraya/

COURTNEY. P.K –  (O’ahu Central Pacific)

Profile: https://profiles.wordpress.org/courtneypk/

COURTNEY ROBERTSON – (PA – North America)

Profile: https://profiles.wordpress.org/courane01/

DESTINY KANNO – (Japan – Eastern APAC)

Profile: https://profiles.wordpress.org/piyopiyofox/

POOJA DERASHRI –  (India – Southern APAC)

Profile: https://profiles.wordpress.org/webtechpooja/

Voting

Training team members are requested to vote to select two Training team reps by online poll in the following link:

Click here to Vote

The voting is open until 19th December 2022.

Results

Once voting is concluded, we will announce the result on December 20, 2022, in our weekly Team Meeting.

#team-reps

#nominations, #team-reps

Nomination for Training Team Reps 2023

This post kicks off the call for Training team reps. See also: Team Rep Nominations, 2022

The Role

Each team has one or more representatives (reps). Team reps are responsible for communicating on behalf of their team to other contributor teams. They represent the team, collaborate with other teams, raise, manage and address any issues. This role averages two to five hours per week in team organizational duties.

In the WordPress open sourceOpen Source Open 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, each team has on average one or two representatives, abbreviated as reps. Some teams have more than two.

Historically with the Training team, the team repTeam Rep A 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. duration was around two years, though some reps stuck around longer if there was a particularly good fit.

Anyone who serves as a “team rep” is responsible for communicating on behalf of the Training team to the other contributor groups via weekly updates, as well as occasional cross-team chats.  Reps are also consulted on Contributor DayContributor 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/., helping find someone within the Training team attending an event who can help lead a Training table.  Full details on the Team Rep role is on the Team Update site.

It is not called “team lead” for a reason.  It’s an administrative role. While people elected as team reps will generally come from the pool of folks that people think of as experienced leaders, remember that the team rep role is designed to change hands regularly..

Here are the main tasks:

  • Publish an update on make.wordpress.org/updates, suggested as a weekly post
    • X-post to Support, Marketing, and Community teams at the end of each sprint (when new content is on LearnWP)
  • Draft the weekly agenda, including reviewing the happenings in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. over the past week.
    • Nice to have: welcome new channel members during team meeting
  • Conduct weekly Slack meetings
  • Recruit contributors to facilitate portions of the meeting
  • Recruit contributors for meeting recap notetaking
  • Review drafts of recap notes
  • Assist in drafting a post for any Contributor Days

The Election Process

We will follow the same process as other teams, dates may differ slightly.

Nominations

Nominations are now open and remain open until December 2, 2022, at 12:00 UTC. Please add your nominations as a comment on this post. You can nominate yourself or someone else if you think they are a great fit.

Elections

We will review the nominations at our team meeting on December 6, 2022. If there are more than 3 nominations, we will organize a poll to select the Team Reps.

If we need to have a poll, this will be open until December 19, 2022 at 12:00 UTC .

Announcements

We will announce the results at the next team meeting on December 6, 2022. If there are more than 3 nominations, we will announce the results at the December 20, 2022 team meeting.

If you have any questions, please ask in the comments!

#nominations, #training-team

Looking for feedback: Handbook page about content localization

The Training Team has wanted to make contributing localized content for Learn WordPress easier. As of today, you can now find a page in our handbook that will walk you through both translating existing content, and creating new content in locales other than English!

New handbook page: Content Localization

The workflows listed are a combination of processes currently used by Training Team members, and some new ideas to better track contributions and maintain consistency across translated content. The team is looking for contributors to try these new workflows and help us identify how we can make them even better.

Please share your experience creating localized content for Learn WordPress with these new workflows in the comments of this post. If you have any suggested improvements to the newly created handbook pages, please share those below, too! We will continue to update the processes as we receive feedback.

+make.wordpress.org/polyglots/

#learn-wordpress, #localization