Docs Chat Recap, Oct. 1, 2015

Here’s a recap of the Oct. 1, 2015 Docs Chat:

Attendees: @nlarnold1, @lizkaraffa, @justingreerbbi, @justinsainton, @liamhogan, @slaffik, @samuelsidler, @drewapicture

Chat Archive (must be logged-in to Slack to read, sorry):

  1. Project Updates
    1. Theme Developer Handbook@lizkaraffa
      • @iwritten and @thoronos have been working on some good things the past week or so. @lizkaraffa will be going on maternity leave soon and feels that the “ship” can likely steer itself in her absence. Sounds like @thoronas might be a good point of contact as he knows most of what’s going on with the handbook currently.
    2. HelpHub@hlashbrooke
      • @hlashbrooke wasn’t able to make it to the meeting, but he posted his update as a comment on the agenda post.
    3. Codex MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies.@drewapicture
      • The Codex Migration project is cruising along. I cleared out the moderation queue for examples the other week and will likely start redirecting more Codex pages in earnest this week based on our progress and readiness.
    4. Inline Docs@drewapicture
      • I recently hit 1,000 commits for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., very possibly about 950 of those were for inline documentation, so yay for continuing to improve the quality of our inline documentation.
  2. “Weekly” Chats
    • We discussed continuing forward with meeting every other week, and doing weekly office hours during the normal chat time in the off weeks. This will allow new contributors to more easily get involved if they know we’ll be meeting/available at a consistent time.
  3. Open Floor
    • @slaffik raised a question about adjusting some now-defunct links for IDE packages on the inline docs standards, @drewapicture will take care of it.
    • @drewapicture is continuing work to improve particularly neglected areas of the core contributor handbook, including the “Automated Testing” article for unit testing.
    • A new contributor asked about how to get involved with contributing to the Codex Migration project, and links/information were shared.