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 (


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”

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 (, 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:

Questions and Announcements

@tmichellemoore: The title in the 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.