Title: Docs Meetup Roundup – Dec 12, 2013 Author: Eric Amundson Published: December 12, 2013 Last modified: February 27, 2014 --- [ ](https://profiles.wordpress.org/sewmyheadon/) [Eric Amundson](https://profiles.wordpress.org/sewmyheadon/) 6:55 pm _on_ December 12, 2013 Tags: [chat recap ( 49 )](https://make.wordpress.org/docs/tag/chat-recap/) # Docs Meetup Roundup – Dec 12, 2013 ## 1. Docs Sprint There’s another [Docs Sprint this Saturday, Dec 14th](http://www.meetup.com/SeattleWordPressMeetup/events/137556472/)@ 10am Pacific and you can join us on IRC at [#wordpress-sfd](https://make.wordpress.org/docs/tag/wordpress-sfd/). It’s our last scheduled sprint of the year. ## 2. Admin Screen Updates WordPress 3.8 includes a makeover of the WordPress Admin, so we need to update the Administration Screen pages in the Codex. [@kimparsell](https://profiles.wordpress.org/kimparsell/) will post a list of pages that need to be reviewed and updated on make.wordpress.orgWordPress.org 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. [https://wordpress.org/](https://wordpress.org/)/ docs. Please help by grabbing one (or more) pages and updating. ## 3. DevHub Still in active development. [@rarst](https://profiles.wordpress.org/rarst/) is working on the theme for the code reference and [@krogsgard](https://profiles.wordpress.org/krogsgard/) is working on the theme for the Handbooks. ## 4. Docs Issue Tracker [@Otto42](https://profiles.wordpress.org/Otto42/) will be developing the issue tracker for Docs. Yay! Also, Sarah Gooding [posted about the Docs Issue Tracker](http://www.wptavern.com/coming-soon-an-issues-tracker-for-wordpress-documentation) on WPTavern. ## 5. Admin Help The Admin Help project has been re-christened AH-O_(2). If you’d like to help with this effort, show up on Mondays at 16:30 17:30 UTC in [#wordpress-sfd](https://make.wordpress.org/docs/tag/wordpress-sfd/), or get in touch with Chris Reynolds ([@jazzs3quence](https://profiles.wordpress.org/jazzs3quence/)). ## 6. Awareness of All Docs Projects [@DrewAPicture](https://profiles.wordpress.org/DrewAPicture/) voiced a concern that the Docs Sprints have been focused almost solely on the Handbooks, while there are several other docs-related responsibilities beyond the Handbooks, like Admin Help, Codex, Inline Docs, etc. We’ll work to make sure that all Docs projects get exposure and it’s clear how people can get involved and participate. Since participation at the Sprints has been usually between four and ten people, often with a few new contributors, we’ll need representation from  other projects to attend meetups and/or provide instructions ahead of time, to help meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. participants get involved in the areas that suit them. [#chat-recap](https://make.wordpress.org/docs/tag/chat-recap/) ### Share this: * [ Threads ](https://make.wordpress.org/docs/2013/12/12/docs-meetup-roundup-dec-12-2013/?share=threads) * [ Mastodon ](https://make.wordpress.org/docs/2013/12/12/docs-meetup-roundup-dec-12-2013/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/docs/2013/12/12/docs-meetup-roundup-dec-12-2013/?share=bluesky) * [ X ](https://make.wordpress.org/docs/2013/12/12/docs-meetup-roundup-dec-12-2013/?share=x) * [ Facebook ](https://make.wordpress.org/docs/2013/12/12/docs-meetup-roundup-dec-12-2013/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/docs/2013/12/12/docs-meetup-roundup-dec-12-2013/?share=linkedin) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2013%2F12%2F12%2Fdocs-meetup-roundup-dec-12-2013%2F%23respond&locale=en_US) 1. ![](https://secure.gravatar.com/avatar/d6d6254d551f10047c16ac27288de32bfa5d96a399f1bcf618ac6b49656424f7? s=32&d=mm&r=g) 2. [Chris Reynolds](https://profiles.wordpress.org/jazzs3quence/) 7:05 pm _on_ December 12, 2013 3. It’s [Monday 17:30 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20131216T1730) not UTC 16:30 — the time on the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. hasn’t been changed for daylight savings. 4. ![](https://secure.gravatar.com/avatar/d83d084ee0387ee8c0314fbedc2bc28d017efbb3b724031c93b23bd7ace0cc01? s=32&d=mm&r=g) 5. [bcworkz](https://profiles.wordpress.org/bcworkz/) 12:41 am _on_ December 16, 2013 6. FYI, I made a first pass through most of the Codex admin screen pages linked from the Administration_Screens main page. Most of the screen shots have been updated and I tried to update any text that I noticed needing attention. I probably missed a lot so some tying up of loose ends is in order still. It’s progress at least. 7. * ![](https://secure.gravatar.com/avatar/8bf29c777c4a386cb938cb3afc6fa6398259c5d31103b9704f75feba84b6b385? s=32&d=mm&r=g) * [Kim Parsell](https://profiles.wordpress.org/kpdesign/) 2:56 pm _on_ December 17, 2013 * Thank you very much for doing that. 🙂 * ![](https://secure.gravatar.com/avatar/4afd830f71468aa93bb1c1953c2ad4ed93cd4316bc0a4db3614ff13a775cf4a5? s=32&d=mm&r=g) * [Eric Amundson](https://profiles.wordpress.org/sewmyheadon/) 7:06 am _on_ December 18, 2013 * Yeah, thanks a bunch [@bcworkz](https://profiles.wordpress.org/bcworkz/), you’re awesome! 8. ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662? s=32&d=mm&r=g) 9. [Siobhan](https://profiles.wordpress.org/siobhan/) 8:20 am _on_ December 17, 2013 10. Thanks for this. Just a few comments: 11. **Codex Updating** 12. Was updating the Codex for 3.8 discussed? I know [@drewapicture](https://profiles.wordpress.org/drewapicture/) usually deals with this but he has been very involved with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. during the last release. 13. **Awareness of all docs projects** I think [@DrewAPicture](https://profiles.wordpress.org/drewapicture/) makes a fair point about Docs Sprints being handbook focussed – but that’s because@ sewaheadon has been running them and he’s responsible for the theme dev handbook. I don’t think it’s feasible to always have a representative of every part of the documentation project at every meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area./sprint. 14. As a short-term solution, I suggest rebranding the “docs sprint” that Eric runs to the “Handbook Docs Sprint” as that’s what the focus usually is and it prevents the misconception that all “Docs Sprints” are handbook related. If someone else wants to run a “HooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. Sprint” or a “Codex Sprint” or a “Function Reference sprint” they can do that. 15. Since it’s the end of the year it would be good to have a higher level discussion of where all of the different sub-groups in docs are, what issues we’re facing and how we can help each other to make progress in the coming year. I suggest having a Google Hangout some time between now and December 31st. I’d like to have the following people present: [@drewapicture](https://profiles.wordpress.org/drewapicture/) [@sewmyheadon](https://profiles.wordpress.org/sewmyheadon/) [@hanni](https://profiles.wordpress.org/hanni/) [@kpdesign](https://profiles.wordpress.org/kpdesign/) [@jazzs3quence](https://profiles.wordpress.org/jazzs3quence/)@ sams and anyone else that wants to attend. We could record the hangout and put it on the docs P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at [https://make.wordpress.org](https://make.wordpress.org/) afterwards. 16. What do you guys think? 17. * ![](https://secure.gravatar.com/avatar/d6d6254d551f10047c16ac27288de32bfa5d96a399f1bcf618ac6b49656424f7? s=32&d=mm&r=g) * [Chris Reynolds](https://profiles.wordpress.org/jazzs3quence/) 2:32 pm _on_ December 17, 2013 * Give me a time and I’ll be there. * ![](https://secure.gravatar.com/avatar/8bf29c777c4a386cb938cb3afc6fa6398259c5d31103b9704f75feba84b6b385? s=32&d=mm&r=g) * [Kim Parsell](https://profiles.wordpress.org/kpdesign/) 2:55 pm _on_ December 17, 2013 * Unfortunately, my home internet connection doesn’t support things like Skype and Google Hangouts, and there really is no place here that I could go to with decent free wifi, so I would be unable to attend. * I agree with changing the name of the sprints for the very reasons you listed. * ![](https://secure.gravatar.com/avatar/d83d084ee0387ee8c0314fbedc2bc28d017efbb3b724031c93b23bd7ace0cc01? s=32&d=mm&r=g) * [bcworkz](https://profiles.wordpress.org/bcworkz/) 2:32 am _on_ December 18, 2013 * The Codex was mentioned, “discussed” may be making too much of it, at least on IRC. Maybe more occurred for the physical participants? * It seems “Sprints” of whatever label are one of our best opportunities for progress. Reps from all sub-groups at each meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. is of course unworkable. Perhaps on occasion a particular Sprint meetup can focus on another docs area in need of reaching a short term goal. I’m not convinced it’s feasible to have additional regular sprints for all the sub-groups. What focused energy there is for the current handbook sprints could be shared around a bit IMHO. That would only require a rep for the particular docs du jour be available for a few hours on a Saturday. * Another issue that has stymied progress (besides handbooks) is the apparent lack of a current up to date document outlining what immediate work needs to be done. Presumably the issues tracker will resolve this, but the fact remains some people are not good self starters and perform better when directed. Not everyone willing to help will readily review a huge dataset to find something that sounds good to them. For such people, sprint coordinators could use a short list of immediate needs requiring little skill that could be doled out to volunteers. * Some people want to help with an immediate need regardless of the subject. Large datasets imply there is an unofficial shortlist beyond a hypothetical tracker’s “Urgent” tag of which 30% of all issues are so marked. People want to feel like their effort has an immediate benefit. Being personally directed to do something reinforces this. Lots of people know their interests and are just fine with finding tasks they can do. But don’t underestimate the power of directing certain resources. The hard part is deciding which group a volunteer falls into with only the briefest of interactions, and actually having that short list. - ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662? s=32&d=mm&r=g) - [Siobhan](https://profiles.wordpress.org/siobhan/) 6:23 am _on_ December 19, 2013 - I agree that at the minute it’s not that easy to help out. However, we should have the new devhub theme up and running soon at developer.wordpress.orgWordPress. org 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. [https://wordpress.org/](https://wordpress.org/) so that should make things much easier. - Since [@sewmyheadon](https://profiles.wordpress.org/sewmyheadon/) is coordinating the sprints, it might make since for him to gather together task lists from the various groups. * ![](https://secure.gravatar.com/avatar/4afd830f71468aa93bb1c1953c2ad4ed93cd4316bc0a4db3614ff13a775cf4a5? s=32&d=mm&r=g) * [Eric Amundson](https://profiles.wordpress.org/sewmyheadon/) 7:55 am _on_ December 18, 2013 * **Codex updating** * [@siobhan](https://profiles.wordpress.org/siobhan/) – I checked in with [@drewapicture](https://profiles.wordpress.org/drewapicture/) before our Sprint last Saturday and he mentioned that they’d whipped the 3.8 page for the Codex into shape. * **Awareness of all docs projects** * I definitely think [@drewapicture](https://profiles.wordpress.org/drewapicture/) has a point with the visibility of the Handbooks being high. This is largely due to: a. My big mouth. b. I’m organizing the sprints. c. A Docs Team member asked in one of our weekly meetings a few months back if I could organize a second monthly MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup. com will help you find options in your area. so we could make more progress on the Handbooks. So, that’s what I’ve done. * While my posts on the Meetup site do mention working on the Handbooks, we do have contributors that work on other things and we discuss other projects too. * Personally, I’m not a fan of the re-branding these _Docs Sprints_ as _Handbook Docs Sprints_ for a few reasons: - **It’s easier to _sell_ a WordPress Docs Sprint** and get participation if people have more choice in the way they contribute. - **It’s our problem, not theirs.** We, on the Docs Team, realize this is an issue, but contributors are showing up and helping now. We’re not packing the house, but are consistently getting 6 – 10 contributors each Meetup from US, Canada, and UK and not all have worked on handbooks. - **We can make it easier.** The Sprints are helping with progress, so we should work to make it easier for people to get involved in the project of their choice. * The biggest issue, as [@bcworkz](https://profiles.wordpress.org/bcworkz/) mentioned, is that the barrier to entry still seems high for a new contributor. It’s not clear where to go to find things that you can do to contribute, unless you have a bit of guidance. * The Sprints really help with that. I don’t always write as much as I’d like during Sprints, but I’m able to help others get up to speed and many are coming back and contributing again. * I’m hoping that the Docs Issue Tracker can help, along with a clear, simple, prevalently-linked _Getting Started for Docs Contributors_ guide. This guide could link to pages for each specific docs effort, containing instructions for how to get involved with individual efforts/projects within the Docs Team. * If the Issue Tracker can allow us to categorize issues by project (AH-O_(2), Handbooks, Inline Docs, etc), it might function as an effective, if partial, to-do list for contributors. * I agree that it’s not feasible that a Team Member from each part of the project attend at every Sprint, but they could attend some, or if they need specific help from contributors at a Sprint, can post specific tasks that folks can work from. * **Group meeting** * I’m in. Suggest some days and times that work for you, but I’m pretty available with relatively few meetings from here through the end of the year. - ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662? s=32&d=mm&r=g) - [Siobhan](https://profiles.wordpress.org/siobhan/) 6:36 am _on_ December 19, 2013 - **Codex updating** - By Codex updating, I don’t mean whether the 3.8 page was updated – I mean have all of the new features and functions been added? Tasks include: * Have the screenshots been updated to show the new UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.? * Has the widgets page been updated for the new widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. panel? * Has the process for installing a theme been updated? * have all of the new functions been added to the function reference? * Overall – has the Codex itself been updated to reflect 3.8? - This is what we’ve come up with in the past: [https://make.wordpress.org/docs/2012/11/27/if-all-goes-to-plan-wordpress-3-5-will/](https://make.wordpress.org/docs/2012/11/27/if-all-goes-to-plan-wordpress-3-5-will/) - **awareness of docs projects** - It may be easier to _sell_ a generic docs sprint, but I’m not convinced that it’s better overall. By having more focused sprints it makes it clear ahead of time what is expected of people. That means that they can make a decision beforehand about whether it will suit them or not. A person who might be interested in helping with the inline docs probably won’t think about going to a Docs Sprint but they might come along to an Inline Docs Sprint. Similarly, there’s not always opportunity for people to write user docs, for example, on a sprint that’s focused on handbooks. People can end up feeling dispirited because they have to spend their time editing and they don’t feel that’s the best use of their time. - Yes, you may get less contributors, but you’ll get more focused contributors, and you won’t end up in a situation where people come along and aren’t sure where to fit in. People will know in advance if they’ll be able to help out. - It isn’t particularly easy to get involved right now, but two things that should happen within the next month should help: * moving the handbooks to devhub (imminent!) * the docs tracker - I agree that a Getting Started for Docs Contributors Guide would be useful. I’ll put it on my task list and have it ready for the new year 🙂 - — - **Meeting** - As Kim can’t do a Skype/Hangout, I suggest that we do IRC instead. I reckon next week is out because it’s boxing day, but how about [January 2nd at 22:00 UTC+7](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20130102T1500) * ![](https://secure.gravatar.com/avatar/d83d084ee0387ee8c0314fbedc2bc28d017efbb3b724031c93b23bd7ace0cc01? s=32&d=mm&r=g) * [bcworkz](https://profiles.wordpress.org/bcworkz/) 10:43 am _on_ December 19, 2013 * Re: Codex updating. I’ve tried to address the first 3 tasks you listed, but not having an authoritative list to work from, changes were applied haphazardly as I stumbled upon them. I am not at all confident that all related aspects were addressed. * The new functions have not been addressed, the version_3.8 page contains mostly redlinks for the new functions listed. So clearly the Codex is not updated for 3.8, though thanks to new screenshots, many people will not notice. * The 3.5 list was awesome, the 3.8 rollout desperately needed something similar. No single person can possibly know where all the changes need to be applied. It takes our collective knowledge to compile such a list. But first it takes someone to step up and coordinate the effort, which apparently did not happen this time. * ![](https://secure.gravatar.com/avatar/479f05d4acc73915a43b24a1ee3f30477d4ee19bbec6a5a79906d396f2b2d2ad? s=32&d=mm&r=g) * [Sam Sidler](https://profiles.wordpress.org/samuelsidler/) 9:58 pm _on_ December 19, 2013 * Give me a time and I’ll be at any meeting you’d like me at. ### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/docs/2013/12/12/docs-meetup-roundup-dec-12-2013/?output_format=md#respond)󠁿 You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2013%2F12%2F12%2Fdocs-meetup-roundup-dec-12-2013%2F&locale=en_US) to post a comment. # Post navigation [← Hook Docs sprint today](https://make.wordpress.org/docs/2013/12/11/hook-docs-sprint-today/) [Types of Issues for the Issue Tracker? →](https://make.wordpress.org/docs/2013/12/13/types-of-issues-for-the-issue-tracker/)