DocsWP — WordPress Help

Recap of February 16, 2016 Meeting

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

  1. Welcome
    1. We had a few new folks in the chat and welcomed them by explaining a bit about the team: The training team makes in-person lesson plans for use in workshop/presentation settings. Right now we’re working on a series of user lessons for use in a Hack the Hood workshop in the spring. This is our weekly meeting where we check in with one another about progress on all the things.
  2. Lesson Plan Updates
    1. @kimwhite is going to read over the Managing Widgets lesson plan one more time and then will ping the channel so this plan can go into copyediting.
    2. @melindahelt will have a solid draft of Choosing and Installing Themes by next week.
    3. @skarjune is 90% done with the Managing Menus plan and will ping the channel when it’s done so this plan can go into copyediting.
    4. @bethsoderberg asked the group about the use case of demoing an out of date site for the Managing Updates lesson plan and the group confirmed that pointing the teacher towards out of date theme/plugin/core files to set up a local with out of date stuff makes sense as an approach.
    5. Our in progress priority plans:
  3. Copyediting Updates
    1. @bethsoderberg finished copyediting @chmchm‘s Local Install lesson plan and it is ready for testing. Special thanks to @meaganhanes for testing lots of questions related to that plan on her local machine.
    2. @c3zh‘s What You can do With WordPress plan was copyedited by @toniaslimm and is ready to test.
    3. @juliekuehl‘s Intro to Common Plugins plan was copyedited by @jcasabona and is ready to test – the copyeditors will take one last look at the language in this plan to double check that it refers to the plugins as “common” and doesn’t call them “must-have plugins” per the groups’ conversation about plugin references (notes below).
    4. Managing Media and What is a Theme are still in copyediting for next week.
  4. Lorem Ipsum Generator Update
    1. @chanthaboune reported that there is no preferred generator for Lorem Ipsum, so that we should find something that is family-friendly/fits the overall voice of the project and we will be golden. The group chose lipsum.com as a standard and non-spammy generator to use moving forward. @bethsoderberg will add this preference to the style guide.
  5. 3rd Party Plugins Update
    1. @chanthaboune reported that the rule on 3rd party plugins is that we should only use them when necessary and that they should be in the repo. We should review the ones that have been included in lesson plans periodically (perhaps during content auditing sprints or contributor days?) so that we can make sure they are still following the rules and if they aren’t following rules, then we should raise a flag.
    2. This means that plans that are currently about/reference a 3rd party plugin are fine as long as the plugin is  in the repo and following GPL guidelines.
    3. We should share the plugins that they will get the most use of early on, regardless of who wrote them (within reason… GPL, etc). If there is a non-specific need to include a plugin in a lesson plan, we don’t need to stick to .org plugins alone.
    4. Which plugins can be used in specific ways will be more complex/in depth subject with lessons that focus on plugins/plugin development down the line. For now, the guideline to follow is that the plugins are “in the repo and maintained” for right now, but we want to be sure we know how to plan for the future as the lessons get complex. As such, @chanthaboune will write a P2 post detailing the current plans and we can list all of our concerns/thoughts about the subject of 3rd party plugins in the comments.
  6. Welcome Message
    1. @bethsoderberg wrote a new draft of the welcome message. The goal was to make the whole thing shorter and less intimidating, while being more explanatory about what the team is/does, what we’re doing right now, and what we need help with right now. In the new draft, current activities/needs could be easily swapped out in the future as those priorities change.
    2. @meaganhanes and @mikemueller made some edits to the draft.
    3. @kpegoraro provided feedback that we need to include a reference that explains jargon terms the team uses, which everyone agreed is a very good idea. We made a list of the terms we need to define:
      • P2
      • Tier One
      • User Level
      • Tester
      • Copyeditor
      • Author
      • Sandbox
  7. We ran out of time to talk about the demise of Skitch and our need for a new screenshot annotation tool and to talk about a contributor drive. As such, @chanthaboune will post to the P2 on both subjects.