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)

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.)

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)

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!

Meeting Agenda for Thursday 29 March 2018

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

A link will be posted in the Slack channel just before the meeting begins.

A brief agenda for the meeting:

1. Welcome
2. Training Team and Contributor Days
2. Discussion on on new workflow in GitHub
3. Updates on other current projects
4. 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 (actually) see you soon!

Recap of March 15, 2018 meeting

We have been working on setting up our GitHub presence:

All the lesson plans from Make ( https://make.wordpress.org/training/handbook/) are now there in their own repos.

And we have a project set up to track the remainder of the work in making sure everything has been converted as best as it can be.

The lesson plans in Make were converted and dropped into GitHub, but we need to verify what was brought over and add issues for missing images or anything else that needs attention.

I’ll be perfectly honest that I’m not 100% certain of the best/easiest workflow to make that happen.

We have put together a couple of draft screencasts to show how we’ve been doing things, but it seems the process could be improved.

I can share those screencasts though.

They’re pretty rough and I’d like to combine them into one more “official” screencast to show the best practices. So, I’d love to get some feedback on those videos and the process they show to see if there is a better way we could be doing things.

Also, I should add that one of the things that needs to be done is to basically compare the Make lesson plan to the GitHub lesson plan and take note of the differences.

We do want to get to the point that all changes are coming in through Pull Requests (or emails) eventually

I may write a post on the Make site to spell out the steps we should go through to get all the repos (aka lesson plans) in a verified state. Once they’ve been verified we can go back to writing, copyediting, testing, and publishing!

This is more in-depth than a chat can handle. And screencasts are very helpful too.

That’s something to be aware of too on GitHub.

I may copy those step there too.
So I know a few of you have been wanting to help. I’ll get those instructions up there and then you can just pick a lesson plan and start comparing the Make to the GitHub versions and we’ll be on our way!

@pbrocks: I think we add instructions on Make, on Github, and as a post here in Slack.

@juliekuehl: Absolutely

@bethsoderberg: I can also test out what you all have as I’m in the unique position of knowing exactly what we were trying to do, but haven’t actually been able to do anything for a little while.

@kashif: How about testing (Delivering the Lesson plans to audience and provide Feedback) procedure , is that same as previous?

@juliekuehl: At the present time, yes. But we may want to address that as we get further into using GitHub.

@kashif: I am already doing that since more than 6 months, I am working with a Government Training project (more than 1000 Students Graduated so far) and Leading WordPress Curriculum and I have taken several lessons from Training.

@kashif: It will be really helpful if I can have some kind of Questionnaire to ask for feedback from trainers who delivered the course.

@juliekuehl: Questionnaire is exactly what is needed. But it might take the form of an issue template in GitHub. But I’ve also seen ways to have Google Forms create issues. Still looking into options.

@davidneeham: I have a template that I use for all of my training. I can contribute that as a starting point if we don’t have anything official yet.

@bethsoderberg found the previously-used form. https://make.wordpress.org/training/handbook/about/testing-lesson-plans/instructor-testing-feedback/

@bethsoderberg: We actually have lots of documented thoughts on testing and feedback from testing, but @juliekuehl is right that we’re not quite ready to absorb new feedback while we’re in the middle of the migration to GitHub. Though submission of feedback to that old form will be collected we just can’t promise that we’ll go through it right away.

@kashif: I guess Google or any other form will be easy to collect and compile feedback, I have 30+ trainers who will be providing feedback on lessons.

Agreement that feedback can wait until the migration is complete.

Discussion on feedback as a separate project on GitHub vs. an issue for each repo.

@juliekuehl: This brings up a good point. I did not bring the About section from https://make.wordpress.org/training/handbook/about/ into GitHub. I would expect much of that will remain on Make as a proper Handbook as intended for that site.

I think what needs to be done for the immediate future (meaning this week) is…
1) Get a better screencast of the verification process.
2) I wanted to add image and docs folders to each of the repos.
3) Everyone start pitching in on that verification process.
It would be great to put the migration process to bed in a couple of weeks!

@juliekuehl: I want to say thank you to the new people on the team. You’ve jumped in at a time that is not typical of what this team does. I appreciate everyone’s willingness to help and patience as we work through this migration.

@pbrocks: How do you add images?

@juliekuehl: @pbrocks I’ll need to add an image folder so image files can be uploaded. Then we can link to the images stored in GitHub.

Open announcements/discussions

@juliekuehl: We’ve scheduled 4 videoconferences per year, including one for the end of March.

@bethsoderberg: We should do it.

@juliekuehl: We should. This GitHub stuff would benefit from a video chat.

So we will have a video meeting next week.

Special note: @bethsoderberg had a baby named Reading, “Pronounced like the town, market, railroad, etc. He’s also being called Red.”

Daylight Savings started here,

so if you’re in most US states, we’ve switched from xST to xDT, which will affect our meeting time, no? That is, if we stick to 20:30 GMT, the East Coast is now -4 hours, as opposed to -5 hours. West Coast US is now 7 hours different from GMT in the West Coast of Wales.

Meeting Agenda for 22 February 2018

Please join us later today at 20:30 UTC in the #training Slack channel for our weekly meeting! A brief agenda for today:

1. Welcome
2. Update on GitHub transition (including icons)
3. Update on speaker training lessons
4. Updates on other current projects
5. Open announcement/discussion time

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!

Icons to replace CSS formatted sections on GitHub

I researched The Noun Project icons and learned some interesting things. I have a concern about their giving credit each time we use the icons (that’s a small but added burden with each LP).

With that said, I have some examples below. I’m using links (to avoid having to give attribution).

Otherwise, I’ve looked at a few “free” icon sites and they seem to be aggregators of other people’s work. Having used images and sound files, I know that sometimes the licensing information can be incorrect, either accidentally or intentionally.

Our symbols are simple. I can’t draw a straight line, but I could use Sketch or whatever to duplicate what we already have. In our meeting Thursday we can discuss what the group would prefer.

This is from their FAQ:

What’s the difference between a paid and a free account?
Both free and paid members get access to all the icons. As a free member, you must give credit to the icon’s designer each time you use their icon. NounPro members get unlimited royalty-free licenses (no need to worry about attribution), can download icons in any color, and get access to all of our apps for quicker access.

Note: free icons are black and white only. To use colors (like the WP standardized colors) we must become paid members.

WARNING: Icons must come from the url thenounproject.com. There is a malware site called nounproject.org that installs wonderful “extensions” to the user’s button if they click “continue.”


Serifed “i” in black dot

Serifed “i” alone

Sans Serif “i” in black circle

Italic “i” in black dot


Line drawing of light bulb

Black lightbulb shape


Black waving flag shape

line drawing of waving flag


Warning triangle line drawing

Black warning triangle

Circle with “X”

Black dot with “X” outline

Black dot with white “X”