Recap of May 10, 2018 Meeting

@juliekuehl: First up today is the 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 There are many teams that people can participate in, each with a different focus. info. That is a card that should be useful to anyone who wants to help with the training team during a contributor day. The marketing team graciously helped to create a Training Team specific onboarding document, which is uploaded to that card.

@juliekuehl: It has just basic info on which accounts would be needed to help the team ( 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., TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the team uses for example:, 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., SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at…)

@juliekuehl: The other Trello card related to Contributor Days is this one, which is specific to 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. EU in June.

@chetan200891 @davidneeham is there anything else that you would need to lead that effort? I know we’ll need a list of lesson plans that would be good ones to work one. That’s a rolling list though.

@juliekuehl: This document is also meant for Contributor Days, but it’s going to be helpful for anyone new to the team:

@juliekuehl: There are several options there on how to jump in and get started.

@juliekuehl: So with that Google Doc in place (and it should move to the Make site before WCEU) I think we have what we need for Contributor Days now. So I think if anyone wants to represent the Training Team at any Contributor Day, we have materials to help them do so.


@juliekuehl: Slides have been a hot topic for years and the issues surrounding them have been documented here We had talked about using Reveal.js as our solution for slides, but recently had the #accessibility team recommend Show-er. I did run it by a 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 person as to whether that would work on the site and got a thumbs up.

@juliekuehl: So I wanted to be clear that our slide solution at this point is Show-er, not Reveal and we’ll get some documentation and workflows put together around that.


@juliekuehl: Ideally we would have one stylesheet for all the slide decks that could be updated and all that would be needed is the markup (HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites.?, md?) file.

Learn.WordPress.Org Site

@juliekuehl: So that’s it for item 2 on the agenda, but it leads into item 3 – the site

The Trello card has some information on it as to how we can get started to design and actually start using that domain.

@juliekuehl: We need to create a TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. ticket for the #meta team and alert #design and #marketing to get their input too. There are some wireframes on that Trello card too as a rough concept of what that site could look like. But the idea would be to be able to push lesson plans from GitHub to the Learn siteLearn site The Training Team publishes its completed lesson plans at which is often referred to as the "Learn" site.. (which may mean we need to slightly adjust how we are working with the master branches).

@juliekuehl: I can get that Trac ticket started as I would think it would be weeks/months before all the details would be worked out and we’d be able to actually get things together for that.


chetan200891replied to a thread: But the idea would be to be able to push lesson plans from GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. You mean embed. Correct?

@juliekuehl: That’s some of the details that would have to be worked out by the #meta team.

@juliekuehl: Just so everyone is aware, both the Make blog site and the Learn site are not your typical WordPress installs and they have quirks and restrictions that we have to work within. The #meta team are the ones that can help us navigate that.

@juliekuehl: I wanted to wait until after today’s meeting to get that Trac ticket started. So if you have any thoughts about it, please either DM me or drop your thoughts on the Trello card or here in the #training channel. I’m sure it will take me a few days to write it up and get it submitted.

Team Survey

@juliekuehl: We have gone through so many changes in the past few months and there are many new faces here in the channel. I will admit to having lost track of who is all here and what brings them to the team.

@juliekuehl: Apologies, since I know I’ve chatted with several of you. But I think it’s time to get a little more information from folks regarding interests and skill.

@juliekuehl: I would like to ask everyone to consider filling out the information here just so we have a better understanding of what you are interested in and able to help with. This is an optional form. You are not required to participate, but it would sure be helpful , to get the work of the team moving forward. Currently the info is restricted to just team leadership (there’s about five of us).

@tmichellemoore: @juliekuehl Would you be able to summarize the changes? I understand the team has been around for a while but am just curious as to why so many changes in the short time I have been here. I am not averse to change, just trying to gauge is it constant or was there something that happened recently?

@juliekuehl: The underlying big change was the move to GitHub. There were many reasons behind it: the loss of our image assets on the Make site, the difficulty in managing the lesson plan workflow, the difficulty in maintaining them and keeping them up to date, and there was no “workspace” everything was publicly available as it was being worked on (people were finding old, half-written info and that’s not good), and last, the Make site was intended to be a handbook (like every other team) – not the place lesson plans were actually published.

@juliekuehl: We made the decision to move probably around the time of WordCamp US and started in earnest around the first of the year.

@juliekuehl: And we had two of the three meeting leaders step away for a few months so there were changes due to that too (meaning I had no idea how it was supposed to be done, so I just made something up)

@pbrocks: Really, we have been talking about this for close to a year, it seems, and we all agreed that what we had wasn’t working and at WCUS, i was able to get FINAL confirmation that the images weren’t ever coming back. so in our meeting that Sunday we went forward full steam.

@juliekuehl: Thank you for asking @tmichellemoore. I really should put that in a blog post for the record.

Trello and LP Workflow

@juliekuehl: After looking at scores of lesson plans, I realized what a wide variation we have in approaches and quality. I think we need a QA step before copyediting. I added a “Lesson Plans Needing Instructional Review” list to the board.

@juliekuehl: Before having folks go through with a fine-toothed comb looking for typos, grammar, and style, I think we need a forest and not tree review to make sure the lesson plan fits the team’s goals. For instance, @Taylor found two duplicates already. No sense in pushing both of them forward.

@juliekuehl: And if there are any instructional designers here today, BloomBloom's Taxonomy Bloom's Taxonomy is a way of writing lesson plan objectives using specific words so that the objectives can be measured. See for more details.’s TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. standards are lax and objective – assessment connection is practically non-existent in some of them.

@juliekuehl: Now that I think of it, there’s a new role for the team that’s not listed on the Trello board. So if you have any education / instructional design background, that would be a very good place to help out.

@tmichellemoore: I actually have a masters in instructional design.

@tmichellemoore appointed to take control of the list.

Many LP’s lacking Owners

@juliekuehl: Some need to be written from scratch while others need to be updated/rewritten – or possibly just quickly reviewed and pushed forward.

@juliekuehl: Just add yourself to the card as a Member and type your name in as Current Owner on the card and have at it. If you need any help with any part of the process, this is the place to ask!

@juliekuehl: I know it took us a while to get the GitHub workflow sorted out (and we may have just changed it slightly this morning) but we should be good to go now.

@chetan200891: I have worked on this so in Trello work flow Can i check first 3 development checklist?

@juliekuehl: I would say only the first one.

@tmichellemoore: I have a few questions on process: I got a merge notice. I needed to add one more thing to the lesson.
If I had anything I needed to add, could I have added it before the merge or should I wait until the merge request goes through?
Who does copyedit #2?
What do I do with the card once I finish copyedit #1?

@juliekuehl: The reason there are two copy edits (and three testing rounds) is to simply have more eyeballs on the lesson plan. We’ll need to address the whole multiple branches / rebasing / etc. issue (hint hint @pbrocks).

@juliekuehl: But as far as copyediting goes, when you’re finished (meaning the pull request has been merged) we’ll need someone else to step up for the second round and do the same.

@pbrocks: When you have a branch and you do a Pull Request which is a request to merge, like @tmichellemoore is asking about they will get applied to the original pull request. IF you want them to be separate, then ou create another branch.

@juliekuehl: A video is needed to demonstrate / explain

Meeting Time

@juliekuehl: I have one final question before I have to bolt out the door… would moving this meeting up 30 minutes be a problem? Then I wouldn’t have to leave so quickly every time. I may schedule it a half hour earlier next week and see what happens.