@juliekuehl: I think a Contributor Drive could be just what we need to get the old Make handbook shut down in the next few weeks, but I’m not sure it can move that fast. Is anyone interested in volunteering to take a closer look at that Contributor Drive info and see how we can work with it? If not, I should have more time to look at it this week than last.
Tabled for next week.
WordCamp 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
Attending: @chetan200891. @zzap is looking for a Training Team representative for WCEU.
@chetan200891 offered to be the representative. @bethsoderberg offered to help with preparations.
Confusion between Contributor “Day” vs. “Drive.”
@bethsoderberg: what we’ve done in the past for WCUS is make sure that we have a number of well-defined tasks on the docket and available for people to work on. that way when people show up, there is a clear path forward for them contributing. we can work on this as a group as WCEU approaches.
@juliekuehl: Contributor Drive is much the same but not event-oriented.
@lisa is interested in helping with the drive.
GitHub 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. https://github.com/ Workflow
@juliekuehl: Workflow is coming together. Our GitHub Page (https://wptrainingteam.github.io/) has been updated with some recent info. That’s the spot where we wanted to have a complete list of our lesson plans because that would be easier to look at than the list of repos The Training Team uses GitHub for working copies of lesson plans. You can find them at https://github.com/wptrainingteam. on the GitHub team page. It’s just plain HTML 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. and CSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site., so anyone with CSS skills could make a significant difference there. It’s workable for now but could be better.
@juliekuehl: We could also put workshop “recipes” on that page. Combinations of lesson plans for specific topics / audiences / time constraints.
Discussion of # of lesson plans and repos. @juliekuehl: But that question alone indicates why that https://wptrainingteam.github.io/ page is valuable.
@juliekuehl: Does anyone want to shepherd that page and set up the links to the GitHub repos for the lesson plans, essentially mimicking the setup at the old Make site? Users, Plugins, Themes…
That would only be a couple of hours work to create lists of links to the repos.
@juliekuehl: OK, that’s already an issue in GitHub if anyone wants to pick it up.
@juliekuehl: @lisa you might not be able to see this. I will need to get you added to the team on GitHub so that you can, I believe.
@juliekuehl: But if you look at https://github.com/orgs/wptrainingteam/projects/2 you can see the things that need doing which are what Contributor Drives or Days could help us with along with our regular weekly contributors
@juliekuehl: But we do actually have two projects in GitHub – one to move the lesson plans over and one TO ACTUALLY CREATE LESSON PLANS. yay!
@juliekuehl: Speaking of which… those projects do wind up being “private” because of the way GitHub works. It can’t be changed. Yet. It’s a feature request that I’ve spoken to them about, so maybe it will change. I’d love for all of that to be available to anyone who wants to take a look.
@juliekuehl: So our other project https://github.com/orgs/wptrainingteam/projects/3 actually has some issues on it too. So if anyone is bored with this whole moving stuff over and wants to dig into creating lesson plans, there’s a few out there that can be worked on.
@juliekuehl: So one thing that’s happened this past week is that I did get some time to work on getting lesson plans set up which has helped solidify the workflow. We will need to set some guidance for tags on issues and milestones, but the columns alone are a good starting place for now. Any guidance (and I don’t have exclusive rights to this AT ALL!) would be over at the https://github.com/wptrainingteam/contributor-resources.
@juliekuehl: I did want to mention for @jillbinder as well as everyone else that the all the repos should have folders (eventually) for images and slides. We talked last week about using the README files in the slides folder so folks could include links to slides they’ve created or they can upload the files and make a note of that one the README. So I think that’s a piece of the workflow that we’ve sorted out.
@juliekuehl: And I did take the latest edits from the old Make site for the speaker lessons and this one is a great example https://github.com/wptrainingteam/creating-great-slides. It has a bunch of images embedded in the lesson plan.
@juliekuehl: We might want to make this too part of the workflow, or style guide
Check out https://github.com/wptrainingteam/creating-great-slides/tree/master/images with the list of images there. I think it would be a good idea to use descriptive file names for all images because they’re a lot easier to spot in that list than IMG_001.png, and we could easily have multiple IMG_001.png files.
@jillbinder: I have a request. My team is stuck on how to train our trainers (on running the Speaker Training lessons). Could someone be my contact person for training questions?
@bethsoderberg: I can, though I am going to be out of commission for a week or so soon. @juliekuehl also happy to help.
@juliekuehl: @jillbinder I know you have several issues that you’d like to discuss. One of which I want to mention before we go – translations. We’re going to need a strategy / workflow for dealing with translations in GitHub. So I’m just going to drop that bomb here right before we finish up.
@bethsoderberg: I’ll think on that one, as you’re right that it’s a bit of a bomb in terms of size/complexity.