Tag Archives: chat recap

Kim Parsell 11:45 am on May 26, 2014
Tags: chat recap   

Docs Chat: May 22, 2014

Thank you to everyone who came.

The following is a summary of the topics discussed.

1. Deprecated files issue: @siobhan asked us to discuss Item 1 under Current Priorities in the DevHub chat summary – does it make sense to use @deprecated tags in the file headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. of deprecated files? The consensus reached by the team was @deprecated tags should not be used in a file header to designate a file as deprecated, or that it contains deprecated items.

2. DevHub: The weekly chat summary included a list of the team’s current priorities, which includes several open MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets. There was also an explanation of the team’s current organization structure and goals. They currently need feedback on code reference explanations, as well as the proposed search results badges.

3. Handbooks: @samuelsidler posted a summary of the weekly Handbooks chat containing the current status of both Developer Handbooks. Good progress was made on both, and there are several new contributors. If you’re interested in helping, you can contact @blobaugh and @sewmyheadon at the email addresses listed in the post. A reminder that the next Docs Sprint is Saturday, June 7, 2014 at 10am PDT – they’ll be meeting in-person in Seattle, and virtually in #wordpress-sfd.

4. Admin Help: @Clorith said the team is defining components (work flows) for user testing. They’ll be looking into doing more in-person testing at local WordPress meetups and WordCamps, which will eliminate potential time constraints from user testing services. I suggested they also reach out to 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/. 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. organizers for help in identifying areas that new users are struggling with. (weekly chat summary)

For anyone unable to attend, you can read the chat logs here.

#chat-recap

Kim Parsell 1:47 pm on May 17, 2014
Tags: chat recap   

Docs Chat: May 15, 2014

Thank you to everyone who came to the meeting on Thursday.

The following is a summary of the topics discussed.

1. DevHub: Work continues on moving the parser out of alpha. @siobhan posted a list of the project’s current priorities/issues, along with a list of other issues that need to be resolved. There are also several MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets open. If you are interested in helping out, you can attend the weekly chat on Tuesdays at 19:00 UTC.

2. Admin Help: @trishasalas stepped down as project lead, and @Clorith will be the lead moving forward. The weekly chat discussion included user testing and other options for identifying problem areas for users.

3. Handbooks: @blobaugh posted a summary of the Handbooks chat, along with the current status of the 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer Handbook. @sewmyheadon will be wrapping up work on the new Theme Developer Handbook intro this coming week. Contributors are still needed for both handbooks, so if you’re interested, please attend the weekly chat on Wednesdays at 21:00 UTC.

4. Reserved Terms: We discussed how to resolve #27962. There needs to be a generic, top-level reserved terms list somewhere in the Codex/handbooks. Right now, the only place that list appears is in the register_taxonomy() Codex page, and is hard for developers to find. We discussed where such information would be on DevHub – a general, best practices area for developers, or in one (or both) of developer handbooks. Several options were suggested. For now, we decided to do a Codex page so the Trac ticket can be closed. @trishasalas volunteered to take responsibility for completing that task.

For anyone unable to attend, you can read the chat log here.

#chat-recap

Kim Parsell 4:06 pm on May 11, 2014
Tags: chat recap   

Docs Chat: May 8, 2014

The weekly chat was held at the new time (17:00 UTC). @sivel and @samuelsidler made the changes to the IRC chat topic and the 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/ main page to reflect the new meeting time.

@jerrysarcastic is on a dotorg rotation for 4.0, and will be helping with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. docs. Welcome back Jerry!

The following is a summary of the other topics discussed:

1. DevHub: There’s been some work done on the code reference theme, including review and inclusion of some work by @trishasalas. Improvements to the search results template are also in progress.

2. Admin Help: The team discussed the user testing results, and started making plans for the next round of tests, using the same starting point (working with themes). They also discovered an interesting limitation in the user testing (soft limit of 15 minutes to complete the task) which they will need to account for in future tests.

3. Handbooks: @samuelsidler posted a summary of the Handbooks chat containing the current status of the 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer Handbook. @sewmyheadon has been working on combining the new Theme Developer Handbook intro (Part 0) with the existing intro, and should finish work on that this week. The Seattle Docs Sprint last weekend had 5 contributors – 3 worked on the Theme Developer Handbook, and 2 worked on the Plugin Developer Handbook.

4. Inline Docs: Hook docs cleanup to improve the code reference continues in #26869. The focus for 4.0 will be improvements to the functional docs in core.

5. Codex Updates for 3.9: We still need help with pages that need to be updated or created. There are some questions about whether the keyboard shortcuts for editing media are working properly.

For anyone unable to attend, you can read the chat log here.

#chat-recap

Kim Parsell 11:29 am on May 3, 2014
Tags: chat recap   

Docs Chat: May 1, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: The new code reference is now live. The team is working on code reference improvements, and work continues on the handbook theme and 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.

2. Admin Help: @Clorith said the team is moving forward with user testing, having users do goal-oriented tasks which focus on one area of the admin at a time to identify specific pain points. The test site uses real data provided by @jazzs3quence. He also represented the team at Tuesday’s Featured Plugin meeting.

3. Weekly Chat Time: I asked whether we should change the weekly docs chat to an earlier time on Thursday that would be more convenient for team members to attend the meeting. Discussion will continue in a separate post.

4. Handbooks: We had a new handbook contributor join the chat. @topher1kenobe worked with @siobhan at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Austin’s contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., getting set up to work on the handbooks. He also talked with @blobaugh about working on the Plugin Developer Handbook.

#chat-recap

Kim Parsell 8:31 pm on April 25, 2014
Tags: chat recap   

Docs Chat: Apr. 24, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: @siobhan said @nacin, @otto42, and @coffee2code have been putting the finishing touches on the parser and the code reference theme this week, and version 1 of the new code reference is almost ready to be deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. now online.

Nacin, Otto, and Scott

2. Admin Help: @jazzsequence said the team discussed the personas that @jerrysarcastic provided. Other discussion included whether to continue reviewing older user testing videos or focus on finalizing the plans for new user testing, as well as possible solutions, including admin tours.

3. Handbooks: The contributor handbooks have a new design, thanks to @sonjanyc! @samuelsidler deployed the new theme this week to all of the contributor handbooks across 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/ (thank you Sam!). We need to make a decision whether to keep the Pages list at the top of parent pages and style it, or to remove the list entirely, so please leave your feedback on the post.

4. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.: The Docs team needs to provide feedback on changing a text string in Trac ticket #27196. Anyone interested that may have a better way to explain the error is welcome to comment and/or provide a patch.

5. Contributor Experience Survey: @jenmylo posted the WordPress Contributor Experience Survey – 4 questions, none are mandatory. Please take the survey, then post, tweet, and tell your co-contributors/community members about it so they can take the survey too.

#chat-recap

Kim Parsell 12:52 am on April 19, 2014
Tags: chat recap   

Docs Chat: Apr. 17, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: Parser and theme work is ongoing. @DrewAPicture will be pitching in to help the team finish up work on both.

2. Admin Help: @trishasalas said work continues on reviewing the original user testing videos. @jerrysarcastic attended this week’s meeting, and has volunteered to help with video reviews and preparation for the next round of user testing.

3. Handbooks: @blobaugh is reviewing the current content in the 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer Handbook, and making notes for the spreadsheet. He still needs to review existing content in the Codex that can be moved over.

4. Inline Docs: We’re done with hook docs – yay!

5. Codex Updates for 3.9: @siobhan put together a list of Codex pages that either need updated or created for the 3.9 release. If you have some time and want to help, please grab a page and make the appropriate edits. Anything not done before April 25th will be available for contributors to work on at the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Austin Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/..

6. Community Summit: There is a proposal to hold another community summit this year as part of WordCamp San Francisco. Anyone wishing to discuss doing another retreat-type summit instead of adding community discussions to the WCSF agenda should leave a comment on the post.

#chat-recap

Kim Parsell 3:01 am on April 5, 2014
Tags: chat recap   

Docs Chat: Apr. 3, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: Work continues on the parser, and has resumed on the code reference theme.

2. Admin Help: @Clorith said the team is still reviewing existing user tests to identify pain points in admin areas that haven’t been updated since the original tests were conducted.

3. Handbooks: @blobaugh is currently reviewing the existing content in the 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer Handbook. He also plans to review content in the Codex to see what can be moved over to the handbook. @sewmyheadon wasn’t able to attend the chat, but sent a reminder about this weekend’s Seattle Docs Meetup – Saturday, April 5th at 10am PDT. You can also attend virtually in the #wordpress-sfd IRC channel.

4. Docs Conferences: The list of talks was announced Thursday for Write The Docs NA. Both @siobhan and @DrewAPicture will be speaking – “Writing For Your Other Half” and “Putting the (docs) Cart Before the (standards) Horse“.

5. Miscellaneous:

• IRC Chat Times: Please review the listing for your group’s weekly IRC chat to be sure the times are correct. I pulled info from IRC logs and posts on make/docs to make the corrections for the DST changes.

• Handbooks Master List: @DrewAPicture asked whether there should be a master list of all the handbooks (coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./plugin dev/theme dev/team-specific) and who the point of contact for each is. If so, where should that live? The handbooks the Docs team is responsible for are listed in our handbook. It was suggested we could include a list of handbooks available on other Make sites in our handbook, with a link to each handbook and a point of contact.

#chat-recap

Kim Parsell 7:31 pm on March 30, 2014
Tags: chat recap   

Docs Chat: Mar. 27, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: @siobhan said there are two issues left to address with the parser. Once that is finished, attention turns to completing the handbook and code reference themes. (3/25/2014 team meeting summary)

2. Admin Help: @jazzs3quence said they are looking back at the original user testing videos, and prepping for new user tests. They have received some good feedback on the list of admin tasks. Starting this week, the weekly meeting on Mondays will be held at 17:30 UTC.

3. Handbooks: @blobaugh said he received an email from @jdgrimes, offering to donate some tutorials on unit testing for the 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer Handbook. @sewmyheadon said there is nothing new to report on the Theme Developer Handbook. He said the next Docs Meetup in Seattle is April 5th, and hopes for another good turnout to work on both handbooks. You can attend in person in Seattle, or remotely in the #wordpress-sfd IRC channel.

4. Codex Updates for 3.9: The Codex will need to be updated after 3.9 is released. @siobhan suggested we go back to doing a virtual sprint for the updates. We can build the task list for the sprint from the 3.9 version page that @DrewAPicture is working on.

5. Upcoming Docs Conferences: I posted earlier this week about upcoming docs conferences. @siobhan will be speaking at Write The Docs in Portland in May. I’ll be attending the OpenHelp conference in Cincinnati in June. OpenHelp contacted @siobhan about whether we plan to send a team and/or sponsor this year’s conference in Cincinnati.

6. Docs Chat Time Change: Starting this week, the meeting time will shift to 23:00 UTC on Thursday to get us back to our old schedule – 4pm PDT, 5pm MDT, 7pm EDT, 12am London (Friday).

#chat-recap

Kim Parsell 4:43 pm on March 23, 2014
Tags: chat recap   

Docs Chat: Mar. 20, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: Work continues on fixing parser-related issues. @siobhan posted on Make/Core, looking for volunteers to help with the parser and the handbook theme. If you would like to work on the project, leave a comment on the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post, or come to the weekly IRC chat on Tuesdays at 19:00 UTC.

2. Admin Help: @trishasalas said the group’s current focus is on discovering what problems users are currently having, and addressing those with appropriate solutions. @designsimply has agreed to help with user testing. The team will start with a few simple tests, and see what those reveal. They are compiling a list of tasks to be used during testing. If you would like to be part of the effort, please attend the weekly meeting on Mondays at 18:30 UTC. (3/17/2014 team meeting summary)

3. Handbooks: I asked @samuelsidler when the Theme Developer and 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer handbooks would be moved over to DevHub. He said he wasn’t sure, but there are some encoding issues that may require them to be moved manually. @siobhan said it was important to retain the contributor information to be used on the Credits page for each handbook.

4. WordPress Core Style Guide: Fred Clay Meyer and @joshlevinson attended the meeting to discuss their proposal for a WordPress Core Style Guide. Discussion centered around how they could best present their ideas to the core team to begin the discussion. The team suggested that Fred put together a proposal to present at a core dev chat after 3.9 is released.

#chat-recap

Kim Parsell 1:19 pm on March 16, 2014
Tags: chat recap   

Docs Chat: Mar. 13, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: Work continues on fixing parser-related issues. @samuelsidler said volunteers are still needed to help with the handbook theme. If you would like to work on the project, leave a comment on this post, or come to the weekly IRC chat on Tuesdays at 16:00 UTC.

2. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.: There are some big changes, and a new direction, for both the team and the project. The new co-leads are @trishasalas and @Clorith. @jazzs3quence will still be involved in the project in a supportive role. Their weekly meeting on 3/10/2014 was used to discuss the Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. Meeting, and the feedback @jazzs3quence received regarding the current implementation of the 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. They also began laying the groundwork for the new direction the project will take. If you would like to be part of the effort, please attend the weekly IRC chat on Mondays at 18:30 UTC.

3. Handbooks: @sewmyheadon and @hanni met on Wednesday to discuss the current status of the handbooks. @philiparthurmoore has made progress on the Theme Developer Handbook intro. @sewmyheadon still needs to review it.

4. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Style Guide: The team discussed a post that proposed a community-written (and maintained) style guide for WordPress Core to follow. The consensus was that WordPress has its own voice, and there are places where that voice could probably be refined a bit. A WordPress Core style guide could be written, but it would be a canonical reference rather than a community-driven guide.

5. New 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/ Profiles: @jenmylo reached out to the team reps a few weeks ago about identifying people in each team to get badges on the new profiles that are being worked on. At some point they hope that the process may be automated, but for now, the profile badges will be manually added. I have already provided a preliminary list of names of team members.

6. In-House Mentorship Program: @DrewAPicture and I talked to @jenmylo and @andreamiddleton about the program at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Phoenix in January. They hope to kick off the one-month ‘contributor onramp’ within the coming month. The team discussed what the requirements are, what tasks we could have someone work on for the one-month contributor onramp, and possible mentors.

7. Group Chats Calendar for WordPress Project: @GaryJ brought up the idea in IRC for a group chats calendar that people could subscribe to. @siobhan said this would be a project for the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team, if a decision was made to implement one. Concern was expressed that, without a maintainer, the calendar could end up with incorrect information listed. The consensus was that the chat times listed in 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. for each of the Make blogs should be sufficient for now.

#chat-recap