Recap of October 13, 2015

Slack Log  (Requires Slack login to view. Set one up if you don’t have a Slack account)

1. Welcome
2. Recap of last meeting
3. Lesson plans status and questions
4. Testing status and questions
   1. Feedback provided on “Anatomy of a Lesson Plan” via Pittsburgh WP Meetup
5. Update on slide decks from tested plans
   1. Upcoming blog post with a list of tested plans that we’re looking to collect slides from, hopefully in the next week
6. Continuation of the location of team documentation discussion
   1. Our handbook is currently being used to store our lesson plans.  This is confusing for those looking for our handbook.
   2. Pain point: the confusing nature of the “empty” lessons that have been started with just the template and are sitting there in the handbook
   3. Suggestion to make the lessons plans that are in-progress not public
   4. The web address https://make.wordpress.org/training/handbook/ says that it is a handbook, but in fact it’s the parent page for Lesson Plans. (@courtneyengle)  It reads visually as a page error – I was waiting on something to load (@irishguy)
   5. No matter where we store Lesson Plans – that top page for them is awfully blank… like no book cover art.  It’s just a jump to the table of contents.  It’d be weird if that were a paper book
7. Review of plan to ensure accurate lesson plans and call for volunteers to get this started
   • Moving forward we will use a new column in our Lesson Plan Tracking Spreadsheet  titled “Ongoing Review” to identify the lessons that need to be revised because of changes to WordPress itself. Team training will divide responsibility for monitoring changes to WordPress itself between regular contributors to the team and contributor day volunteers. The tracking process will cover major or point releases and will include the following steps:
     1. We will use the change logs found in the Codex (example: https://codex.wordpress.org/Version_4.3) and the release blog posts (example: https://wordpress.org/news/2015/08/billie/) to determine whether there are plans that need to be updated.
     2. If a component of WordPress is significantly changed in an update of the software itself then we will run a keyword search to flag ALL lessons that mention that component.
     3. We will review the flagged lessons and remove any from the list that aren’t affected.
     4. Any lesson plans with confirmed updates required based on updates to WordPress itself will be redirected to the team training queue of plans that need content updates made to them
8. Upcoming Contributor Days
   1. Documentation on current WordPress releases can be found in the Codex (see Current Version of WordPress at https://codex.wordpress.org/WordPress_Versions) and on the Blog in the “Releases” category.
   2. We’re only looking for possible inaccuracies on the lesson plans that are approved for testing.
      1. One person to scan through the point releases and make sure nothing beyond security stuff is in them that would impact the plans. It is identifying “if a component of WordPress is significantly changed in an update of the software itself” and noting what that change is.
      2. Run a keyword search to flag ALL lessons that mention that component.
   3.  @mikemueller volunteers to start reviewing lesson plans approved for testing compared with WordPress 3.9.  Mike Mueller and @judylwh will collaborate for WordPress 4.0 accuracy.

#content-audit, #contributor-days, #procedures, #slides