Training Team Meeting Recap – September 20

Slack Log for APAC Meeting (Tuesday 07:00 UTC)

Slack Log for AMER/EMEA Meeting (Tuesday 16:00 UTC)

(Requires 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/. login to view. Set one up if you don’t have a Slack account.)

The meeting agenda.

We have alternated our weekly team meetings according to the time zone. this week APAC had Team Meeting and EMEA/Americas Had an Office Hour

Introductions and Welcome

Attendees Team meeting (APAC): @piyopiyofox, @webtechpooja, @freewebmentor, @pitamdey, @askaryabbas, @piyushmultidots, @amitpatelmd, @hderashri, @psykro, @chetan200891, @onealtr, @eboxnet, @margheweb, @courtneypk

Attendees Office hour (EMEA/AMER): @azhiyadev, @arasae, @courtneypk, @meaganhanes, @psykro, @isvictorious, @annezazu,

Welcome to the team (WordPress usernames): @GoGinaMarie @adamwood @blerjangashi @iandunn @javiarce @jsholberg @sinarhadiwijaya @lanche86 @lokomofeilow @dvonrohr @xubiant @dantovbein

Meeting Note Takers

Meeting recap notes is one of the best ways to get started contributing to a team. Please refer to this guide to get started.

News

WP 6.1 Sprint

  • Release date for WP 6.1 is Nov 1, So we aim to achieve this in the timeframe and will release ready(add/update) content at the time of release.

Content published this Week
Introduction to block theme development (for beginners)

Content available for review
Padding Versus Margins – Tutorial

Open Discussions

  • @hderashri shared about an upcoming 10 days Hindu festival symbolizing the victory of good over evil.
  • @courtneypk shared about her b’day next week.
  • @digitalchild asked about a way through which a ‘to be reviewed’ list that can be created which is easier than digging around 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/.
    @webtechpooja answered by “new GitHub Project board https://github.com/orgs/WordPress/projects/33 where tabs are grouped by tickets.

Office Hour

@azhiyadev started the office hour and asked and started assigning people to unclaimed issues in WP 6.1.


Upcoming Meetings

You are welcome to join the team at any time! If you are new to the Training Team, please introduce yourself in the #training channel before the meeting (or anytime!) and feel free to join us in the meeting and participate as you are able.


Training Team Mission

The WordPress training team helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Tutorials
    3. Courses
    4. Online Workshops
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

#meeting-recap, #training-team

Training Team Meeting Recap for September 13, 2022

Slack Log for Office Hour (APAC time on Tuesday, Sept 13, at 07:00 UTC)

Slack Log for Weekly Team Meeting (AMER/EMEA time on Tuesday, Sept 13, at 16:00 UTC)

(Requires 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/. login to view. Set one up if you don’t have a Slack account.)

The meeting agenda.

Introductions and Welcome

Attendees Office hour (APAC): @piyushmultidots, @Amitpatelmd. @askaryabbas, @pitamdey, @chetan200891, @piyopiyofox, @webtechpooja, @psykro, @krupalpanchal, @Kemmy99, @onealtr

Attendees Team meeting (EMEA/AMER): @amitpatelmd, @finchps, @Webtechpooja, @onealtr, @pitamdey , @artdecotech, @courane01, @bethsoderberg, @Arasae, @hderashri, @chetan200891, @caraya, @idrissathiam01, @eboxnet, @bsanevans

Welcome to the team (Slack usernames): @kharisulistiyo@Benachi@finchps@Corina Burri@olsenp@Gökhan Ordu@thedavidjohnson , @Allie Nimmons@Sally Thoun and @Kathleen Cabral

Office Hour Update: We have reviewed Drafts in Progress column in Learn Content 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/ Project board.

News

Meeting Note Takers

Meeting recap notes is one of the best ways to get started contributing to a team. Please refer to this guide to get started.

Faculty Members Update

Please check the faculty members’ full list here. https://make.wordpress.org/training/faculty-program-members/

Proposal for GitHub Process Updates

Based on the discussions during the August 24th / 30th Supplemental SME Meeting and recent Monthly Faculty Meeting, folks have requested changes to the GitHub Content Development Board’s issue triaging and management. This proposal offers improvement suggestions to the current GitHub processes in order to clarify workflows for Faculty and Training Team Members.

WCUS 2022 Update

WCUS took place last weekend and you can scroll back to find out what went on that day ( please note that this link will take out of the flow of this discussion) https://wordpress.slack.com/archives/C02RW657Q/p1662918243308299

Individual Learner Survey

Courtney requested that we all take the survey, promote it on social, and ask others to take it.
https://learn.wordpress.org/individual-learner-survey/

August Sprint Retrospective

At the end of the month, we run a retrospective and review

  1. What went well?
  2. What could we improve?
  3. What will we do differently?

Check out the feedback from last month and if you missed it you can add your comments to the post.

 Course Creation – Making the process public

Jonathan is publicly documenting his process for course creation.

I’ve been thinking a lot about how to make the process of course creation public and open to feedback. As such I have decided to try and build the content publicly, by using a separate GitHub repository in my personal account. You can read more about my reasoning on this comment on the course issue in GitHub.

Allie has an idea for a course about creating courses.

Here is the link: https://wordpress.slack.com/archives/C02RW657Q/p1662927462402609

Training team badges

Pooja has been working on a post regarding how training team badges are awarded. This will shortly be circulated to the team to review and comment.

Handbook Updates

The following pages in the handbook have been updated:

Open Discussion

There is some confusion as to which GitHub Projects board should be used.

  1. This is the original board for content: https://github.com/orgs/WordPress/projects/2
  2. This board was created to test GitHub automation:  https://github.com/orgs/WordPress/projects/33

Courtney shared the following thoughts :

We prefer the point where media comes in to be on LearnWP itself. We’ve had issues of media being hot linked to GitHub still. Also, all currently live posts should be revised using the revision 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 tool on Learn itself. We moved to only creating on Learn because GitHub can intimidate a lot of folks. The old way of writing on GitHub was a much steeper step up for folks that don’t know it. I think the key for the team is to be consistent so we know where to go to view work someone has partially done.


Upcoming Meetings

You are welcome to join the team at any time! If you are new to the Training Team, please introduce yourself in the #training channel before the meeting (or anytime!) and feel free to join us in the meeting and participate as you are able.


Training Team Mission

The WordPress training team helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Tutorials
    3. Courses
    4. Online Workshops
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

#learn-wordpress, #meeting-recap, #training-team

Training Team Meeting Recap – September 6

Slack Log for APAC Meeting (Tuesday 07:00 UTC)

Slack Log for AMER/EMEA Meeting (Tuesday 16:00 UTC)

(Requires 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/. login to view. Set one up if you don’t have a Slack account.)

The meeting agenda.

Introductions and Welcome

APAC Attendees: @webtechpooja, @chetan200891, @amitpatelmd, @piyushmultidots, @askaryabbas, @piyopiyofox, @chaion07, @pitamdey, @azhiyadev, @hderashri, @aion11, @psykro, @onealtr, @courtneypk

EMEA/AMER Attendees: @azhiyadev, @eboxnet, @artdecotech, @meaganhanes, @onealtr

Welcome to the team (Slack usernames): @Idrissa Thiam@Labun Chemjong, and @kharisulistiyo

News

Faculty Members Update

Please check the faculty members’ full list here. https://make.wordpress.org/training/faculty-program-members/

See recaps published from the latest faculty meetings:

  1. August 24th / 30th Supplemental SME Meeting Recap
  2. Monthly Faculty Meeting Recap – August 30/31 2022

Individual Learn Survey

Help form the priorities for the Training team needs analysis. Survey is live, please fill out and share:
https://learn.wordpress.org/individual-learner-survey/

WCUS 2022

WCUS 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/. on Sept. 11 @courane01 will be the table lead, @courtneypk will lead onboarding. There will be a live stream available for the event https://us.wordcamp.org/2022/livestream/  – Check your local WordPress community to see if there’s a watch party near you, or see if you can get one started.

Summary Update: Courses Currently in Development

Check out for the update

Launching workshops in additional Locales

@bsanevans started drafting a handbook page for localized content. He’d appreciate any feedback added to the Google Doc.

Team Structure

@bsanevans also reimagined our contributor roles in light of the Faculty Program. More details can be found in this Slack thread.

Sprint

Content published this week

Reviews requested this week (help needed):

  1. Course: Block Development
  2. Using Block Attributes – Tutorial
  3. Adding a pattern from the Pattern Directory to your theme
  4. Image Optimization (@courtneypk would like another set of eyes on her review)

Retrospective

What went well?

  • Solid amount of content
  • First online workshop in Japanese
  • Improved onboarding and process documentation
  • Moved APAC meeting
  • Learn survey is live

What we can improve?

  • Update outdated handbook pages
  • Clear guidelines for newcomers
  • How we use 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/

What will we do differently?

  • Call for audit and content update for WP 6.1
  • Sprint sweep at end of month and assigning certain issues to the sprint

Open Discussions

The deadline for applications to speak at WordCampWordCamp 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. Asia 2023 has been extended to September 30, 2022. You now have 1 month to prepare and send in your application.


Upcoming Meetings

You are welcome to join the team at any time! If you are new to the Training Team, please introduce yourself in the #training channel before the meeting (or anytime!) and feel free to join us in the meeting and participate as you are able.


Training Team Mission

The WordPress training team helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Tutorials
    3. Courses
    4. Online Workshops
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

#meeting-recap, #training

Training Team Meeting Recap – August 30

Slack Log for APAC Meeting / Office Hour (Tuesday 07:00 UTC)

Slack Log for AMER/EMEA Meeting / Office Hour (Tuesday 16:00 UTC)

(Requires 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/. login to view. Set one up if you don’t have a Slack account.)

The meeting agenda.

Introductions and Welcome

attendance:
(APAC Meeting) – @chaion07, @webtechpooja, @bsanevans, @chetan200891, @aion11, @amitpatelmd, @tahmidulkarim, @pitamdey, @piyushmultidots, @piyopiyofox, @hderashri, @askaryabbas, @ashiquzzaman, @atomchat, @onealtr (async), @psykro (async), @courtneypk (async)

(AMER/EMEA Meeting) – @azhiyadev, @courane01, @caraya, @arasae, @manzwebdesigns, @onealtr, @eboxnet (async), @meaganhanes, @chaion07, @courtneypk (async), @atomchat

Welcome to the team (Slack usernames) Liz Dularza, Pitam Dey, Manzur, Davinder Singh Kainth, Aan Darmatirta

News

Meeting Note Takers

Meeting recap notes is one of the best ways to get started contributing to a team. Please refer to this guide to get started.

  • September 6 – @artdecotech
  • September 13 – Opportunity to volunteer
  • September 20 – @hderashri 
  • September 27 – Opportunity to volunteer

We are looking for note-takers for September, Interested? Let us know!

We’d still like a few folks to help provide access to the team site during meetings and welcome anyone along. Interested? Let us know.

Faculty Members Update

Please welcome our newest faculty member @Vagelis. He is joining our team as a content creator.
Please check the faculty members’ full list here for more details. https://make.wordpress.org/training/faculty-program-members/

Update on Individual Learn Survey

The survey is currently in progress for review.
@courane01: Once we are ready to go with it, Then I’ll integrate the survey to Learn Website and share the link here in the Training channel.  I anticipate this possibly later today.

Update on Team meetings

Meetings will be held in alternating time zones starting from September, so bear with us for today. Also, our next meeting will be in an alternating pattern. When a region is not running a team meeting, the time will be used for:

  • Office hour, bring your questions about training, Learn, content, etc.
  • Sprint/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 review
  • Provide feedback on items that are currently in review

further discussion on this in a slack thread

Training Team Profile Badges

We provide training team contributor badges that reflect on the http://WordPress.org profile that acknowledges your contributions to the Training Team. Right now this handbook page is outdated. we need to update it.

Things to consider before updating it:

  1. We are no longer using Github for a lesson plan, so we should consider removing it. No PR merged for this, then how we can provide a badge
  2. What if someone reports and fixes issues on Github, and after how many merged PRs, a person is eligible for a badge
  3. We are no longer using TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. boards, need to remove there

further discussion on this in a slack thread

Localized Content

@bsanevans started drafting a handbook page about how folks can create localized content for Learn WordPress. He’d appreciate any feedback people would like to add to the Google Doc in this Slack message: https://wordpress.slack.com/archives/C02RW657Q/p1660986964613769

Team Structure

@bsanevans: Secondly, I’ve been thinking about the current team structure. I’ve reimagined the contributor roles we have, in light of the Faculty Program which is going really well. This is very much a rough idea, and I’m open to any thoughts the team has. Please leave any feedback in this Slack thread I started earlier: https://wordpress.slack.com/archives/C02RW657Q/p1661838946241849

Update on August 25th / 30th Supplemental SME meeting

We had a meeting to finalize the role and responsibilities of our newly joined SMEs. Anyone can share the update on who is in the meeting?

We discussed the Github board and what can we do to make it clear to go to work for them. @piyopiyofox will soon share a post on what we discussed in this meeting on our Training team p2 post. Stay tuned for that.
further discussion on this in a slack thread

Launching workshops in additional Locales

Our first localized online workshop was done in Japanese and @Ben Evans shared his experience, if you are looking to host an online workshop in your locale, do check out this doc

Youtube channel

Please provide your feedback on this (google doc and a slack message by @courane01): https://wordpress.slack.com/archives/C02RW657Q/p1661876931073489

Events

WCUS 2022
It is approaching near. WCUS is from Sept 9 to 11 and 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/. is on Sept. 11 @courane01 will be the table lead, @courtneypk (subject to availability) to help with onboarding on location, and @webtechpooja will serve as Slack rep.

  • We will onboard new people to the training team.
  • We will promote our individual learn survey
    We could work on the Need analysis poll, according to the availability of involved folks.

This will be the first WordCampWordCamp 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. in person for many attendees at this event. We anticipate meeting the interested folks, helping them get up to speed with what Learn is working on, learning about each other’s skills, and brainstorming additional ideas.

Sprint

The Make post has now been broken down into

  1. Learn Content
    a. Upcoming 6.1 changes
    b. Revisions
  2. Website Development
  3. Training Team administration
    These mimic our project boards on GitHub.

Content published this Week:
Creating a new header with blocks

Content available for review:
The following reviews have been requested this week

Check-ins

What went well this month?
Significant content in multiple languages was shipped., Long-time contributors re-joined. Security measures developed for Online Workshops to protect facilitators and attendees from disruptions/Zoom bombing. You can follow the conversation here.

What could we improve? 
We still need course creators’ input on how to revise the content for any feature changes in WordPress. We need to focus on creating more course content and also build out the handbook so contributors have clearer guidance. You can follow the conversation here.

What will we do differently?

We can reduce the frequency of meetings and move detailed these discussions to the team blog using the meetings only for quick discussions. You can follow the conversation here.

September sprint plan discussion

@azhiyadev: One of the suggestions we’ve had is to only post 5-10 items on the monthly Sprint post so that newcomers are not overwhelmed. We also discussed having Faculty SMEs vote on what we should be working on.
We’ve got Faculty meetings scheduled this week and it would be a good opportunity to get the SMEs to prioritize our workload for September.
One of the things I would like to see taken into consideration is the auditing of existing content especially courses as we plan what we should be working on.
further discussion on this in a slack thread

Open Discussions

There was a discussion on using tools and plugins that are not part of WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. You can follow the conversation here.


Upcoming Meetings

You are welcome to join the team at any time! If you are new to the Training Team, please introduce yourself in the #training channel before the meeting (or anytime!) and feel free to join us in the meeting and participate as you are able.


Training Team Mission

The WordPress training team helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Tutorials
    3. Courses
    4. Online Workshops
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

#meeting-recap, #training

Monthly Faculty Meeting Recap – August 30/31 2022

Attendees

AMER: @arasae, @courtneypk, @courane01, @azhiyadev, Chris B, @onealtr

APAC: @piyopiyofox @bsanevans @onealtr @webtechpooja @west7 @amitpatelmd

Recap notes

  • Proposal to make Faculty meetings more public 
    • The team will continue working in the open
    • everything that isn’t a privacy concern should go into a public channel of some sort. 
    • The private channel is intended for logins, incident concerns, etc.
    • https://wordpress.slack.com/archives/C03B11FA16D/p1659098737136069?thread_ts=1658970512.900959&cid=C03B11FA16D 
    • Amer Notes: Does this mean more conversation in the #training channel instead of the #training-faculty channel? Yes. TL;DR – Have conversations we have been having in #faculty-training in #training itself. We can use the 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/. groups in different roles if we need attention of specific groups (such as subject matter experts)
      • PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” Groups: @faculty and it pings everyone in the faculty or if you want to ping a separate group. It’s something similar to @faculty-smes; it’s pinned to the private faculty channel.
      • If people have access to things like Learn’s wp-admin dashboard, these links can still be put into the #training channel – user permissions will keep things under wraps as far as strangers being able to access sensitive things while also allowing us to work in the open. 
    • APAC: The intention of this message was asking if we should open the faculty meeting up to the wider training team or keep these calls for faculty only?
      • Yes, keep the faculty meeting for faculty only, but continue to post agenda and notes publicly.
      • When we post the agenda for faculty meetings, we should more widely share with the training team that they can contribute to the agenda items async on the agenda post.
      • The admin will monitor the questions/comments on these posts and reroute them to the applicable faculty member
  • announcing new channel joinees
    • Is there a benefit in announcing these still to someone?
      • Amer Notes: Meant to acknowledge the team; the original purpose was to pull folks in and make them feel welcome. Marketing provides a, “Here is a good next step action item that you can do”.
        • Encourages people to step out of “lurker” mode; encourages people to join the meeting live. Alerts people to a meeting happening now.
        • Having this drop-in for faculty is useful; in terms of good “next of action” items, someone does contact them. 
      • Feels possibly like duplicated work; there’s a welcome committee. Is this just for faculty or just for joining training? Understanding is for everyone. 
      • TL;DR – People are being welcomed both in DM’s and in public.
    • Or are meeting facilitators (team reps) tracking these some other way anyway?
      • This has been helpful for team reps. Team reps go back through the week to try and see who has joined; if that exists somewhere and someone pings them, they can pick up. It’s helpful to know that someone else has already reached out.
      • Conclusion: We will continue to do this as it is helpful for the team reps.
    • APAC: One of the Welcome Wranglers will add the new channel joinee list directly to the meeting agenda which will cut the duplication of efforts.
  • Zoom disruptions
    • turned a few more security features on in our shared Zoom account
    • https://wordpress.slack.com/archives/C03B11FA16D/p1659733286494459 
    • Changed:
      • Annotation to “Only the user who is sharing can annotate”
    • Turned off:
      • Whiteboard (Classic)
      • Remote control
      • Gesture Recognition
      • Allow users to change their name when joining a meeting
      • Allow participants to rename themselves
      • Show participant profile cards in a meeting
    • Turned on:
      • Mute all participants when they join a meeting
      • Hide participant profile pictures in a meeting
      • requiring authentication to join a meeting.
        • APAC: If this is a requirement, we should document the process for joining.
        • We shared feedback that this particular item feels like a barrier to entry.
        • Perhaps this could be the final step if the other changes we made are not effective.
    • APAC: Is the fact that not many people are unmuting or turning on their video detracting from the “social learning space” aspect of our Online Workshops?
      •  
  • Faculty Meeting Calendar
  • Workflow (SME’s)
    • Difficult to jump in on things like reviewing new topics because the workflow may not be clear or simple enough to manage at the moment.
    • https://wordpress.slack.com/archives/C03B11FA16D/p1660112243025129 
    • https://make.wordpress.org/training/handbook/getting-started/how-we-work-together/#development-workflows
    • pull our GitHub issues into a spreadsheet to help SMEs better assess priority and “staleness
      • My first guess would be to use 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/ APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.
      • https://docs.github.com/en/rest/issues
      • More specifically https://docs.github.com/en/rest/issues/issues#list-repository-issues
    • Amer Notes:
      • SME’s weren’t aware of the topics; there was concern that topics were being duplicated because there were multiple elements. We have tutorials, lesson plans, online workshops, and courses, so topics looked duplicated – it’s a different learning format that the topic is being 
      • Link to SME notes (when SMEs are supposed to jump in, when supposed to pass on to the content creators)
        • We should reach out to SMEs to figure out how they would best like to work with us.
        • Could use time during former training meetings (since they’re rotating) to work with SMEs when the meetings.
          • Go through an update notes on Github from a more synchronous setting.
      • Github session – need to know how this works in order to run a session for SMEs, then use that to generate automations. As long as a flow exists, it’s easier for SMEs to work with.
        • We would like to have more Github automations, and we can do that with the new version of Github projects
          • Code approach of automations was discouraged; it was pretty challenging. CER will reach out to Micah and Github representatives around that issue of automation in order to leverage more things.
          • All content is in one project board; still figuring out how this works. We moved into Github to make sure we can leverage the tech to better track – we want to track contributions. 
  • Hugh has secured a Crowdsignal premium account for us to use
  • Contributor badges
    • I’m not quite sure how our contributor badges are distributed– will @Tahmid ul Karim receive a badge for this merged PR? https://github.com/WordPress/Learn/pull/890
    • Here is the process mentioned to provide a badge: Team Profile Badges – Make WordPress Training
      • Amer Notes:
        • What are the steps? What are the requirements? Discussed in today’s meeting. There is a process, but it’s outdated; one of the new elements to it is because we’ve started using Github. With the pilot we’re doing with metaMeta Meta 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., that may be another way we don’t have to manually add badges. Meeting notes, pull requests… we actually do pull requests on the development side. We didn’t previously have a development board, so that is new. Pooja has made some updates to it.
          • Get faculty to approve it; need the training team to approve the badges and process there.
          • Do we have a badge for faculty? No; we should present it back to the training team, based on the updates and some of the discussions, what do you think in terms of the process?
          • We think that Pooja is working on a P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post about this (correct us if we’re wrong!) – Check with Pooja to see if she needs anything here, but no other action item needed if this is true. 🙂 Pooja is not working on a P2 post. She is only updating the Handbook page. 
  • Individual learn survey – https://learnwordpress.survey.fm/make-wp-training-team-individual-learner-survey
    • Related to Crowdsignal above, I already talked about it.
    • Courtney Robertson is working on this. She’s working on it (some login issues, need to do a password reset)
    • Make use of this for WCUS, get some good data back.
    • APAC: Should be ready to go within a week just in time for WCUS!
  • Faculty Meeting September 2022 – 5 weeks in September
    • Amer Notes: Change this in early September to 2nd and 4th weeks, fixes that issue.
    • Also, can we make sure to include zoom links integrated with the meeting calendar event, so that any faculty member can join in the meeting by following the event and zoom link
      • Amer Notes:
      • We should use our standard Zoom link
      • We may want to not have this on the main calendar because if it’s just for Faculty, we don’t want all the WordPress community. We may get flooded with folks who just want to jump in who aren’t faculty folks.
      • We could instead send invite details ahead of time, but use the general Learn training account.
      • Where is the repeating event? If that’s a private invite, we can replace the link in there (Action Item: ask Destiny to replace the link with one scheduled on Zoom) – Destiny replaced this, but note that the event is modifiable by any guest on the invite so no need to wait for any one person to make changes.
        • Have the date in the general team calendar
        • Zoom link should just be on the invite.
  • Content Errors
  • WordCamp Asia Call for Speakers – Do we want to do a session where we promote the Training Team, the Learn WordPress site, and explain how folks could get involved? (Original Slack convo)
    • Oneal and Pooja are on the speaker’s selection team; they’re trying to get more speakers to apply. Call for speakers is yielding a lower return. Focus on speakers from Asia. A lot of applications may come in at the last minute.
    • Some folks who might be interested: Jamie, Mike Schroeder, Destiny, Ben, and others are all living in Asia. They will probably have more to say on this. 
  • APAC walk on: Pooja is working on a process improvement for first time WordPress contributors.
    • We suggested Pooja connects with Courtney PK around this

#faculty-meeting

August 24th / 30th Supplemental SME Meeting Recap

Faculty Members held a supplemental Subject Matter Expert call on Wednesday, August 24th at 18:00 UTC for Americas/EMEA and Tuesday, August 30th at 05:00 UTC for APAC to brainstorm and discuss how we can make these processes more clear for folks, and also evaluate which responsibilities SMEs find productive and impactful for their work. You can find our agenda post linked here.

Attendees

August 24th, 2022: @annezazu @azhiyadev @onealtr @wpscholar

August 30th, 2022: @afshanadiya @bsanevans @piyopiyofox @onealtr @webtechpooja @digitalchild

Notes

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/

  • A lot of the conversation surrounded GitHub and its current organization and use:
    • Right now Team Reps are not planning to reduce issues in GitHub topic ideas column, but they are looking to provide more direct priority to certain issues which will go into the sprint those will be provided by SME’s.
    • What type of labels do we need?
      • For marking what is in the sprint -> milestones would be a good tool for this
      • Categorize the content so that it is targeted toward SME’s expertise
      • Add a “Needs SME review” label
    • Where to store topic ideas?
      • The. project board should only contain items that are ready for pick up or are being worked on.
      • Perhaps topic ideas can be stored on another GitHub project board and then transferred to the content development board when ready? Is GitHub Discussions a place where we could allow folks to submit ideas?
    • Do we need a GitHub organizer team?

Ideal SME workflow

  1. SME’s vet topic ideas off Github for accuracy and relevance
  2. Vetted topic ideas are added to GitHub in the Ready to Create column
  3. A Content Creator picks up a task from the Ready to Create column, moves it to the Drafts in Progress column, and creates the content
  4. As the content is being created, the SME who vetted the topic or is an expert in the topic provides guidance / mentorship to the Content Creator
  5. Once the content is in the Reviews in Progress column, an Editor reviews the content

Action Items

#faculty-meeting

Training Team Meeting Recap – August 9

Slack Log for APAC Meeting (Tuesday 07:00 UTC)

Slack Log for AMER/EMEA Meeting (Tuesday 16:00 UTC)

(Requires 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/. login to view. Set one up if you don’t have a Slack account.)

The meeting agenda.

Introductions and Welcome

Attendance APAC Meeting: @webtechpooja @chaion07 @st810amaze @hderashri @ashiquzzaman @chetan200891 @thisisyeasin @amitpatelmd @ronakganatra @kafleg @FahimMurshed @Krishnakumar @aion11 @eboxnet @onealtr @courtneypk @bsanevans @digitalchild

Attendance EMEA/Americas Meeting: @artdecotech @courane01 @chaion07 @arasae @azhiyadev @Kemmy99 @yusuf @caraya @chetan200891 @eboxnet @onealtr @amitpatelmd @Webtechpooja @azhiyadev

Welcoming the newcomers joining the Training team in the last week (Slack usernames) : @Nilesh Choudhary @Premalatha Rajan @Kevin Lim @Lukman Nakib @Burak KAHYAOĞLU @Omar Vásquez

Meeting Note Takers

News

The Month in WordPress – July 2022

The July 2022 monthly update is out now. Check out the link for some exciting announcements and proposals for the WordPress project, from an updated timeline for the WordPress 6.1 release, to design updates on 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/.

Faculty Members Update

New Faculty Members have joined the Faculty Program and The Faculty Member list has been updated with their information. If you are a Content Creator, Editor, Subject-Matter Expert or an Administrator, and interested in helping the community, then check out our Faculty Member handbook, for the various volunteer roles available with our team.

Lesson Plan landing pages

We’re really excited about the upcoming Lesson Plan redesign. While we wait for the code review on the updates, do check out the GitHub link if you’d like to read up on the interesting ideas shared by the team.

It’s all Greek!

Did you know? Greek is the oldest recorded living language, with written records spanning over 34 centuries, and today there are around 13 million native Greek speakers. Please do check out our brand new Lesson Plans in Greek and stay tuned for some exciting upcoming workshops in Japanese, Greek, and Hindi.

Microcontribution Opportunity

Sarah @arasae is running a fascinating brainstorming experiment while writing the lesson plan for “Different types of Themes”. The goal is to collect invites idea contributions from everyone and select the best from them. Check out the GitHub link for more details.

Information Sources for WP 6.1

Courtney @courane01 has kick-started a comprehensive review to identify the lesson plans and workshops that need to be revised for WordPress 6.1 along with the links to connect them to specific 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/ issues and GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ or CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. More details here.

Ideas Board for WordPress content

Hugh @Hugh Lashbrooke has proposed the creation of a public ideas board hosted directly on WordPress, where users can propose new content ideas and also vote on other ideas. If you would like to collaborate on this interesting concept, please check out the GitHub link for this idea.

Sprint

The August Sprint structure is now synced to our current GitHub project boards, viz. Learn Content, Website development and Training team administration. Head over to GitHub boards to pick from the High Priority issues. If you’re just getting started, then check out the Quick Fixes or Good first issues board.

We are also getting a lot more translation requests on Learn. If you would like to help us translate a lesson plan or workshop into another language, please let us know on Slack or comment on the original GitHub issue.


Upcoming Meetings

You are welcome to join the team at any time! If you are new to the Training Team, please introduce yourself in the #training channel before the meeting (or anytime!) and feel free to join us in the meeting and participate as you are able.


Training Team Mission

The WordPress training team helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Tutorials
    3. Courses
    4. Online Workshops
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

Training Team Meeting Recap – August 2

Slack Log for APAC Meeting (Tuesday 07:00 UTC)
Slack Log for AMER/EMEA Meeting (Tuesday 16:00 UTC)
(Requires 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/. login to view. You can set one up if you don’t have a Slack account yet.)

Here is the agenda for these meetings.


Introductions and Welcome

Attendance APAC Meeting: @webtechpooja @bsanevans @kafleg @hderashri @west7 @amitpatelmd @chaion07 @onealtr @digitalchild @courtneypk

Attendance EMEA/Americas Meeting: @eboxnet @courane01 @webtechpooja @caraya @onealtr @arasae @courtneypk @azhiyadev

Welcome to the newcomers who joined the Training team in the last week: @theholidayatlas @eddymedia @rashmimathur @vkrish @bhupendra2909 @fox289

Meeting Note takers


News

Wider community

There have been some bigger discussions happening in the wider WordPress community which will have effects on the work we do in the Training team. Check out these discussion, and make sure to leave any thoughts you have on the respective posts.

Information Sources for 6.1

@courane01 began auditing GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ change logs and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets related to the upcoming core 6.1 release. She’s been able to connect the topic issues in our 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/ project board. We could use support from course creators to track areas that need to be updated/revised related to WP 6.0 (already shipped) and the upcoming changes in 6.1.

Lesson Plan landing page will be updated!

The team has been discussing a visually organized way to navigate the Lesson Plans. We’ve landed on a conclusion, and are just waiting for a code review on the updates. Keep an eye out for the updates to go live soon!

We welcomed new Faculty Members!

We recently onboarded additional members to our Faculty Program. If you’re interested in joining our dedicated team, come check out the Faculty Program section of our handbook. We’re particularly interested in seeing more join from APAC regions.


Sprint

We’ve come to the end of our June and July 2022 Sprint and will be publishing a retrospective in the coming week. We took some time to share stats, wins and other feedback in the meetings.

What went well?

What could we improve?

  • Clarification, increased participation, and better onboarding to our different team roles.
  • Assign priority on GitHub issues more precisely.
  • Ship the Individual Learner Survey.
  • Become more data-driven in our decisions.

What will we do differently?

  • Improve general onboarding flow for newcomers.
  • Create material to clarify and introduce each team role.
  • Improve communication around GitHub issues and what contributions are appreciated.
  • Work with MetaMeta Meta 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 on tracking contributions.

Open Discussions

Collecting feedback from Online Workshop facilitators and attendees

@bsanevans suggested setting up an optional feedback form for workshop facilitators on the After an Online Workshop handbook page. Faculty administrators would have access to the form submissions, and would act on any actionable feedback.

@caraya suggested also collecting participant feedback – perhaps anonymously. We’re still considering what method would be most effective.


Upcoming Meetings

You are welcome to join the team at any time! If you are new to the Training Team, please introduce yourself in the #training channel before the meeting (or anytime!) and feel free to join us in the meeting and participate as you are able.


Training Team Mission

The WordPress training team helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Tutorials
    3. Courses
    4. Online Workshops
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

#meeting-recap, #training

Training Team Meeting Recap – July 26 & 28

Slack Log for AMER/EMEA Meeting (Tuesday 26 July at 16:00 UTC)

Slack Log for APAC Meeting (Thursday 28 July at 11:30 UTC)

(Requires 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/. login to view. Set one up if you don’t have a Slack account.)

The meeting agenda.

Introductions and Welcome

Attendance EMEA/Americas Meeting: @webtechpooja, @azhiyadev, @eboxnet, @artdecotech, @chetan200891, @colorful-tones, @arasae, @caraya, @kemmy99, @courane01, @nickchomey, @onealtr, @courtneypk, @bsanevans, @manzwebdesigns

Attendance APAC Meeting: @webtechpooja, @onealtr, @eboxnet, @kafleg, @amitpatelmd, @chetan200891, @meher, @atomchat, @psykro, @hderashri, @jominney, @courtneypk, @thisisyeasin, @sabbir16

Meeting Note Takers

We are looking for note-takers for August

News

Faculty Members Update

We had a faculty member meeting on Tuesday at 7:00 PM UTC for EMEA/AMER region and on Wednesday at 5:00 AM for the APAC region, this is the update from that meeting.

APAC Training Team Meeting

The APAC Training Team Meeting will move to 7:00 AM UTC from 2 August 2022

Summary Update: Courses Currently in Development

Currently, we have four courses in development. This is an overview of what is being worked on and relevant links to follow if you are interested to learn more.

We welcome any contributors to share their ideas for relevant courses you would like to see on the Learn platform or to get in touch about creating your own course.

5ftF end-to-end recognition process

In an effort to raise awareness about all contributions, not solely those limited to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. props releases, @courane01 has been participating in some discussions around this topic and was asked if the training team would like to be involved in this pilot.

There was general agreement that the team would like to take part.

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/ site updates

Posts that need team/community feedback:

Community Course Creation: A Proposal

Courses contain text, screenshots, and videos. Much of this content can be sourced in lesson plans and tutorials (formerly workshops). However, creating a course is a big and perhaps hard task for a single contributor.

Having multiple opportunities for contributors to create the content on a single topic that could be included in the course would help involve more folks, and possibly help us release material sooner.

Rethinking the Lesson Plan Creation & Updating Process

This is related to the course creating proposal, and discusses who makes what portions of a lesson plan, and how it comes together.

Proposal: Merging Lesson Plans, Video Tutorials, and Slides

This is a topic the team has been discussing since the launch of the Learn siteLearn site The Training Team publishes its completed lesson plans at https://learn.wordpress.org/ which is often referred to as the "Learn" site..  At launch, a lot of the content on the site was not created by the training team. However, we have now found our place as one unified team creating and managing all this content.

The idea here is that the stand-alone topics that go into courses can live independently, merging the content types to include text, screenshots, code samples, video, etc. in one spot. This may be easier for also tracking updates for content.

However, there are also concerns about the audience of Learn WordPress, and whether these changes benefit them, or not.

Feedback for this is really welcome. In the hopes to consolidate, we’d unify multiple learning styles on a single source, roughly have the workings for stand-alone content in a similar way as inside courses already, and could tuck the teacher/trainer parts a bit out of sight until we have more understanding of our audiences. 

Training team Handbook updates 

  1. Faculty Member Getting Started guide is now up and running.
  2. Preparing a Technical Handbook a guide for folks wanting to create technical tutorials.
  3. Best Practices for Hosting Online Workshops has been updated.

Sprint

June-July Sprint

The following lesson plans have been published

  1. Block Patterns (Greek translation)
  2. WebP images in WordPress
  3. Create a Basic Child Theme for Block Themes
  4. Locking Blocks in the Full Site Editor

The following reviews have been requested this week

  1. Managing Updates Tutorial (Brazilian Portuguese translation)
  2. Customizing your post content layout tutorial
  3. Using the Create Block Tool tutorial

Open Discussions

Giving FSE a More User Friendly Name

Road to WP 6.1 – thanks @courane01 for creating this for the team.


Upcoming Meetings

You are welcome to join the team at any time! If you are new to the Training Team, please introduce yourself in the #training channel before the meeting (or anytime!) and feel free to join us in the meeting and participate as you are able.


Training Team Mission

The WordPress training team helps people learn to use, extend, and contribute to WordPress through synchronous and asynchronous learning as well as downloadable lesson plans for instructors to use in live environments, via learn.wordpress.org.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects.

  1. Learn.WordPress.org
    1. Lesson Plans
    2. Workshops
    3. Courses
    4. Social Learning Spaces
    5. Pathways to Learn WordPress
  2. Getting Involved
    1. GitHub Website Development
    2. GitHub Content Development
    3. What We Are Currently Working On This Month
  3. About The Team
  4. Our Team Blog

July 2022 Faculty Meeting Recap

On Tuesday, July 26, 2022 19:00UTC (AMER) and Wednesday, July 27, 2022 05:00UTC (APAC), the Training Team Reps and Faculty Program Members held two calls to discuss the progress of the training team goals and our strategy for meeting them.

Thank you @arasae and @bsanevans for facilitating and taking notes! Outlined below are the notes taken from these two calls.

Attendees

AMER call: @annezazu @courtneypk @azhiyadev @colorful-tones @courane01 @ndiego @chrisbadgett @onealtr @richtabor @arasae

APAC call: @bsanevans @west7 @webtechpooja @onealtr

Notes

  • Proposal: Merging Lesson Plans, Video Tutorials, and Slides
    • Do we have a consensus on how to move forward with this?
      • At Learn’s Creation: Community team made many materials; though as not a lot of collaboration with the #training team. Vision was to have topic parity, unit single topics together. 
        • A needs analysis may help us to shed light on this.
        • Need some more stats about our user journeys; we have Jetpack, but we need more data to make informed decision
        • Vision of uniting these ideas: 
          • Consolidate the buckets for updating things
          • Keep all of the assets for the same topics together
          • Tuck “teacher” things behind the menu behind a tab
      • Lots of comments about many things moving toward tutorials; it’s important to be mindful that not everyone learns using video. We also have the accessibilityAccessibility 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) side of things – within developing countries, we need to be mindful of bandwidth and what we need to think about this in terms of accessibility. 
        • Barriers to entry 
        • Text-based format may be better for some
          • From APAC meeting: The line between text-based materials and the docs created by the Docs team gets blurry here. We’ll want to consider how to best join forces so that we’re not duplicating efforts.
        • Video element may be better for other content creators
        • Do we still need every section in lesson plans?
          • What should be re-used? (For example, the “example lesson” is that someone could take and create a video out of it; likewise, you can take the transcript that someone generate at the videos and use that to create some form of lesson plans) – how is it best to present this content in a way that works best for everyone?
      • One Approach: Needs analysis to decide what is needed across things.
        • Another approach: Try something new, see if it’s viable, see if that model works. Could we pick an area and see what happens if we morph it into a more standardized, unifying approach? Does it make it easier, or are there too many edge cases? 
        • Could we pick four or five things to chunk and pull from it to create a model of this ahead of time to see what works and doesn’t? 
      • Could we create a few versions? One where things are for learners, one for teachers, and one hybrid? 
      • There does not seem to be a consensus at the moment; we should continue to gather feedback. There are two audiences; do we need to look at a needs analysis to decide which way to go, either merging everything or separating it out entirely?
        • Who is using the site? Educators/ facilitators / teachers? Or is it people who just want to learn how to use WordPress? We need to discover our audience.
        • From APAC meeting: We want to clearly categorize our content for the two audiences – learners and teachers.
          • The learner audience is going to be substantially larger than the teacher audience.
          • Content should be clearly defined as to who they are for.
          • Cross-linking content aimed at different audiences could cause confusion. 
      • Content Type: Video tutorials, lesson plans, courses. All specific content type; if we have really strong templates that people can build off of, that makes it easier for the creator; using the topic categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. for a mixed search is a good idea. There are certain things that could become components within other things. We also may be able to use this example.
      • From APAC meeting: In the past, Training looked after content for facilitators (meetupMeetup 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. organizers), and Community looked after content for learners. Both are now responsibilities of the Training team.
        • So we want to keep in mind, we are building content for two distinctly different audiences.
        • Could we keep content separate on the front end, but link things by topic behind the scenes? (Such as in 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/?)
      • Conclusion: This conversation is still ongoing; continue to leave comments on the actual project thread and continue the conversation going publicly on the thread.
      • Conclusion from APAC meeting: We are serving two audiences – learners and teachers. Where we can link resources or combine efforts, great! But our decisions around designing the site and creating/managing content should always keep these two audiences in mind.
    • Explore how this relates to Rethinking Lesson Plan Creation Process – Let’s discuss both of these threads to come to a consensus on a way to move forward. Discussion Frame:
    • Existing Lesson Plan Goals (as Sarah sees them)
      • To make the process bite-sized so people can contribute what they can with the time that they have.
        • Are we succeeding in this endeavor? If so, why? If not, what could we change?
      • To entrench the process in instructional design best practices so that the quality is A++ from start to finish (with an eye on eventual certifications)
        • How can we make this process more accessible to lower the bar of entry for quality contributions?
      • To be able to track what people are doing so everything is public, we can market it, and we can celebrate!
      • Is there a way to do this where it’s a reversible decision quickly? Could we iterate upon this later? What is reversible? What is irreversible?
    • What’s working to make the bar entry lower in other places? What can we change?
      • Online Workshops
        • Live workshops haven’t touched much on lesson plans; we have two directions: creating content for an educator, and creating content for learners. There are two different kinds of content.
        • The reception we are getting from online workshops is really encouraging. People are excited to explore and engage more.
        • The original intention of learn is excellent and creating content for educators is important, but it is also equally important to create content for learners as well. We are moving to a place where lots of people are scared about different things and want to learn.
      • Video Tutorials
        • Missing workshop template; if there were a template specifically for video tutorial. All that may be needed is a frame.
        • There are frames for lesson plans, but not for workshops; is there a way to embed strong instructional design foundations without locking it 100% into a lesson plan to speed up the process without sacrificing content.
        • We don’t have a template for video tutorials; we do have a process flow in the handbook. We may need to take that and change it into a template, similar to what we have for lesson plans.
        • Having a video first that they can base a lesson plan around and running with it may be a good thing for other contributors.
      • Note Taking
      • Review Process
      • Faculty Program
    • How can we make contribution easier for beginners, and make onboarding newcomers smoother?
      • Make templates for each content type (tutorials, live workshops, courses) that are easy to follow – where? Github then to Learn? Flesh out templates (workshop, video tutorial, courses) – maybe having one place where we update things rather than multiples? Maybe it could stay in Github.
        • The idea of putting this in Github is a good one. Almost ready for publication, then access to the Make site. Putting in Github and maintaining it there until it’s ready to be published may be a good direction.
      • Allow for more flexibility in what can come first, second, third. 
      • Make Design Elements more Accessible: Video thumbnails – where are new contributors getting hung up? “Where do I find X thing?” Can this be built into the templates?
      • Github can be really daunting for someone who is new. Where should templates live? 
      • Could we create a separate repo in Github? What are the things you should post in your workshop?
  • Enabling and empowering new contributors to put on Online Workshops
    • How can we make space to allow new contributors to be vulnerable and make mistakes?
      • Having a buddy to help you is immensely helpful
      • Consistency in templates: provide all resources (Google slide with the featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. templates)
    • Suggestion: Change Github to Topics and link different forms of content 
    • Group Alert words have been helpful
    • How can we do better to check our biases to ensure we relay constructive feedback for new contributors to action?
      • We ran out of time before getting to this issue; a meeting dedicated to this by itself has been requested.
      • Could we have a dedicated time to discuss online workshops to make sure we are being as constructive and welcoming as possible?

Action items

Listed below are action items created from our discussion. Note the items that have not been assigned, and are open for volunteers. Please comment if you are interested and available!

  • Create Github Issue templates for video tutorials and workshops: volunteer(s) needed.
  • Consolidate all the available resources (Blue Templates for Screenshots) into those Github issues/templates: volunteer(s) needed.
  • Find a time/space to discuss online Workshops (reviewing, constructive feedback, etc.): volunteer(s) needed.
  • Bring Faculty discussions to a more public venue (i.e., public 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): All

#faculty-meeting