Training Team Profile Badges

There has been a recent flurry of pull requests from people new to the Training Team. Most of these pull requests are fixing small issues with the lesson plans – and we have many of those! However, these contributors have not introduced themselves to the team in Slack or participated in the team’s meetings. Their efforts are seemingly to procure the Training Team badge on their WordPress.org profile. That raises the issue of what the requirements are to secure those badges.

The Training Team would like to be more transparent and consistent and define the criteria for giving profile badges to people who contribute to our team.

Other WordPress.org Teams

Looking at how a few other non-code-focused teams handle their badges…

The Meta Team

“On your profile, badges are added based on your contributions to the WordPress project. There are two kinds of badges: contributor and team. The contributor badges are generally assigned to anyone who has contributed to a particular team. Meanwhile, the team badges are given to those who are active on their team. Each team can set its own criteria for who should get each badge. When possible, the meta team will automate badge assignment.”

(https://make.wordpress.org/meta/handbook/documentation/profile-badges/)

The Polyglots Team

The Polyglots Team requires ten string translations to earn their Contributor badge. The also have an “Editor” badge which is given when a person has Editor status on a [locale].wordpress.org site.

The Support Team

“We have official badges for Support Contributors and Support team members. For the moment being, these badges are awarded manually to active contributors. In the future, we hope to be able to automate that process, and then use the following criteria:

  • Support Contributor: You have contributed over 400 support replies.
  • Support Team: You have been promoted to Moderator.”

(https://make.wordpress.org/support/handbook/contributing-to-the-wordpress-forums/volunteering-in-the-forums/)

The Documentation Team

The documentation team is probably the team that is the closest to the Training Team in their responsibilities. They do not yet have criteria for their badges but are also working on this.

Recommendation for Discussion

One-time contributions are very welcome, but perhaps not the purpose of the badges. As a starting point for discussion, let’s consider the following:

  • Training Contributor:
    • Writing – You have developed an approved lesson plan from scratch or completely rewritten one that was out of date.
    • Copyediting / Reviewing – You have contributed 10 pull requests over a period of more than 30 days.
    • Testing – You have completed 3 testing feedback forms after using a lesson plan in an event.
    • Auditing – Review 3 lesson plans and create GitHub issues for any needed changes.
    • Connecting – Make 3 workshop recommendations by combining existing lesson plans.
  • Training Team: You have admin rights on GitHub and/or the make.wordpress.org/training site.

Too easy? Too difficult? Does it deter people or encourage them? Is the “over 30 days” part a good idea? Thoughts? These criteria are up for discussion!

Training Team Meeting Agenda 28 March 2019

Please join us at 19:30 UTC in the #training Slack channel for our weekly meeting!

Today’s Agenda

  1. Learn site update
  2. Lesson plan assignments and updates
  3. Team profile badges
  4. Open announcements/discussion

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 creates downloadable lesson plans and related materials for instructors to use in live environments.

Getting Involved

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

Team Links:

Training Team Meeting Agenda 17 January 2019

Please join us at 19:30 UTC in the #training Slack channel for our weekly meeting!

Today’s Agenda

  1. Handbook update
  2. Videos update
  3. Learn site design update
  4. Lesson plan assignments
  5. Open announcements/discussion

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 creates downloadable lesson plans and related materials for instructors to use in live environments.

Getting Involved

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

Team Links:

Notes on January 3, 2019 Meeting

Slack Log (Requires Slack login to view. Set one up if you don’t have a Slack account)

Welcome and Meeting Outline

  1. Handbook Updates
    1. Revising the Style Guide
      1. Examples displayed should be relevant to Github formatting
      2. Slides style guide wasn’t functional as the slide display tool was discontinued. Suggest moving to https://pages.github.com/ . 
      3. @juliekuehl will update this page.
    2. Add tasks for semi-annual handbook updates to our team Trello board.
      1. 2 weeks before time changes begin, communicate about if the meeting moves times.
      2. Update a few places on the handbook displaying meeting times
      3. Update annual team goals
  2. Videos
    1. @jessecowens has been working on editing the atom video with some updates. He expects both the atom video and the one on slides to be complete by end of January
  3. Learn.WordPress.org
    1. The Design Team is still working on re-doing the design based on the recommendations of the meta team.
  4. Lesson Plans
    1. Regrouping about what lesson plans are in process next week to get more ready for the relaunch of the Learn site
    2. Possibly conduct a video meeting to brainstorm regrouping on lesson plans.
    3. Work with Kids Camps for workshop plans
    4. Repo Maintenance Labels for tagging lesson plans
      1. @courane01 will brainstorm ideas this week to be reviewed next week (January 10) and finalized on January 17.
      2. These will be part of the lesson plan submission process
    5. Meeting Wrap Up and Next Meeting Next meeting on 10 Jan 2019

#handbook, #slides, #videos

WordCamp US 2018 Contributor Day

The Training team made a lot of progress at Contributor Day this weekend. We on-boarded several new members, completed several Trello Cards, and collaborated with the Design and Marketing teams to develop the plan for our front-end lesson plan site.

A photo of WordCamp US 2018 Contributor day. Image Credit to @harryjackson1221
WordCamp US 2018 Contributor Day. Image Credit @harryjackson1221

Call for Your Comments

One of the largest-scope discussions involved the development of our WordPress.org front-end site. Currently, our dedicated URL is learn.wordpress.org, but a proposal was made to change to teach.wordpress.org.

The reasoning behind the proposal is that our content is in fact focused on how to teach WordPress topics, rather than learning. We’d like to open the discussion on this since it will be a rather large change. Please make a comment on this post with your feedback on the proposal so that we can discuss it in our upcoming meetings.

GitHub Restructuring

As we collaborated with the Meta team with the goal of translating our Lesson Plans in GitHub to the front-end, we reached the conclusion that a restructuring of our repositories will be needed.

In order for the front-end to be most easily kept up-to-date, as well as provide a mechanism for a final editorial review before content is published, a new master repository will be created with individual lesson plans as submodules within it. This will allow our current workflow to remain mostly unchanged, and the Team Leads can perform an editorial review before pulling into the master repo. @jessecowens has volunteered to spearhead this project.

Contributors

We’d like to welcome all of the new contributors and recognize the experienced contributors who volunteered their Sunday to join the team! @rbailey10 @davidneeham @learnwithchloe @winternetweb @juliekuehl @jessecowens @davidbgreen @dabrattoli @sunsand187

Help Wanted

We’re still looking for folks who have the time and expertise for a few vital roles in the Training Team:

  • Taking notes from team meetings.
  • HTML- and CSS-proficient writers who can develop new Slide Decks for lesson plans.
  • Instructional designers or educators familiar with Bloom’s Taxonomy.
  • Wrangling the team’s style guide.

Priority Projects Moving into 2019

  1. Finish the copy and design of the learn.wordpress.org (or teach!) and deliver it to the Meta Team.
  2. Clean up the Training Team Handbook with the vision of creating a one-stop-shop for new contributors.
  3. Identify priority lesson plans to highlight on learn.wordpress.org when it goes live.

#training, #wordcamp, #wordcampus

Proposed Handbook Outline

 

  1. About
    1. What we do
    2. Origin story https://make.wordpress.org/marketing/handbook/about/whats-our-origin-story/
    3. Vision
    4. Tasks
    5. Team leadership
  2. Get Involved
    1. First steps
    2. Contributor Day
      1. Organize
      2. Participate
    3. Areas to contribute
      1. Present a lesson & Feedback
      2. Write a lesson
      3. Review lesson plans
      4. Other
  3. Communication
    1. Meetings
      1. agenda/notes etc P2
      2. Slack
    2. Trello
    3. Github
    4. Creating meeting notes
  4. General Guides
    1. Style Guide
      1. Tools (screenshots)
      2. Lesson plan
        1. Template
        2. Example
      3. Slides
        1. Template
        2. Example
    2. Presenting
      1. Single plans
      2. Workshop
  5. Roadmap
  6. Learn WordPress site
  7. Resources
  8. FAQ
  9. Old lessons (until Learn launches)

Notes on December 20, 2018 Meeting

Slack Log (Requires Slack login to view. Set one up if you don’t have a Slack account)

  1. Welcome and Meeting Outline
    1. @juliekuehl Welcomed everyone to the meeting and reviewed how the #Training team operates for the new comers and also touched on the outcome of 2018 and the projects accomplished. Julie also outlined the purpose of the meeting and asked about the goals for 2019.
    2. Link to the 2019 Goals post
    3. Suggestion for more videos on our YouTube channel from @fahim.
    4. @courtneyengle suggests:
      • Tag & categorize lesson plans by versions, themes, etc. in Github (digging back to the old Content Audit idea)
      • Purpose statement about videos on Youtube (target audience is those contributing to and accessing materials from the training team, not the end user to be trained)
      • Write guidelines for plugins created by an agency
      • On-boarding buddies
  2. @juliekuehl mentioned that the lesson plans follow Bloom’s Taxonomy (more info) and that there are needs for translating videos from WordPress.tv into lesson outlines.
  3. How to Contribute
    1. Look up projects on Trello.
    2. Review style guides available on our getting started page
    3. GitHub issues are listed out in Waffle.io 
  4. Comments about Gutenberg/5.0 and WCUS
    1. Suggestion on lesson for using 5.0 / differences between old editor and new editor.
    2. Newcomers to WordPress would not need lesson on legacy WordPress.
    3. @fahim links to Health Check Plugin
    4. @courtneyengle How to create a post lesson plan idea – reuse Comparing Classic Editor and Gutenberg for the tasks in creating a lesson plan. Create same plan using both modes.
  5. Meeting Wrap Up and Next Meeting
    1. Next meeting on 3 Jan 2019 and resuming the usual weekly schedule after that.

Time to Set Team Goals for 2019

It’s that time of year when we need to evaluate how we did against our goals for this year and make new goals for the upcoming year.

In 2018 our goals were to:

1. Create handbook
2. Move lesson plans to GitHub
3. Restructure make.wordpress.org/training
4. Fix broken images
5. Update lesson plans for 4.8-4.9/Gutenberg
6. Make workshop recommendations
7. Accessibility workshop

In fact, 2018 was a year where the team underwent a major restructuring of its tool and processes and we accomplished goals we hadn’t imagined when the year started. So our accomplishments for the year can be summed up as:

1. Create handbook (expected by the end of the year)
2. Move lesson plans to GitHub
3. Restructure make.wordpress.org/training
4. Fix broken images (perhaps not all are fixed, but moving to GitHub addressed the problem)
5. Make workshop recommendations
plus
6. Onboarding improvements including a PDF and videos
7. Team management on Trello and in Waffle.io
8. Creation of the https://wptrainingteam.github.io/ page
9. Work towards the relaunch of the learn.wordpress.org site including collaboration with the #design, #marketing, and #meta teams.

Goals that we didn’t quite accomplish include:

1. Update lesson plans for Gutenberg
2. Accessibility workshop

So, for 2019 what should our new goals be? I’d propose a couple to begin with:

1. Launch learn.wordpress.org
2. Create several lesson plans to combine into an accessibility workshop (the ARIA session from WordCamp US has caught my eye…)
3. Use resources from WordPress.tv more often as a basis for lesson plans
4. Collaborate with other efforts such as the diversity speaker training and Kids Camp to get their material available from the learn.wordpress.org site
5. Increase the number of regular contributors to the team

These all seem very do-able. What else should the team be working towards? What should we have for stretch goals? All comments and ideas welcome!

We’ll also be discussing this during our meeting this week. Everyone is invited to join in the discussion!!!

Training Team Meeting Agenda 7 June 2018

Please join us at 19:30 UTC in the #training Slack channel for our weekly meeting!

Today’s Meeting

  1. Design of Learn site
  2. WordCamp EU Contributor Day preparations
  3. Recruitment
  4. Lesson Plan Example: Anatomy of a Theme
  5. Videos
  6. Open announcements / discussion

Welcome to @Govind Kuman @drpepper2soda @njwrigley @abhijitrakas and @grimlord1 who joined the #training Slack channel this week!

NOTE: The “Welcome” item has been removed from the agenda. 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 creates downloadable lesson plans and related materials for instructors to use in live workshop environments.

Getting Involved

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

Team Links:

Proposed Change to Lesson Plan Template

The Training Team has been using the same lesson plan template for the past few years. It works well! I would like to suggest just a couple of improvements to make to more understandable, to provide some additional information about the lesson plan, and to help keep the emphasis on it being a lesson PLAN intended for instructor led training such as meetups, WordCamp workshops, or other such events. (Our focus is not on building online tutorials). Since we are rebuilding many lesson plans from the ground up at the moment, this seems like a good time to make this change.

Current Lesson Plan Outline

1. Description
2. Objectives
3. Prerequisite Skills
4. Assets
5. Screening Questions
6. Teacher Notes
7. Hands-on Walkthrough
8. Exercises
9. Quiz
10. Additional Resources

Proposed Lesson Plan Outline

1. Description
2. Objectives
3. Time Estimate
4. Prerequisite Skills
5. Teaching Materials
6. Readiness Questions
7. Teaching Strategies
8. Teacher Notes
9. Lesson Overview
10. Exercises
11. Differentiation Strategies
12. Assessment
13. Additional Resources
14. Hands-on Walkthrough

What Changed?

  • “Time Estimate” is added (and will be confirmed or changed base on testing experiences)
  • “Assets” is renamed “Teaching Materials” to be more understandable
  • “Screening Questions” is renamed “Readiness Questions” to be less intimidating
  • “Teaching Strategies” is added to help identify the best way to convey the material
  • “Lesson Overview” is added to provide a true plan for the lesson
  • “Differentiation Strategies” is added to provide ideas on how to accommodate different learning styles and speeds
  • “Quiz” is renamed “Assessment” to be more about whether the objectives were met and less about whether students “passed”
  • “Hands-on Walkthrough” is moved to the bottom so that the Exercises, Assessment, and Additional Resources don’t get overlooked, and to somewhat de-emphasize it.

I took the liberty of testing out the proposed template for the Content Editor Overview lesson plan if you want to see an example.

Thoughts?