Recap of March 15, 2018 meeting

We have been working on setting up our 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. presence:

All the lesson plans from Make ( are now there in their own reposrepos The Training Team uses GitHub for working copies of lesson plans. You can find them at

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 SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at

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

@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 migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. 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 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.”