The WordPress training team creates downloadable lesson plans and related materials for instructors to use in live workshop environments. If you enjoy teaching people how to use and build stuff for WordPress, immediately stop what you’re doing and join our team!
Regardless of your skill set, you can help! We need people to write, copyedit, test, audit, connect, and review our lesson plans. Find out how to get started.
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
3. Updates on other current projects
4. 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!
@juliekuehl announced the screencast for using GitHub is up at https://github.com/wptrainingteam/contributor-resources.
Regarding transferring LPs:
@juliekuehl
I’m not sure if we’re ready for the next step to start moving lesson plans.
We might be, but here’s a couple of things to think about first.
1) We will need to tweak our style guide to reflect the realities of working in GitHub with Markdown rather than at Make with HTML.
2) We’ll need a process to track what’s been done/needs doing.
I’ll start with some thoughts on those action steps:
1) Set up project board in GitHub
2) Work on updating style guide (icons included)
3) Assign lesson plans for transferring/editing
4) Screencast of how to upload images and other supporting files
5) Screencast of how to do pull requests for updates once lesson plans are in place in GitHub
@Josh McIntyre volunteered to do step 1 by looking at the audit file from WCUS and create a list in the project board. Then they can be assigned from there.
@juliekuehl: Regarding the icons, perhaps we could use inline images from The Noun Project. https://thenounproject.com/
@pbrocks posted a “Markdown to GitHub Converter” screencast at http://take.ms/MsLvH.
@juliekuehl requested for @Josh McIntyre have the project board set up by next meeting.
If all tasks are done we may be ready for “The Big Move.”
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
3. Updates on other current projects
4. 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!
@juliekuehl is still working on the GitHub screencast
@jillbinder gave an update on the Diversity Speaker Training: both small and medium to-do items need doing but there is now a deadline of the end of February for an event in Vancouver. Promotion for the the training to be used worldwide in meetups will start soon too, so that helps with motivation!
Also a question about handouts and slides and whether that should just wait for GitHub. @melindahelt suggested to just create what is needed and we’ll figure out the best way to share them, even if it isn’t the final way.
Work on lesson plans has been a little slow because of the anticipated shift to GitHub.
@jillbinder asked about how she could be “gatekeeper” for future changes in some lesson plans. That should also be addressed in the move to GitHub.
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. Updates on current projects
3. Tasks from lesson plan audit
4. 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!
Meeting called off due to lack of attendance.
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. Updates on current projects
3. Tasks from lesson plan audit
4. 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!
@juliekuehl review of the work in GitHub
We have an organization page at https://github.com/wptrainingteam/.
We’re going to have a separate repository for each lesson plan.
That’s the repo that I’ve been using as an example to begin with. The idea is that each lesson plan would be its own repo with a README.md file where most of the work is done and an images folder where we could store screenshots. That way they’d be in the same place and easily changed when needed.
Notice there are a bunch of topics associated with the repo. We’ll need to use those to both make our lesson plans searchable as well as use them for our own organizational purposes.
RE: alerts, code sample formatting: the formatting looks to be mostly the same, but I haven’t tested everything. It’s Markdown and not HTML, so there’s that.
@melindahelt: GH has the option to quote things, etc. We should come up with suggested formatting from that.
@juliekuehl: Also, I’ve created a GitHub Page https://wptrainingteam.github.io/. We can use that as a more public-facing page to help organize lesson plans and/or provide additional info to contributors.
@juliekuehl: The other thing I wanted to point out is the organization projects, such as https://github.com/orgs/wptrainingteam/projects/2. This is what I’m hoping would replace the hot mess spreadsheet as a place to keep track of where things are at.
GitHub account required to view projects but content viewable to all.
@melindahelt: As we talked at WCUS, if someone wants to participate but is against joining GH (say, to just write one lesson plan) they can write and submit ands someone on the team can add it.
@juliekuehl: As far as the process of getting lesson plans into GitHub, it’s pretty manual. It’s a copy and paste from make.wordpress.org and then doing some reformatting. Then it’s a matter of downloading any images from Make and then uploading them in GitHub. Then switching over the links in the lesson plan.
Standard tools for source control (commits, pulls track issues, etc.) work.
@juliekuehl: I’d love it if everyone would test it out a bit more. Take an exisiting lesson plan and try to bring it into GitHub and see where you get hung up. Play with the projects / issues / pull requests to work out the processes. I’d like to break it learning now before we get serious about moving everything over.
We need to document some of the processes. Things like creating issues and working in the projects. We’ll need some information for other folks who want to help out.
@juliekuehl is working on a screencast to cover much of this.
Perhaps next week we will delegate some of the GitHub tasks, such as setting up the public page and organizing the projects a bit better if needed.
Any questions should be referred to @juliekuehl in Slack.
@estes.chris to take recently edited LPs and move them to GitHub.
Please join us later today at 20:30 UTC in the #training Slack channel for our weekly meeting! A brief agenda for today:
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!
@bethsoderberg is out for a few weeks and @juliekuehl for at least this week, so GitHub may stall for a little while.
@josh McIntyre: We worked a little last week on how to set up the Project boards for tracking how lesson plans get updated. Other than that, Julie has more info.
@estes.chris SupportFlow seems to be working now.
@jillbinder couldn’t get some answers from @bethsoderberg before she had to go offline. It sounds from the above message in this meeting that it might be a few weeks before they can be resolved so she will use that extra time before looking at them anyway. If she needs to, she will reach out to someone else or to the channel in general.
Regarding questions on Getting Started and Style Guide LPs from @estes.chris:
It’s possible we’ll use GitHub instead of the status page. There has to be more research on that. The status and proposed LP pages are removed but the info is saved and can be added back.
Skitch seems to not work and isn’t open source, so it won’t be the annotator of choice for images.
Placekitten will still be the placeholder source of choice and the instructions will be updated based on information from @jillbinder.
