Dev Chat Summary: September 12, 2018 (4.9.9 week 5)

This post summarizes the weekly dev chat meeting held Wednesday, September 12, 2018 at 20:00 UTC. Agenda | Slack archive


4.9.9 Planning

We have a Road Map and she is gorgeous. Thank you @antpb and @schlessera for putting it together. Here’s a summary:

Suggested Timeline

We will reassess these dates after the three-week mark:

  • Beta : Monday October 22, 2018
  • Release Candidate : Monday October 29, 2018
  • Release Date : Monday November 5, 2018

Key Focuses

If you’re interested in helping out with these topics, hit up these Slack channels:

*Not real but should be.

Bug Scrubs

  • The plan is to run them weekly in the #core Slack channel across multiple timezones. Schedule 👏 Coming 👏 Soon 👏

Focus Lead and Component Maintainer Updates

Notes and Summary Posts

Additional Updates/Requests

  • From PHP Servehappy: More testers are needed for the WSOD protection on real-life, complex sites to reveal edge cases. A “complex site” is basically any site running locally with random plugins and random code.

If you’re thinking about get all up in these Focus and Component Maintainer teams, try attending a chat. Here’s the comprehensive list.


Open Floor

Tickets

Anyone can submit a ticket for the Open Floor. Send your submission to @jeffpaul or moi (@whitneyyadrich), or comment on the agenda for that week’s chat.

  • #12563: New action on body open – Submitted via @welcher. Will be discussed in the #themereview meeting.
  • #32326: Improve Support for Structured Data – This one pairs nicely with the ticket above, so the conversation should be happening in the #themereview room and scheduled chat.
  • #25280: wp_localize_script unexpectedly converts numbers to strings – Submitted via @adamsilverstein and Ivan Kristianto. Lots of words about code were had in the chat, and then the conversation was moved to the ticket itself.

General Announcements

Dev Chat Schedule

@psykro published his proposal for a second <dev chat> and it’s open for your comments. I’m sure we’ll touch on this during tomorrow’s dev chat, too. 

As always, anyone is welcome to join <dev chat> every Wednesday at 20:00 UTC. As I said in the chat, to sorta quote the late, great Notorious B.I.G.

I’m goin’ go call my WP crew
You go call your WP crew
We can rendezvous in <dev chat> tomorrow around two (or Wednesday at 20:00 UTC)

#summary, #4-9-9, #core, #dev-chat

One DevChat to rule them all…

From – https://make.wordpress.org/core/weekly-developer-chats/

The weekly WordPress core developer chats take place on Wednesdays at 20:00 UTC in the #core channel on Slack. These chats generally last one hour.

The purpose of the meeting is to discuss core WordPress development. This is a working product team meeting, not an open town hall or Q&A session. The focus is on technical issues and release scheduling, and the players are the people who are working on patches for the active core development cycle. Anyone is welcome to attend to keep up with what’s going on in core, but the agenda is generally limited to discussion by active contributors.

At the moment, one dev chat is held every Wednesday. This often makes it difficult for folks in different time zones to attend dev chat.

Multiple teams hold more than one weekly chat. For example Community has two chats, one at 8:00 UTC and one at 16:00 UTC. While this doesn’t cover every time zone, it does expand the opportunity to join a team chat for contributors close to U.S. and EU time zones.

After 4.9.8, it was suggested a discussion be held around adding an  alternative dev chat. 

During the 4.9.8 release cycle, @pbiron and @joshuawold tried  running two independant bug scrubs, one about 10 hours before the usual one, and one at the usual time. The jury is still out as to whether this was a success or not.

During dev chat on Wednesday, 29 August, and after a discussion with those interested in running a second dev chat, it was proposed to hold an alternative dev chat 12 hours before the current chat.

https://wordpress.slack.com/archives/C02RQBWTW/p1535575692000100

Some concerns were voiced during dev chat:

  • @karmatosed mentioned this time is during school hours in EU time zones.
  • @clorith and @afercia raised concerns that two meetings could result in a disconnect between the community and present communication obstacles for decision making.
  • @jeffpaul floated the idea of holding three chats, eight hours apart. This approach is more inclusive of global time zones, but requires additional dedicated volunteers to manage the chats and communicate with the other dev chat volunteers.
  • @jorbin feels that decisions should rarely be made during dev chat highlighting the fact that the dev chats be just that, chats about current development cycles, not a time when decisions should be made.
  • @nerrad (and others) echoed the sentiment that “there’s value in clearly identifying in agendas when a item needs a decision and what chat that decision will be made in ahead of time”

The general consensus was that all of this should be shared in a Make post, so that the greater community could comment on it and we could vote publicly on the subject.

Problem: Not all who want to contribute and participate during a devchat are able to because of the timing of the devchat (currently 20:00 UTC).

Questions to guide our designing a solution to the stated problem:

  1. Is one Dev Chat enough or should alternative dev chats be considered to accommodate more time zones?
  2. If there is agreement that alternatives should be considered, what times/intervals are the most suitable for maximum coverage of folks from all corners of the world?
  3. Is there some process that can be implemented to improve the decision making process and therefore either take that requirement out of any proposed dev chat or, alternatively, make it easier to reach decisions in any given dev chat?

This post’s comments will remain open for two weeks to allow for comments and/or suggestions.

WordPress 4.9.9 Minor Release Roadmap

Release Schedule (Tentative) :

Beta : Monday October 22, 2018

Release Candidate : Monday October 29, 2018

Release Date : Monday November 5, 2018

Bug Scrubs:

We will be running bug scrubs across the planet for this release. We will do our best to provide coverage for every time zone, but you can expect to see one in the #core channel weekly. We will share the schedule soon.

Summary:

For the 4.9.9, we plan on working on 4 focus areas: Accessibility, Internationalization, Site Health Project, Gutenberg Preparation. Along with these concerted efforts, we want to over-communicate and make sure we get involved with all teams as much as possible.

Key Focuses:

Internationalization (i18n):

We are going to try and bring focus around internationalization. Translations, making sure date/time values work and RTL is supported. More to come as we learn more about the current backlog.

Accessibility (a11y):

We’d also want to focus on fixing issues in accessibility. There’s lots of ways we can drastically improve the experience for a lot of people with minor effort.

Site Health Project (Servehappy) :

We will investigate the work remaining for the Servehappy project and determine how to get it in people’s hands as soon as possible. WSOD protection, update dashboard notice, plugin version requirements are the hot items pending. 

Gutenberg Preparation:

We are collecting the tickets that should be processed for laying the groundwork for the upcoming Gutenberg merge. The tickets that have been proposed by the Gutenberg team so far are:

Communication :

As per usual, we will be regularly communicating details around changes made. For this release, we’d like to aim to over communicate happenings in the release. If there is a commit and you don’t mind us putting you on blast, we’re going to explore ways to publicly celebrate and tell the story of that! This goes especially if the contribution is one of your first!

We will also strive to be more present in component meetings. We will each be attending every component meeting at least once in the release cycle to check in on any things that may be needed for 4.9.9.

Dev Chat Agenda: September 12, 2018 (4.9.9 Week 5)

If prisoners could take their own mug shots, they’d be called cell-fies. 


This is the agenda for the weekly <dev chat> meeting on Wednesday, September 12, 2018 20:00 UTC in #core.

4.9.9 Planning

  • When asked if we had 4.9.9 agenda items Tuesday at 3:39 p.m. CT, @antpb said, “Working on it now!” So I figuratively  👏cannot wait 👏to see what he and @schlessera have in store.
  • UPDATE: We have topics!
    • Tentative Release Schedule
      • Beta
      • RC
      • Release Date
      • Bug Scrubs
    • 4.9.9 Engineering Focus & End Goals

Focus Lead and Component Maintainer Updates

Open Floor / General Announcements

Open Floor tickets

Pssst. You can send these my way and I’ll add them to the list.

  • #12563 New action on body open – Might need to include Theme Review team. 
  • #25280 wp_localize_script unexpectedly converts numbers to strings 
  • #43657 Custom HTML widget editor content not updating after save 
  • #16828 Add filter on initial_meta_boxes for nav menu
  • #32326: Improve Support for Structured Data

General Announcements:

  • Update on potential second <dev chat> 😱

If you have anything to propose to add to the agenda or specific information related to the above, then please leave a comment below. Either way, we look forward to seeing you at the dev chat this week!

#agenda, #4-9-9, #core, #dev-chat

Dev Chat Summary: September 05, 2018 (4.9.9 week 4)

This post summarizes the weekly dev chat meeting held Wednesday, September 05, 2018, 20:00 UTC, including topic updates from the lively August 29 dev chat. Agenda | Slack Archive

4.9.9 Updates & Planning

Release Leads

  • After a lively discussion about the ideology of the leadership structure for minor releases during the August 29 dev chat, and following through on our effort to develop a broader group of people who can lead releases, @antpb and @schlessera will serve as co-leads for 4.9.9. @sergeybiryukov will assist with commits. There were 21 emoji reactions to this message in Slack, so it’s official. No takesies backsies.
  • A tentative schedule will be announced once release leads can align schedules for the next 6-8 weeks.

4.9.9 Inclusions

@youknowriad mentioned it would be lovely for these two REST API issues to land in 4.9.9:

  • #44862: Create REST API endpoints to lock, release and takeover post edition
  • #44758: The REST API is not respecting the user’s locale properly 

If you have other issues you’d like to see in 4.9.9, come on over to next week’s chat. We’ll keep the lights on for ya.

Focus Lead & Component Maintainer Updates

Gutenberg

  • We’ve got a 3.7 release! This version includes clarifications for some core interactions, expanding the Unified Toolbar mode, squashing Gutenbugs and SO. MUCH. MORE. 
  • Please continue to provide us with feedback via testing and block usage. 
  • I personally appreciate any and all Gutenberg puns. Thanks in advance!

JavaScript

The fab JS team posted notes from their weekly chat. Thanks @matveb for posting the recap! Highlights:

  • Deprecation strategy
  • Allow building in `src`
  • Guidelines for including WP packages

General Announcements

A second dev chat? 

  • During the August 29 dev chat, we notified the channel that we had volunteers to host a second dev chat at a different time on Wednesdays. The goal of having a second dev chat is to see if expanding dev chat across another set of time zones would be more inclusive of the non-U.S. based WordPressers.
  • Following a lively discussion, those who volunteered to lead the second chat are drafting a proposal that is still a WIP. We’ll open up the discussion again during next week’s dev chat.

Merge Proposal: Dark Mode

  • @danieltj is here 100% here for our eyeballs with Dark Mode. His merge proposal answers what Dark Mode is and isn’t, especially the big question about why it isn’t a color scheme. You have to click to find out. I’m not spoiling it here.
  • Further testing and feedback is needed, so please help out if you can.

HTTPS

tl;dr – This conversation has moved over to #core-http in Slack and is being self-organized by those involved. And yes we know that channel name is not secure!

  • Chrome stepped their game up when it comes to flagging non-SSL sites, so @westonruter suggested we do the same when encouraging users to enable HTTPS whenever possible. 
  • Some additional resources on this topic:

That’s it! We’ll see you at <dev chat> next week: Wednesday, September 12 20:00 UTC in the #core Slack channel. 

#summary, #4-9-9, #core, #dev-chat

Dev Chat Agenda: September 5th (4.9.9 Week 4)

This is the agenda for the weekly devchat meeting on September 5, 2018 at 20:00 UTC:

  • 4.9.9 planning
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, then please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

#4-9-9, #agenda, #core, #dev-chat

Dev Chat Agenda: August 29, 2018 (4.9.9 Week 3)

This is the agenda for the weekly dev chat meeting on Wednesday, August 29, 2018 20:00 UTC.

  • 4.9.9 planning
    • Release leads discussion
  • Updates from focus leads and component maintainers
  • General announcements
    • Discuss second dev chat proposal (for our non-20:00 UTC friends)

If you have anything to propose, to add to the agenda, or specific items related to the above, please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

#4-9-9 #agenda #core #dev-chat

Dev Chat Agenda: August 22nd (4.9.9 Week 2)

This is the agenda for the weekly devchat meeting on August 22, 2018 at 20:00 UTC:

  • 4.9.9 planning
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, then please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

#4-9-9, #agenda, #core, #dev-chat

Dev Chat Agenda: August 15th (4.9.9 Week 1)

This is the agenda for the weekly devchat meeting on August 15, 2018 at 20:00 UTC:

  • 4.9.8 feedback
  • 4.9.9 planning
  • Updates from focus leads and component maintainers
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, then please leave a comment below. Either way, we look forward to seeing you at the devchat this week!

#4-9-8, #4-9-9, #agenda, #core, #dev-chat

Dev Chat Summary & Call for Release Lead Nominations: August 01, 2018 (4.9.8 week 5)

This post summarizes the weekly dev chat meeting held Wednesday, July 18, 2018 (agenda | Slack archive).

4.9.8 Release

4.9.9 Road Map

  • Rumors of a v. quick release (like next week) for 4.9.9 were squashed. 
  • There are currently 46 tickets assigned to this milestone.
  • See the “Call for Release Leads” section below.

Focus Lead and Component Maintainer Updates

Recap posts within a recap post. Woah.

General Announcements

Devchat Coordination Reminder

@jeffpaul returns next week, thus ending the mighty reign of temporary dev chat leads @joemcgill, @audrasjb, @antpb et moi. Please tell him how truly fantastic we were in his absence.

Next Meeting

The next meeting will take place on Wednesday, August 08, at 20:00 UTC in the #core Slack channel. Please drop in with any updates or questions. If you have items to discuss, drop a comment on next week’s agenda post, so we can take them into account. 

(You can add them as a comment here, too, but they might get lost in the flurry of release lead noms.)

Call for Release Lead Nominations

Here we go. It’s time to nominate leads for 4.9.9.

  • Post a comment on this recap to be considered. 
  • You do not have to be an engineer to be nominated.
  • Self-nominations are welcome.
  • Ready? GO!

#summary