Meeting Agenda for January 11, 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. 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!

Recap of January 4, 2018 Meeting

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

Recap of December 21, 2017 meeting

Github Updates

@juliekuehl: I have been considering using a GitHub page to organize/describe our lesson plans… kind of like we had Theme, User, Speaker groups before. I think that’s the last piece of the GitHub architecture that needs to be thought through/built out before we can move to filling it up with good content! Once that is in place, I think we’re ready to create the screencast of how to use GitHub for our contributors.

Also will probably have a report on the screencast at the next meeting.

SupportFlow

Still testing. No results yet. @josh_mcintyre and @chetan200891 offered to help with testing.

Questions & Announcements

@juliekuehl: I don’t want to deal with this today, but we should put the lesson plan format on the agenda for after the new year.

Also: Continue to do everything in Make until we make the switch to GitHub. The move won’t happen quickly.

@jillbinder questions for @bethsoderberg:

1. How do I create workbooks that are nicely formatted and still editable by #2:
2. We had talked about these modules having a gatekeeper (myself and now also my Community team), so how to move that forward.
3. If there is a way to ensure that any changes are reflected in the course content, slides, and workbooks. Other than just informing the gatekeepers to ensure they do this.

@jillbinder also said: Just wanted to share that I’m actively training people to run the speaker training modules as part of an initiative I’m running in Community and it’s going very well.

2018 Items

Lesson Plan Format

@estes.chris will add lesson plan format to @bethsoderberg goals in tab of HotMess Spreadsheet.

Meeting Agenda for December 21, 2017

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. Github setup updates
  3. Any updates to support flow issue?
  4. Assigning out tasks from lesson plan audit
  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 from WordCamp US, 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!

Recap of December 14, 2017 meeting

Github setup

@pbrocks and @lpinelli are working on the screencast and @juliekuehl is finishing figuring out the logistical pieces/process of the parts of how we’re going to manage individual plans.

Tasks

@see_tutt has a group of volunteers that will be helping our team.

Changes are going to be made in Make for right now and then ported over to github. We will have only one canonical copy.

@donkiely suggested having folks pick the plans that interest them the most and officially assign them. He’ll keep track of where things stand to avoid confusion.

@Josh McIntyre will help @juliekuehl with github and project management.

Slides

@jillbinder wanted to know if we should be including slides with lessons.

@melindahelt said “we moved away from slides for other lessons due to many many factors, but these seem a lot more “static content” slides — and we can’t make everyone happy as far as format so I’m thinking what if we had a PDF of slides, ready to go plus provided a raw text file of all of the text from the slides this way if someone wanted to make their own slides, customize the content, etc they could”

@bethsoderberg said we can’t use non-open-source technology in the production of slides. Also this conversation has been around for years with a lot of the original concern about accessibility of content to all people. Reveal.js is OK but has a barrier of entry to folks who are non-technical. PDFs are bad because they can’t be edited and have accessibility problems.

That being said, there was a brief mention of this at WCUS (_I think_) about allowing for slides to be submitted as extra materials through pull requests in Github.

@juliekuehl thoughts we had decided to go with Reveal.js as an “extra” to the content we provide.

@bethsoderberg: Going back to earlier in this conversation, I like @melindahelt’s idea of including a plain text format.

@juliekuehl: I am almost imagining that our lesson plan is the plain text format and the Reveal.js version is the same but in slide format.

@bethsoderberg mentioned that would be opening a can of worms since we want to revisit the format. Can we decide that using slides reveal.js are ok with a text-only backup? I think @jillbinder‘s workshop participants are totally right that this would help them spread the diversity training more effectively/efficiently.

Not knowing JS shouldn’t be a barrier for edits or changes because they are basically text.

This might work for @jillbinder.

@bethsoderberg suggested using this with just the diversity plans first and seeing how it goes.

Recap of slides discussion by @bethsoderberg:

I think this is the proposed solution based on this conversation:
1. Slides are made using Reveal.js
2. A text-only version is made too (this could happen first if the slide author is not familiar with HTML)
3. Potentially a PDF version of the Reveal.js slides is made available as well.

This leaves three potential things that users/teachers could use/download: the reveal slides themselves (either a download or link somewhere in our resources), the text-only version, and the PDF version.

@juliekuehl suggested a print version -> save as PDF in CSS.

@bethsoderberg suggested simply printing the PDFs.

SupportFlow Problems

SupportFlow is broken. We thought with was fixed, but now we’re not sure. @bethsoderberg and @esteschris are working with Meta to get that fixed.

Questions and Announcements

Question from new member @chetan200891 regarding format of the LPs and if they were consistent.

@Josh McIntyre asked if we have a list lesson plans that need testing. @bethsoderberg said we did but it is out of date.

@bethsoderberg is going to be out towards the end of January/beginning of February and would like more people to help with the rotation of leading the meeting.

Meeting Agenda for December 14, 2017

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. Github setup updates
  3. Assigning out tasks from lesson plan audit
  4. Continuation of any other WCUS Contributor Day discussions re: next steps
  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 from WordCamp US, 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!

Recap of Meeting on December 7, 2018

@bethsoderberg welcomed newcomers and folks who were first timers at the WCUS contributor day.

Note: The Community team meeting conflicts with this. So far we’ll just keep it on our radar.

This meeting is to recap WCUS for those not there and use these notes to start an outline of next steps where we can take.

WCUS Accomplishments
Began to define new processes to make them more scalable
Set up GitHub repository
Audited all the lesson plans in preparation for migration, including those missing images or in need of updating
Brainstormed new lesson plans due to changes in WordPress
Started a new handbook

Goals Defined
1. create handbook based on new workflow
2. move lesson plans into github
3. reorganizing our website
4. fix the broken images
5. update for 4.8/4.9/gutenberg
6. make workshop recommendations from existing plans
7. accessibility workshop
8. consider team roles

Question: Should images wait until the migration to github?
@juliekuehl answered that it would be more efficient regarding the images.
@juliekuehl provided a link to github: https://github.com/wptrainingteam
@juliekuehl provided a link to an LP there: https://github.com/wptrainingteam/child-themes

So it is decided that images will wait but we can start assigning out the rest of the content updates now so long as they are text changes done in make.wordpress.com/training.

@juliekuehl suggested bringing down LPs on Make as they are moved to github

github workflow:
@juliekuehl : We opted for a repo for each lesson plan.
It’s not to terrible to simply copy over what is in Make
It’s cleaning up that takes time
It needs to be converted to markdown

@juliekuehl : Put together a screencast of how to work within github. But the workflow for maintenance and governance might still need work.

@donkiely and @pbrocks suggested ways of automating using either tools or websites that convert to markdown.

Discussion on moving them all over vs. having a workflow first. @juliekuehl suggested assigning lesson plans in Make for copy edits and having @pbrocks do the screencast of working in github. @lapinell will transcribe into an accessible format. @juliekuehl will coordinate on the content of the screencast.

@donkiely asked about ways of keeping track of high-level view of the status of LPs.

@juliekuehl said github projects can handle that.

Workflows
@Josh McIntyre took these awesome notes: https://docs.google.com/document/d/1IrOklPHtJOKi0UtAdVQgZaqdxx7ptEGpn70FJkn9FCw/edit

Here are some highlights:

#1 – we need more people to help lead team meetings. This is a task that anyone who is familiar with our team/workflows/current priorities can take on. Feel free to reach out to me/@melindahelt/@juliekuehl if this is something you’d like to take on moving forward.
#2 We also decided that we’d like to have regularly scheduled team video calls to check in that way quarterly. Our proposed dates for these are the last Thursday of March, June, September.
#3 Our last big check-in of the year would be at WCUS contributor day as it has been in the past
#4 We need to write a handbook

MISC
@esteschris and @donkiely volunteered to check our Support Flow emails – these are emails being sent through the contact forms on our make site. BUT the first time @esteschris tried to email someone back the other day he ran into permissions issues. Also suggested changes to contact form at https://slack-files.com/T024MFP4J-F8B1T80G7-71f05e08c1. Please review by next meeting.

@juliekuehl : I may do the same for the GitHub topics/labels/etc

@pbrocks put the orientation repo on https://github.com/wptrainingteam/info-presentation

Working on content edits over the next week:
@esteschris
@donkiely

Last thing:
@bethsoderberg p.s. I have tried to change the meeting time everywhere it is listed – if folks could tell me if they spot a reference to our meeting time in the wild that is wrong/has an old time, please reach out and let me know!

Meeting Agenda for December 7, 2017 Meeting

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

  1. Welcome
  2. WordCamp US Contributor Day recap and planning re: next steps
  3. 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 from WordCamp US, 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!

Plan for WordCamp US Contributor Day

Hello team! Tomorrow is WordCamp US Contributor Day. We have a few main groups of priorities for contributor day tomorrow. We will plan to split into two groups to deal with the following priorities. Contributors can work on just a piece of this or move to the other group mid-day if they’d like. They are as follows:

Priority A: Audit of Lesson Plans to Identify Needed Updates

  • Audit existing plans for WordPress 4.9 (and, really, 4.8 as well based on summer 2017 release date) and make a list of plans that need content updates.
  • As part of the audit, we need to make a list of any plans that need to be copyedited again.
  • We have learned that the images missing from some lesson plans can not be recovered, so as part of the overall audit would like to replace screenshots included in the plans.
  • We should take a hard look at WordPress 4.8 and 4.9 and create a list of any new features that need to be addressed in the “WordPress 101 Track.”

Priority B: Building a Team Roadmap for 2018

  • We need to finalize our new meeting time.
  • We need to take the ideas discussed over the summer regarding our new planned workflow and create a plan to implement these ideas. I am anticipating this is a huge task that will take much of the day. Our notes on next steps for implementing a lot of this are contained in this meeting recap post from 9/12/2017.

We have not heard from team members who can not make it in person about times for a video call, so we are not currently planning to have one. I think we should plan to recap WordCamp US on a team video call in a meeting over the next few weeks instead. Tomorrow we will document everything we do and share through the Make site and Slack.

 

11/21 and 11/28 Team Meetings Cancelled + Asynchronous Planning for WordCamp US Contributor Day

Hello team! Last week we decided in our weekly team meeting that we will not have any more formal meetings before WordCamp US. This means that our regularly scheduled meeting TODAY, 11/21, and next Tuesday, 11/28 at 19:00 UTC in the #training channel of the WordPress Slack will NOT happen.

We will adjust the meeting time after WordCamp US. Based on the results of our Doodle survey and multiple conversations over the course of recent team meetings, the weekly team meeting is likely to be rescheduled to Thursdays at 19:30 UTC after WordCamp US. Please post any last comments/thoughts/issues with the new meeting time on our post about the survey as soon possible.

We DO still need to finish planning for WordCamp US Contributor Day (in Nashville on December 3rd) as a team. This conversation should continue asynchronously in the #training channel and in the comment thread of our 2017 WordCamp US Contributor Day post. We will formalize an agenda in the next week and a half as WordCamp US approaches. If you are not available to attend WordCamp US in person and want to participate in a team check in at some point that day, please comment on the post with your interest and availability that day (please include time zones with all times or use UTC time!).

Please ask any questions you have as comments on this post or in Slack! I am looking forward to seeing many of you at WordCamp US and regrouping virtually with all of you in Slack.

Thanks team!