[Crosspost] Training Team Update 26 April 2018

Transcript in Slack

New Trello Board

WordPress Training Team Lesson Plan Development

There are new lists on the board, new cards in lists, and new information on cards.

  1. The START HERE list now has a GitHub workflow card with screencasts of how to work with the lesson plans in GitHub.
  2. There are some Power Ups enabled on the Trello board that we are experimenting with. GitHub, Slack, Custom Fields are likely the ones we’ll keep, but we also looked at Card Aging. (We are limited to three.)
  3. There’s a new list on the Trello board for Team Roles with a card for each role. Descriptions need to be completed and members who are contributing in that role added to the cards.

GitHub Update

WP Training Team

The lesson plans are all in GitHub as separate repos.

  1. There’s a new “repo-template” repo that is meant to be an example of how to set up new lesson plan repos.
  2. The workflow for working on lesson plans has been tested and documented (somewhat). There’s information in Trello on the current workflow.
  3. Rather than commenting in Github, comments are likely better done in Trello.

Lesson Plans in Focus

At the bottom of the https://wptrainingteam.github.io/ GitHub Page there were some ideas on how to combine lesson plans into workshops. The lessons for the “Welcome to WordPress” workshop are our current focus and will be used to further test our new tools and processes. Volunteers needed to help with those!

Recap of April 26, 2018 meeting

Please note that unless otherwise indicated, it should be assumed Julie Kuehl (@juliekuehl) is the one speaking.

Update on Trello Board (https://trello.com/b/BsfzszRM/wordpress-training-team-lesson-plan-development).


First. In the START HERE list, the GitHub workflow card now has links to a couple of screencasts of how to work with lesson plans in GitHub. So there’s a quick overview of how to fork a lesson plan and then how to edit and commit (save changes) lesson plans.

Whether you are or aren’t comfortable with GitHub please take five minutes to see how we’d like that process to work.

Second. We’ve enabled a couple of “Power Ups” on the Trello board. These are just experiments at the moment. We are only allowed three (as far as I can tell) and we’re trying to decide which will be the most useful to the team. Ideas welcome. Trello card created for that. Make comments there.

Right now we have Custom Fields and Aging Card Power Ups, in addition to the GitHub one.

We’ll likely want to have the Slack Power Up added. (Working on that.)

There was a blog post about integrating GitHub with Slack but as it’s turning out, Trello and Slack is going to be much more useful.

If anyone has a favorite Power Up that they’d like to suggest, I’d love to hear in that Trello card how you think it would help the team!

Third. There’s a new list to the right of the board with “Team Roles”. We started talking about these at WordCamp US back in December and I think we should do some more work to flesh those out. Ideally, the description would describe the role and the Members added to the card would be the person(s) who are acting in that role currently. Many of the descriptions need to be completed. And it would be great if every team member would add themselves to at least one of the roles (e.g., copy editing, testing, etc.).

Questions and Comments on Trello Boards

@davidneeham: Who are the liaisons? People on their team or people on our team who coordinate with that other team?

@juliekuehl: Great question!!! I’ve been winding up on other teams’ Make blogs and seeing how they work and what they’ve been up to and it feels like we should be more aware of what they are doing. Lots of chances to work together!

@davidneeham: Gotcha. One of my colleagues is super active in the marketing team. I could help be the liaison there.

@juliekuehl: That’s a team that seems to be doing really interesting things!
We may have things they’d be interested in and I’ve seen things that they are working on that I think we’re pretty interested in too. Add yourself to that card then @davidneeham!

@jillbinder: What’s the role for folks like me who are creating trainings? Content creator?

@juliekuehl: I was thinking those liaison roles would be one of the Training Team members who would keep up with what’s going on over at that other team and see where there might be opportunities to benefit each other. Jill, your role of creating trainings would be under the Lesson Plan Writers role.

@juliekuehl: Design Team and Docs Team were the other two.

@jillbinder: Great work, Julie. You’re taking a huge project and breaking it down to be simple for us, bit by bit.



One thing that was added this was was a “Repo Template” https://github.com/wptrainingteam/repo-template.

It’s meant to be our current best practice for our repos as far as folders and README files, lesson plan template, and even milestone issues. We’ll see how useful it actually is as we go along, but I think it’s always nice to have an example of what we’re shooting for.

@tmichellemoore: Did you decide on a slide deck technology?

@juliekuehl: Yes and no? The “official” slides will likely have to be in Reveal.js due to accessibility and other concerns. But the beauty of GitHub is that if other folks want to add their slide decks to the repo they can. That way they are shared for all to see or use. The final Reveal.js version may wind up being a synthesis of those and part of the final steps before approving a lesson plan for “official” publishing. GitHub is unofficial – a workspace.

The second thing that we discovered this week is that we should be working from “develop” branches and not the master branch. The screencasts that were created reflect this. Thanks to @wpnzach for figuring that out!

The third “revelation” regarding GitHub this week is that it’s probably not going to be a good place for comments. I think we may have talked about having “high-level” comments in the Trello cards and more specific questions about lesson plans in GitHub. But further thought says that if you’ve forked the repo and are dropping comments there, no one is likely to see them. So that means that most, if not all, comments should be in Trello.

And if we can get Trello integrated with Slack, then those comments will appear here and we should all see them and be able to respond as needed.

Questions and Comments on Github

@tmichellemoore: Just one – can I delete the original repository I forked? It is in my account. I want to follow the new forking process.

@juliekuehl: If you’ve forked and made no changes, you can delete that and fork again. If you’ve made changes you want to keep, it gets a little more complicated. This is something we will need to address in a screencast at some point though. It’s going to happen. Frequently.

@tmichellemoore: I changed the branch to develop before forking and it pulls both. So it appears we need to make sure we change the branch before editing.

@juliekuehl: That would be the best practice. Branch then fork. And make sure you’re editing on the new branch. (not on master).

@wpnzach: We have to fork, then branch. We can’t branch on the wptrainingteam repos. Forking the repo grabs all branches.

@juliekuehl: Argh. Sometimes having Owner privileges complicates this for me. Thanks for letting me know @wpnzach. Will make sure screencast reflects this.

Random Ideas


At the bottom of our GitHub Page (https://wptrainingteam.github.io/), there are a couple of lists that were just random ideas I had about combining lesson plans into workshops. As it turns out, those aren’t half bad. I’ve been using the Speaker lessons as guinea pigs as we’ve built out our processes.

I think we should do the same with those workshops. A small group of lesson plans to work with that we can run through the process from beginning to end to make sure our processes work. Shakedown cruise style.

What I’d like to see is the “Welcome to WordPress” lessons built out, edited, tested, and prepped for publish.

Welcome to WordPress

General History of WordPress
What Can You Do With WordPress
One-Click Install Using Bluehost
Dashboard Overview
Content Editor Overview

They are more text and screenshot oriented lessons so should be something that pretty much any of us would be “experts” in. And I believe they’ve already been drafted, but need to be reviewed now that we’re in GitHub.

Can we get some volunteers to take those on and begin editing them? They are all on the “User Lesson Plans Ready for Drafting” list in Trello. All with a deadline of today. (smile).

@tmichellemoore: When I finish editing the current one that I am working on, I can move to that list. Unfortunately it won’t be today. (slightly_smiling_face) But I should be able to start on Monday.

@juliekuehl: I may reach out to a few of you to see how we can get those moving ahead. There may not be much to do to get them over to copy editing and testing.

@jillbinder: When mine are copy-edited, will I be able to review before the edits are assimilated? I’ve got sensitive material that has been tested a lot (informally) that I’m nervous about changes to…

@wpnzach: You can “Watch” a repo to get notifications when a pull request is opened. Basically, you can get a notification whenever someone suggests a change officially, and there is a way for you to comment on it

@juliekuehl: The beauty of Git is that any change never wipes out previous information. It can always be changed back if needed. And nothing can be “pulled” unless it’s been “approved” Reviewing edits are what pull requests are all about!

@wpnzach: If you click that button (shown in Slack image) on the repo you want to watch, you’ll get an email when someone suggests an edit. then, you’ll be able to comment on the edit on the actual pull request, like this one here: https://github.com/wptrainingteam/what-to-do-when-you-forget-your-password/pull/2

Questions and Announcements

@tmichellemoore: The title in the Readme.md of the lesson I am editing is – Creating Your WordPress Talk [and Diversity Speaker Outreach]. The lesson focuses mainly on Creating Your WordPress Talk. Where does the Diversity Speaker Outreach come in? Is that an aspiration or is there supposed to be content on that? It has been throwing me off. Isn’t that really a separate topic?

@juliekuehl: @tmichellemoore and @jillbinder you should probably pass a few comments back and forth on that Trello card regarding that.

Training Team Meeting Agenda for 26 April 2018

Today’s Meeting

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

  1. Trello board overview and update
  2. GitHub overview and update
  3. Lesson plans needing volunteers (see the “User Plans Ready for Drafting” list in Trello)
  4. Open announcements / discussion

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:

Special Meeting 19 April 2018

Please join us at 19:30 UTC for a special presentation!

There have been a lot of changes to the Training Team’s tools and workflow recently. A presentation to go over all the changes is going to be a better way to communicate them than our usual Slack chat. Therefore, this week’s gathering of the Training Team will video presentation (webinar) style. We will be going over the new Trello board and the GitHub repositories and how they (and us!) will work together.

So join us at the usual time but in a slightly different location. We will be using the Zoom meeting service, and a link for the event will be posted in the #training Slack channel shortly before the meeting time. The presentation will be recorded.

If you have any questions (before, during, or after) please ask in Slack! Expect homework assignments!

Team Links:

  • Getting Started (https://make.wordpress.org/training/handbook/) a little out of date at the moment
  • Our Team Blog (https://make.wordpress.org/training/)
  • Our Roadmap (https://trello.com/b/BsfzszRM/wordpress-training-team-lesson-plan-development)
  • Our Lesson Plans (https://github.com/wptrainingteam)


After working with our lesson plans over the last few weeks as we moved them into GitHub, a couple of things became obvious:

  • GitHub project boards are focused on individual issues and their resolution while we are focused on a lesson plan development workflow which happens at the repo level.
  • GitHub project boards get really gnarly when trying to keep track of the issues for over 100 repos on one board.
  • The verification process to make sure the README files in GitHub looked as much as possible as the pages on the Make site has a lot of steps to it, is hard to communicate, and is very time consuming.
  • Nearly all our lesson plans need to be rewritten or at least revisited with new screenshots and updated information.

So two things came out of this revelation:

  • GitHub project boards are not the place we need to be working (but GitHub still is!)
  • We should just consider all our lesson plans as needing a fresh start.

After several discussions over the past week, testing out a few new tools, dredging up some old ones, and talking with other teams, the team is going to make some changes to our processes. To be clear, our basic steps for creating lesson plans hasn’t changed, though. Our lesson plan development process will continue to have these basic steps:

1. Identify and define topic
2. Create first draft (template)
3. Copy edit draft at least twice
4. Review for style guide adherence
5. Release for testing
6. Test in a live event (#1)
7. Collect feedback (template)
8. Incorporate feedback
9. Test in a live event (#2)
10. Collect feedback (template)
11. Incorporate feedback
12. Test in a live event (#3)
13. Collect feedback (template)
14. Incorporate feedback
15. Mark as complete and make available for use

But what we’re going to change is that we will be using a Trello board to manage our lesson plan development (https://trello.com/b/BsfzszRM/wordpress-training-team-lesson-plan-development) in addition to our GitHub organization (https://github.com/wptrainingteam). We have connected the two and will be tracking issues and progress on Trello. (The Trello board is still a work in progress as more cards need to be created.)

What Does All This Mean for the Training Team Contributors?

No doubt there are details yet to be figured out and improvements needed to this process. But it’s a better place to work from that where we’ve been for the past several weeks. Time to move forward with lesson plan development!

  • You’ll need both a GitHub and a Trello account to contribute.
    • The GitHub repos are public and you should be able to see everything there
    • You will need to request to be added to the team in Trello to work with the cards on the board there. (DM @juliekuehl or @pbrocks in Slack with your Trello account email)
  • You should check the Trello board, not GitHub, to see where lesson plans are in the pipeline and what needs doing (aka where you can help out).
  • Anyone can start working on pretty much any lesson plan at this point.

If you have any questions, comments, or ideas, please leave a comment here or start a discussion on the #training channel in Slack.

Recap of April 12, 2018 meeting

Please note I didn’t attend this meeting and did my best to combine distilling with verbatim discussion. If anyone sees a need to change anything, please feel free to do so.

@juliekuehl: The first thing I want to say is that these weekly meetings don’t seem to be long enough to cover everything lately. We may need to explore something else to help get through all the changes we are in the middle of. It could be our blog over at https://make.wordpress.org/training/ or it could be another video meeting or it could be a series of screencasts or it could be more like a Contributor Day where we schedule a few hours to get together (perhaps by video) to get through several topics all at once. I don’t want to answer this today, but just raise the question so that we can think through options.
One hour hasn’t been enough!

So today’s agenda is:
1. Welcome
2. Discussion on verification workflow in GitHub
3. Discussion on lesson plan development in GitHub
4. Updates on other current projects
5. Open announcements/discussions

Discussion on verification workflow in GitHub

We have been moving our lesson plans from our Make site at https://make.wordpress.org/training/handbook/ to GitHub https://github.com/wptrainingteam.

WordPress Training Team

The WordPress training team creates downloadable lesson plans and related materials for instructors to use in live workshop environments.



All of the lesson plans have been migrated over, but not all of them have been verified that they are complete “copies” in GitHub.

The list at https://wptrainingteam.github.io/ is the complete list of lesson plans that were on Make and those with links are those that have been completely verified.

As you can see there’s a long list of lesson plans still needing verification.

@tmichellemoore: @juliekuehl Can you define complete copies? Does it mean it is the exact thing that was on the Make site?

@juliekuehl: It sounds simple, and it mostly is, but there are several steps to that process that aren’t well documented at this point.

@Lisa: Hey @juliekuehl what is the process of verification?

@juliekuehl: Complete copies means that all the spacing, icons, and as many images as we can recover have been duplicated on GitHub.

@Lisa: That’s what I need to document. It took me awhile to work out the process and there are several steps to it. I need to put together a screencast and a step-by-step document so that others can duplicate the process. That’s on me.

@Dess: Hi @juliekuehl I tested the Getting Started with WordPress Workshop https://docs.google.com/document/d/1Xm2DI0CtF-QKeb6uH8YCZSGmc8YCwscFASm1HrFBiaY/edit. Also translated it to Spanish

@juliekuehl: So for folks wanting to jump in and help with that process, know that nearly all the “how to help” documents right now probably aren’t accurate.

@Dess: I would like to help migrate that Workshop. And maybe we could also add a space for Spanish in Github?

@juliekuehl: @Dess, that’s terriffic! And also something we’re not quite sure what to do with at the moment. Translations aren’t something that we had considered, to be honest. Do you have any ideas on what that space in GitHub would look like? A branch of the lesson plan?

@bethsoderberg: We’ve always wanted to enable translations, I think a branch would make total sense.

@Dess: We could replicate the page in Spanish.

@Lisa: Isn’t there a translation plugin you can install to WordPress.

@pbrocks: Translations, I think need to be a branch. I should consult with the Docs team first before claiming that.

@juliekuehl: If we created new repos for each language it could get to be a nightmare. I would like to ask some of the other WP teams how they handle translations in GitHub.

@pbrocks will help getting first timers up to speed.

@juliekuehl: Good point @pbrocks!

I think there’s not much more we can resolve around the verification workflow at the moment.
This project is where that is being recorded FYI: https://github.com/orgs/wptrainingteam/projects/2

So lets move on to the second item on the agenda

Lesson Plan Development

That would be this project https://github.com/orgs/wptrainingteam/projects/3. @chetansatasiya asked if he could help and drafting lesson plans seemed like the best fit. So there are now 36 lesson plans in that project that have nothing but placeholder text in them. All of those are available for people to assign to themselves, fork, and start working on.

For anyone who wants to just ignore all this migration stuff and get on with what we do.

They are shown in no priority, but plugins would be the least important ones. If you choose to begin working on one, you can also drag it over to the Drafts column. @Dess, that might be where your Spanish version could come in

@juliekuehl: To my point that I started the meeting with, I am wondering if we should have “office hours” where new folks could stop by.

@tmichellemoore: @juliekuehl I think that would be great!

@juliekuehl: To do: document process by next week!

Current Projects

@juliekuehl: Our page at https://wptrainingteam.github.io/ is ugly, ugly, ugly.

@chetan200891 has shown interest in helping to make it better looking and probably more useful too. I have also asked the #design team to work their magic to come up with a plan for that. If they can design something, @chetan200891 is willing to build it out. He also found a tool that can help do that. Do you have that info @chetan200891? It would be using a Jekyll theme, which is supported by GitHub. https://jekyllrb.com/

@juliekuehl: We are on the design team’s Trello board, but they did not have their meeting this week.

@Lisa volunteered to help the design team

@juliekuehl: @Lisa, if you have ideas about the design, you’re welcome to work on it!

@juliekuehl: I’m just eyeballs deep in other stuff, so design isn’t going to be my thing right now.

@Lisa and @chetan200891 will work together to make that happen.

@juliekuehl: @chetan200891 to your point about GitHub, the bigger question is what would we want to use that integration for? Pull requests seems a good place to start.

@Lisa: Maybe explain what we do and join us? With new topic suggestions?

@juliekuehl: I think the best way to proceed here is to create a couple of blog posts regarding these possibilities.

Idea Period

@tmichellemoore: It would be nice if the integration could place a notification in this slack channel when a lesson is assigned and then when it moves to another lane in GitHub.

@juliekuehl: Let’s save those (really great) ideas for that blog post so we don’t lose them.

@Lisa: There are so many changes going on in WordPress this year

@juliekuehl: Info flows by in Slack so quickly we lose good stuff here!

@pbrocks: I like the idea of working in Github. Which means capturing ideas in Github, whether it be a Repository or an Issue in a repository.

@juliekuehl: Explain further @pbrocks.

@pbrocks: So, I agree that things get lost in Slack too easily. Github feels like the place to capture and document.

@Lisa: I like designing visually

@juliekuehl: @pbrocks did you mean for our welcome message and such?
It sure could be set up as an issue and we could all comment

@pbrocks: So, @Lisa I wouldn’t think that you would design there, but add to the list of ideas that we may have.

@Lisa: We could try opening thread each time a topic is raised

@tmichellemoore: How does the blog fit in the overall picture?

@juliekuehl: The Make blog will not be going away. We will continue to use that site for a proper handbook where all the questions that everyone is asking would be answered: what do we do, how can you contribute, what’s the process, etc. It’s such a messy time for you new folks. Sorry about that!

@Lisa: I will select a lesson plan draft and arrange design time. Julie should I wait until the verification process is ready.

@juliekuehl: To-do: record screencast for @tmichellemoore to document.

@juliekuehl: I know this team is a bit chaotic at the moment with all the changes, but I really appreciate folks stepping up to help. Sometimes even before we’re ready! But we’re making great progress and should be running smoothly again soon. Thanks for hanging in there everyone!

Slack Integration with the Team GitHub Account

Since we are moving our team’s workspace to GitHub, it is possible to connect GitHub with the team #training channel in Slack. We would be able to get notices when activities take place in GitHub. What activities you ask? Things like:

  • issues
  • pulls
  • statuses
  • commits
  • deployments
  • public
  • reviews
  • comments
  • branches
  • commits:all

We can choose which of these, if any, we think would be useful to be notified of in the Slack channel. We can turn them on or off as needed if the are/aren’t working for us.

Is this something we want to do? Now? Later? All of it? Some of it? Please share your thoughts in the comments below!

(More info available at https://get.slack.help/hc/en-us/articles/232289568-GitHub-for-Slack)

Automated Greeting in the #training Slack Channel

It is possible that we could set up a Slackbot to send a greeting when new people join the #training channel. (Hat tip to the #design team for this idea.) What would we want to see in that message?

Proposed content (add your ideas in the comments below!):

Welcome to the WordPress Training Team! We create downloadable lesson plans and related materials for instructors to use in live workshop environments. This all-volunteer team needs people with all kinds of skills!

Here are some handy links to get started in our community:

  • The Make WordPress Training blog is where you’ll find meeting agendas and summaries https://make.wordpress.org/training/
  • We communicate in the WordPress Slack #training channel. If you have questions, this is the best way to contact the team.
  • Check out our GitHub page to get an overview of what the Training Team is working on. https://wptrainingteam.github.io/
  • Take a look at our GitHub account where the actual work is done. You can find our in-progress lesson plans there too! https://github.com/wptrainingteam
  • We have more details in our handbook https://make.wordpress.org/training/handbook/
  • Finally, introduce yourself in the #training channel on Slack. It would be great to know where in the world you are located, what brings you to the training team, what your skills/background might be, and how you would like to contribute!

Great to have you onboard 🙂

(Note that the actual bot will need to be created by a WP Slack Admin.)

Meeting Agenda for Thursday 12 April 2018

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

A brief agenda for the meeting:

1. Welcome
2. Discussion on verification workflow in GitHub
3. Discussion on lesson plan development in GitHub
4. Updates on other current projects
5. Open announcements/discussions

If you have any other items to add to the agenda, please list them in the comments. If you have progress updates but will not be able to make the meeting, please comment on this post or leave a note for the team in Slack. We’ll see you soon!

Contributor Days and Contributor Drives

We have been talking about both Contributor Days and Contributor Drives recently and it’s easy to get them confused. So here’s what they are and how they differ.

Contributor Days

The Training Team has held a number of Contributor Days over the years which have been attached to a variety of WordCamps. Contributor Days in general are in-person events usually held the day after a WordCamp where volunteers come to offer their skills to help with the various WordPress teams. It is possible that these would be one-time contributors and not regular team members. The Training Team has taken advantage of these to do everything from annual planning, lesson plan drafting, copy editing, and style guide discussions. The Contributor Day for WordCamp US has been a big event for our team for at least the past 3 years.

Contributor Drives

Contributor Drives, on the other hand, are meant for ongoing, routine projects that can make quick, significant contributions directly to the team. The projects for these drives should have a low barrier to entry for new or infrequent contributors, so identifying projects and/or tasks that appeal to a range of skill/experience levels will be very helpful. It is possible that these would be one-time contributors and not regular team members.

Keep in mind that, unlike a Contributor Day, Contributor Drives are shorter events (just a couple hours, depending on the project) that allow contributors to quickly take on and contribute to projects that further the goals of the team. It is possible that these can be virtual as well as in-person events.

If I’ve mis-portrayed anything here or you have further details or ideas, please feel free to leave a comment!