Tag Archives: chat recap

Kim Parsell 12:36 pm on March 8, 2014
Tags: chat recap   

Docs Chat: Mar. 6, 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. @sams said volunteers are needed to help with the handbook theme. If you have HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites./CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site./theming skills and would like to help with the theme, leave a comment on this post, or come to the weekly IRC chat on Tuesdays at 15:00 UTC.

2. Docs Issue Tracker: @otto42 added the ability to create issue types for the tracker. @siobhan suggested that we keep the terms list to a reasonable amount. Before adding any terms, we should discuss what terms are needed for 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/ users reporting docs issues, then look at our project needs.

3. 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/.: @jazzs3quence presented 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 proposal at the Featured Plugins Chat on 3/4/2014, and said there were some concerns voiced about the implementation they used, and whether it will actually help resolve the current issues users are having. At their next weekly meeting, they will be discussing the feedback from the Featured Plugins Chat, reviewing the plugin’s goals, and brainstorming new ideas. If you would like to be part of this effort, please attend the meeting on 3/10/2014 at 18:30 UTC. (3/3/2014 team meeting summary)

4. Handbooks: Progress is being made on both handbooks. The Plugin Developer Handbook focus is on creating the content for sections 5, 6, and 12. @philiparthurmoore is working on the outline for the Theme Developer Handbook intro. He and @sewmyheadon talked on Wednesday, and @philiparthurmoore will be working on the intro this weekend.

5. Docs Sprints: The Seattle Docs sprint last weekend went very well, with 13 people contributing. @sewmyheadon wrote a short recap of the sprint, along with the information for the April sprint.

6. Inline Docs: @DrewAPicture said the hook docs initiative surpassed the 80% complete mark this week, with less than 30 files to complete. If you would like to help, you can claim one of the remaining files.

7. Codex: The 3.9 version page has been created, and some information has already been added. The page is marked as a stub, and volunteers are invited to contribute by updating the page. Contact @DrewAPicture if you have any questions.

#chat-recap

Kim Parsell 6:14 am on March 1, 2014
Tags: chat recap   

Docs Chat: Feb. 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: @Rarst is working on fixing parser-related issues. @nlarnold1 is working on resolving issues with the handbook theme. (2/26/2014 team meeting summary)

2. Docs Issue Tracker: @otto42 unveiled the alpha version of the issue tracker earlier this week. The Docs team is providing feedback, and work continues to implement those suggestions.

3. 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/.: @jazzs3quence said there were some minor 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. fixes merged in this past week, and work continues on refactoring the overview. Current needs are writers to assist with tooltip creation, and people to test the plugin, and provide feedback. (2/24/2014 team meeting summary)

4. Docs Project Landing Pages: The landing pages are now complete for all four projects: Codex, Devhub, Handbooks, and Inline Docs.

5. Handbooks: Good progress was made on 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. The new outline is finished, and @hanni and @blobaugh completed migrating the existing content into the new structure. @sewmyheadon and @philiparthurmoore will be working together to get the intro completed for the Theme Developer Handbook, and begin work on the new outline. (2/27/2014 team meeting summary)

6. Contributor Events: There are two contributor events happening this weekend: the Monthly Docs Sprint at the Seattle WordPress 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. group, and the WP Contributor Day in the UK. Both events are on Saturday, March 1. If you aren’t located near either event, you can join in via the #wordpress-sfd IRC channel, and participate virtually.

#chat-recap

Kim Parsell 11:59 am on February 22, 2014
Tags: chat recap   

Docs Chat: Feb. 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: Progress continues. Most of the template work for the code reference is done for the moment. @Rarst now has commit access to the parser repo, and will be working on changes needed for parsing the inline docs. @nlarnold1 is working on resolving issues with the handbook theme.

2. Docs Issue Tracker: @samuelsidler said we should have an initial version soon.

3. 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/.: Per @jazzs3quence, @brainfork will be working on redoing the help overviews due to a display issue. Work continues on adding tooltips. Version 0.6 was released Thursday – please test and provide feedback to the team. (2/17/2014 team meeting summary)

4. Docs Project Landing Pages: Landing pages were created for the Codex, DevHub, and Handbooks projects. The Code Reference falls under DevHub, and will be included there. @siobhan will be adding information to the DevHub landing page, and @hanni will be populating the Handbooks landing page.

I’ll be pulling together a to-do list of outstanding Codex tasks to include in the Codex section. We also need to look at putting together a list of Codex updates needed for the 3.9 release in mid-April.

5. Handbooks: @hanni posted the detailed plans for the Handbooks project this week.

There is now a weekly IRC chat for the Handbooks team – Thursday at 1:00 UTC (5pm PST, 6pm MST, 8pm EST on Wednesday) in #wordpress-sfd. The team held their first meeting on 2/19/2014.

@blobaugh is the new editor 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, and is working with @hanni on a revised outline. There are also several new contributors eager to get started writing.

@sewmyheadon is the editor of the Theme Developer Handbook, and will be working with new contributors @philiparthurmoore and @nudge to move that handbook toward completion.

More contributors are needed for the Theme Developer Handbook, so if you are interested in helping, contact @sewmyheadon or @hanni via IRC, attend the weekly meeting on Wednesdays, or leave a comment on this post.

#chat-recap

Kim Parsell 4:46 am on February 15, 2014
Tags: chat recap   

Docs Chat: Feb. 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: There’s been a lot of activity on the 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/ 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 this past week, primarily by @Rarst and @nlarnold1. Good progress is being made on the design change tickets.

2. Docs Issue Tracker: Per @samuelsidler, @Otto42 is still working on it, and making progress.

During our initial discussions about what we would like to see in the issue tracker, several things were mentioned that aren’t included in initial development. I’ll be working through those posts, gathering a list of those items and posting that list, most likely in a Meta Trac ticket. We can review the list after development is complete, and we’ve been using the tracker for awhile to see what items we may still want to add.

3. 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/.: Per @jazzs3quence, the team has removed the use of title attributes from 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, based on @grahamarmfield‘s extensive accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) review of the plugin, and the fact that those attributes are being removed from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Version 0.6 of the plugin has been released, incorporating those recommendations, and is available in the repo. Please download the plugin, test, and provide feedback to the team. (2/10/2014 team meeting summary)

4. Handbooks: @hanni provided an extensive update on the status of the handbooks, and the plans now being put in place to move the effort forward at a much faster pace. @hanni will be posting the details of these plans early next week.

We also discussed the status of handbooks being produced by the other teams. @netweb brought up a post on Make/Polyglots regarding their Handbook. If you are interested in helping write the Polyglots handbook, @samuelsidler will be posting on Make/Polyglots asking for volunteers.

5. First Steps for Docs Contributors: We received some very helpful feedback from the comments, and changes have been made to incorporate that feedback. If you have not had the chance to review it, please take the time to do so, and leave your feedback so we can get this completed. (original post | draft page)

6. Docs Project Landing Pages: I’ll be creating the landing pages for each of the listed projects this weekend so that each team can begin adding the information about their respective projects. The Inline Docs landing page is a good example to follow. We would like to have these completed by February 28th.

We would also like to thank our outgoing 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., @sewmyheadon, for all of his hard work. We look forward to your continued contributions. 🙂

#chat-recap

Eric Amundson 5:43 pm on February 11, 2014
Tags: chat recap   

Docs Chat Roundup – Feb 6, 2014

1. DevHub Progress

Lots of progress being made on DevHub including new tickets and finalization of URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org structure. Once the handbook theme is done, the handbooks will be moved over to 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/.

2. Docs Issue Tracker

Otto says that it’s coming along. The templates are nearly done and he’s working on some 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. bits and pieces.

3. Docs Sprint

The next Docs Sprint is Saturday, March 1 at 10am PST.

Join the sprint in Seattle, or on IRC at #wordpress-sfd.

4. 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/.

@jazzs3quence and contributors are making progress and have pushed recent updates to 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. Still need testers and contributors.

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team reviewed and advised a change in the way the title attribute is handled.

5. 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.

Kim Parsell is taking over as the Docs Team Rep this week. Congrats @kpdesign and thanks!

6. First Steps for Contributors draft

@siobhan put together a draft First Steps for Contributors document and has collected some feedback already and is refining the doc. We all agree that contributing to Docs will be easier once the Issue Tracker and DevHub are live.

Full IRC Logs

#chat-recap

Eric Amundson 6:41 pm on January 30, 2014
Tags: chat recap   

Docs Chat Roundup – Jan 30, 2014

1. Docs Chat Time

We’re changing the time of the weekly Docs Chat (not Support) to:

  • Thursday 4pm PST
  • Thursday 5pm Mountain
  • Thursday 6pm Central
  • Thursday 7pm EST
  • Friday Midnight UTC
  • Friday 7am ICT

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. of 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//docs is updated and we’ll see you next week.

2. 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.

We’re supposed to choose a new team rep this week, so please go comment on Siobhan’s post, New Team Rep (also, do we need one?).

3. Docs Sprint

The Docs Sprint is meeting this Saturday, Feb 1 at 10am PST.

Join the sprint in Seattle, or on IRC at #wordpress-sfd.

4. 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/.

@jazzs3quence and contributors are making progress, but still need help with:

  1. Documentation contributions for tooltips and overviews
  2. Testing and bug/issue reporting.

5. Docs Project Landing Pages

Per last week’s report, the Docs Team are creating helpful landing pages for each docs-related project that provide an overview of the project and a clear path for contributors to get involved.

Your docs project can add a page to the Projects section where @DrewAPicture posted the landing page for Inline Docs, which is a great example.

@siobhan would like to have these pages complete by Feb 28th and would like a volunteer to oversee this project and make sure it gets done.

6. Administrative Chat

@siobhan would you like to use next week’s new chat time for the Administrative Chat you’d mentioned earlier? Or, do you prefer to schedule this for another day?

Full IRC Logs

#chat-recap

Eric Amundson 7:57 pm on January 24, 2014
Tags: chat recap   

Docs Chat Roundup – Jan 23, 2014

1. DevHub

Things are getting back in gear and progress is being made on 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/. We are working on the test site at developer.rarst.net.

There’s a github repo and currently the bulk of the work is being done by @krogsgard and @rarst, but we’d love to have other contributions.

There’s also a Skype channel for this effort. If you’d like to be added, contact @siobhan.

2. Docs Issue Tracker

Otto’s hard at work on the Documentation Issue Tracker and making progress. More to come . . .

3. Inline Docs

@DrewAPicture and @kimparsell are still making steady progress.

4. Docs Sprint

The Docs Sprint is going back to meeting once a month.

The next 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. is Feb 1. Join us in-person in Seattle, or virtually via IRC in #wordpress-sfd.

5. 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/.

The Admin Help (AH-O2) project now has an AH-O2 plugin in the repo for testing and it’s looking more polished.

@jazzsequence needs help with content for Admin Help and is looking for contributions. There’s now a doc detailing how to add new documentation to the Help overviews too.

If you can help, please join the AH-O2 project:

6. Docs Project Landing Pages

We’ve decided to have helpful landing pages for each docs-related project, each providing an overview of the project and telling contributors all they need to know to get involved.

There is a Projects section where others can add their docs project landing pages.

@DrewAPicture posted the landing page for Inline Docs, which is a great example.

We’re targeting Feb 28th to have these all landing pages complete. @siobhan would like a volunteer to oversee this project and make sure these all get created and posted.

7. Handbook Scope

@siobhan brought up a concern that some of the content in the Handbooks getting out of scope and there was discussion about what’s in, and out, of scope.

Currently, there aren’t formal scope documents for each Handbook, so we should create these and consider adding, or linking to, them from each project’s landing page.

8. Administrative Chat

@siobhan followed up on her proposal for holding an administrative chat to review where the docs team is, discuss how we get new contributors, and float ideas for future projects.

We’re thinking this might best work on a Saturday to avoid work conflicts. @siobhan will suggest a date or two shortly.

#chat-recap

Eric Amundson 1:19 am on January 15, 2014
Tags: chat recap   

Docs Meetup Roundup – Jan 9, 2014

1. DevHub

Things are getting back in gear and progress is being made on 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/.

2. Docs Issue Tracker

Still pending because of the Holidays, but Otto’s planning to work on it soon, if he’s not already.

3. Inline Docs

@DrewAPicture and @kimparsell will be working on inline docs 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.

4. Docs Meetups

Going back to once a month. Next meetup is Feb 1.

5. AH-O2

The Admin Help (AH-O2) project now has an AH-O2 plugin in the repo for testing.

Also @jazzsequence would like help figuring out the content portion of the Admin Help.

Join the 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/. project:

6. Docs Project Landing Pages

We discussed having landing pages for each docs-related project in December and @siobhan posted about First Steps for Contributors.

Ideally, it would be nice to have make.wordpress.org/docs link to landing pages for each sub-project that each give an overview of the project and tell contributors all they need to know to get involved.

Full IRC logs

#chat-recap

Eric Amundson 6:43 pm on January 2, 2014
Tags: chat recap   

Docs Meetup Roundup – Jan 2, 2014

Happy New Year!

Our first Docs Chat of the year was quick as people are still recovering from holiday festivities.

2013 was a good year for the Docs Team and there are a lot of exciting things happening now that should make 2014 even better.

Here’s what we discussed in this week’s chat:

Inline Docs as CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Project

@kimparsell and @DrewAPicture think it best to consider Inline Docs a core project going forward. It began that way and developed into a bit of a hybrid, but most contributors come from core.

Docs 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.

First docs meetup of the year is this Saturday at 10am Pacific/1pm Eastern.

WordPress Documentation Sprint

Saturday, Jan 4, 2014, 10:00 AM

Uptown Espresso
500 Westlake Ave N Seattle, WA

13 Members Went

What We’re Working OnThis month, we’ll most likely continue to work on adding to, and improving, the WordPress Theme Developer Handbook and the WordPress 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.These handbooks aim to teach developers most everything they’d need to know to create a WordPress theme or plugin.Both handbooks are under active development, but are …

Check out this Meetup →

Full IRC logs

#chat-recap

Eric Amundson 6:55 pm on December 12, 2013
Tags: chat recap   

Docs Meetup Roundup – Dec 12, 2013

1. Docs Sprint

There’s another Docs Sprint this Saturday, Dec 14th @ 10am Pacific and you can join us on IRC at #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 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//docs. Please help by grabbing one (or more) pages and updating.

3. DevHub

Still in active development. @rarst is working on the theme for the code reference and @krogsgard is working on the theme for the Handbooks.

4. Docs Issue Tracker

@Otto42 will be developing the issue tracker for Docs. Yay!

Also, Sarah Gooding posted about the Docs Issue Tracker on WPTavern.

5. Admin Help

The Admin Help project has been re-christened AH-O2.

If you’d like to help with this effort, show up on Mondays at 16:30 17:30 UTC in #wordpress-sfd, or get in touch with Chris Reynolds (@jazzs3quence).

6. Awareness of All Docs Projects

@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/. 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