Dev Chat Summary: June 28th (4.8.1 week 2)

This post summarizes the dev chat meeting from June 28th (agendaSlack archive).

4.9 ideas

4.8.1 planning

  • #40951 & #40907 will be core to the 4.8.1 release being targeted around the last week of July
  • General bug scrub to be scheduled after the 4th of July holiday on the 4.8.1 milestone
  • Component maintainers please review your 4.8.1 milestone and punt to Future Release / 4.9 as necessary
  • Reminder that we are “approaching 4.8.1 tickets as more traditional regression types of issues”

Editor update

Customize update

  • appreciate more people testing 40951.3.diff
  • also appreciate testing of the HTML widget in trunk (see #40907)

REST API update

  • had a lot of new docs contributions at WCEU contributions day
  • have some momentum and hope to build upon it in coming weeks

Dev chat coordination

  • @jbpaul17 looking for 1-2 others out there to help run the weekly dev chats similar to how the Core Weekly Updates are split up
  • A great way for product/project management or otherwise non-engineers to help contribute to WordPress Core
  • Please ping @jbpaul17 if you have interest in helping out!

New contributor bug scrub/open office hours

  • idea is a weekly bug scrub/open office hours focused on new contributors
  • would include tickets tagged good-first-bug and any tickets new contributors wanted to work on
  • Likely to schedule for Wednesdays at 19:00 UTC
  • @adamsilverstein, @welcher, @stevenkword, & @flixos90 to help run the meetings
  • Please ping @adamsilverstein if you have interest in volunteering as well

General announcements

  • @m1tk00: looking for help with the Gallery Widget in the Customizer regarding the edit button
    • need to know how to send the already selected ID’s, when someone wants to edit the gallery
    • will ping @obenland or @timmyc in #core-customize for help
  • @enricosorcinelli: #21676 patched and awaiting review, how to get it more attention?
    • added needs-testing to the ticket, will ping @obenland as Themes component maintainer to review
  • @pbiron: would like to start a “feature plugin” project to work on rewriting the exporter
    • would like to rework ALL of the XML related code in core (e.g., using XMLWriter instead of echo statements, etc)
    • using XMLWriter and with some pretty drastic changes to the WXR markup
    • should be putting the 1st version up on GitHub in few days
    • also written an XML Schema for WXR 1.2
    • will add the feature proposal as a comment to the 4.9 wishlist on last week’s dev chat summary
  • @flixos90: thinking about ways to improve Trac workflow
    • wondering whether it would be possible to automatically set a has-patch keyword once a patch is uploaded?
    • It’s a bad experience for new contributors to search through tickets without a patch, but finding ones that already have one
    • will drop by #meta-tracdev to continue the conversation
  • @jnylen0@enricosorcinelli working on #39732 and #39730
    • 39732 is a sanity improvement and a follow-up to work done around 4.7 in the API, should land soon for 4.9, but it would be good to get more eyes on it especially someone who has worked on comments before
    • 39730 may as well land at or around the same time as the above
  • @welcher: would love some eyes on Load word-count and do not allow our wp-utils script to clobber it

#4-8-1, #core, #dev-chat, #summary