Docs Meetup Roundup – Nov 14, 2013

1. Docs Issue Tracker Mockups

@sams sent a wrap-up of Docs Issue Tracker feedback to @karmatosed and she’s going to have something by early next week. When that’s ready, he’ll get a developer to work on it and we’ll have an updated timeline.

Thanks to all who gave feedback on the mockups!

2. Docs Sprints

There’s another Docs Sprint this Saturday November 16th, for those who can join in person or via IRC at #wordpress-sfd.

3. Theme Dev HB Opening

@iandstewart gave us permission to use any of the content from the Theme Shaper tutorial in the Theme Developer Handbook.  Thanks Ian!

@sewmyheadon will work on incorporating whatever makes sense into the Handbook.

4. Theme & PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party HB Spreadsheets Revamped

Authors vs. Contributors

In the Handbook reporting spreadsheets, we changed Owner/Author columns to read Contributors because we found that several of the original owners/authors haven’t worked on the docs in months and we don’t want to discourage other folks from contributing.

So, we’re asking contributors to list their name in the Contributors column for future reference.

Noting Individual Document Progress

If you’re working on docs in the Theme or Plugin Dev Handbooks, please note the percentage complete (based on your best guess) in the % column.  This gives us a more realistic overview of each document’s progress.

@siobhan will also add @sewmyheadon to receive emails when updates are made to the Theme Dev Handbook to better monitor progress.

Retiring the Handbook Reporting Threads

We’ve ditched the old Handbook reporting threads on The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. because they weren’t being updated.

Instead, please note progress, questions, problems, etcetera in the corresponding Handbook Spreadsheets instead, or simply post comments in the Handbook page.

5. Working Online

In order to make sure we’re all “on the same page” (pardon the pun), we’re asking folks to post all Handbook content directly to the Handbook, rather than writing offline.  This helps contributors and editors see actual progress, so they can dive in and help without worrying about stepping on toes or duplicating work.

To this end, we’ll be granting editor access to Handbook contributors so they can work online.

If you are working on any Handbook content that is not yet posted to the Handbook, or if you need editor access, please contact @sewmyheadon, @siobhan, or @hanni and we’ll help get it posted right away.

6. Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. Meetings

@siobhan inquired about the status of the Team Rep Meetings that are organized by @jenmylo. While I heard talk of this a few months ago, there haven’t, to my knowledge, been any team meetings.

7. DevHub

@krogsgard has promised us a theme by Sunday or Monday. Getting the DevHub theme finished should spur some actions and more progress.

Thanks folks and have a great weekend!