Dev Chat: 10/23/2019

The facilitator for this week’s chat was @audrasjb.

Announcements

WordPress version 5.3-RC2 was released on Tuesday. Everyone please help by testing out the RC.

The latest Dev Note published for 5.3 discuses “Noteworthy Admin CSS Changes in WordPress 5.3”.

Also, the official Field Guide for 5.3 was published!

@audrasjb called attention to the wonderful documentation work this cycle by @justinahinon and @jeffpaul. Thank you to both for their extraordinary efforts!

5.3 Updates

@azaozz Pointed out that there are only two tickets needing work after RC2, excluding the About Page. Follow the ticket progress in Trac here.

@ianbelanger informed the group that there are currently 0 tickets in the Bundled Themes component for Twenty Twenty. However, he added that an RC3 release would be helpful.

@audrasjb brought up ticket #48396 regarding @afercia‘s request to revert two lines of CSS to remove an unwanted changes on disabled buttons. @azaozz confirmed the revert to be a minor one and suggested that it move forward based on testing.

A pre-RC3 Bug Scrub in the #core channel was tentatively scheduled for Monday October 28, 2019 15:00 UTC. If there are no new tickets or regressions reported prior, the scrub will not take place.

@sergeybiryukov asked about branching for 5.3 this week. @peterwilsoncc suggested certainly branching before WordCamp US Contributor Day, as to allow for good-first-tickets to be committed for new contributors. @desrosj added that branching could be done at any time now that the dust has settled from RC2, but deferred to @azaozz‘s judgement as Core Tech Lead for 5.3. @azaozz suggested trying to resolve a couple of remaining issues in 5.3 prior to branching in the next few days, and a consensus was reached around this idea.

These notes were taking by @davidbaumwald and proofread by @audrasjb

#5-3, #dev-chat, #summary

Dev Chat Agenda for October 16 2019 (5.3 week 9)

Here is the agenda for the weekly meeting happening later today: Wednesday, October 16, 2019, 20:00 PM UTC. Please share any items you’d like to include in the comments below!

  • Announcements and highlighted posts
  • Upcoming Release Discussions
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-3, #agenda, #dev-chat

Dev Chat: 10/9/2019

@davidbaumwald served as facilitator and note taker for this week’s chat held in the #core Slack channel. To view the chat from the beginning, click on this Slack Archive.

Announcements

WordPress version 5.3 Beta 3 was released on Tuesday. Congratulations to everyone involved in inching 5.3 closer to the finish line.

5.3 Updates

With 5.3 Beta 3 now release, focus turns to Release Candidate 1(RC1) is next on the schedule just a few days from now. A “soft string freeze” is now in effect.

@francina called for volunteers for next week’s RC1 release session. Both Mission Control(MC) and a Core Committer will be required. @azaozz and @sergeybiryukov raised their hands.

@karmatosed provided a quick update on 5.3’s About page, saying that everything is on track and copy is being finalized.

@jeffpaul inquired about the progress on compilation of Dev Notes for 5.3. @justinahinon pointed to a Google Sheet that he’s using to organize them and coordinate volunteer authors.

This discussion led to a call for more volunteers and ticket owners to draft Dev Notes. @desrosj mentioned that he’s “… started a page for the handbook collecting the learnings from the last three releases for this.”

@ianbelanger brought a Twenty Twenty update to the group. A PR has been opened to address WPCS violations in the Beta Twenty Twenty patch, and a call for testing was announced. @karmatosed added that testing on mobile is a great help to the team.

Open Floor

@azaozz mentioned that there are, as of writing, only 37 open tickets in the 5.3 milestone, and everything should be closed out as RC1 is released. This was a great reminder of the tremendous work done by Core Contributors during the course of the 5.3 cycle, as over 350 tickets were initially open when the cycle was kicked off!

These notes were drafted by @davidbaumwald and proofread by @justinahinon.

#5-3, #dev-chat, #summary

Dev Chat Agenda for October 9 2019 (5.3 week 8)

Here is the agenda for the weekly meeting happening later today: Wednesday, October 9, 2019, 20:00 PM UTC. Please share any items you’d like to include in the comments below!

  • Announcements and highlighted posts
  • Upcoming Release Discussions
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-3, #agenda, #dev-chat

Dev Chat summary: October 2

The 5.3 Release Coordinator, @francina, led the chat (full transcript). For the record, here was the agenda for the meeting.

Announcements and highlighted posts

@francina made some announcements and pointed out highlighted posts from Make/Core blog:

Feel free to browse through these posts and add comments or thoughts.

@youknowriad mentioned Gutenberg 6.6 recap post. This version focused on stability for the editor and performance for WordPress.

Upcoming Releases

Gutenberg team lead @youknowriad said they welcome any testing to detect bugs and regressions before 5.3 release. You can see what’s happening with the editor on this GitHub board.

Site Health component maintainer @clorith reported that desired changes are on track and should be ready for the Release Candidate, currently scheduled for October 15.

Docs coordinator @justinahinon said 5.3 dev notes include some for major changes/enhancements, plus many others. Check out all the dev notes here.

@earnjam reminded the group that each published dev note on Make/Core sends an email to ~4000 newsletter subscribers. He suggested authors limit each dev note to a single topic so people can find things in the index.

@francina shared WordPress 5.3: Accessibility focus progress report.

WordPress project Executive Director @chanthaboune brought up changes that are coming to the admin interface. She stated that the focus leads have been discussing whether to keep the changes or allow extra exploration time for them, as suggested in this post.

Here are the key stances she noted from the various discussions so far:

  • There are some concerns about how quickly the changes were decided on and then implemented from design.
  • There are some concerns raised about the process overall, and whether there’s enough time for testing. Josepha and a few core committers share this concern.
  • There are concerns that further delays will result in loss of momentum from accessibility as well as confidence in an iterative process.

Josepha said she’s doing her best to balance progress with caution, and that she has gotten a lot of feedback from the release focus leads.

Here are the different opinions that have been shared by people regarding this:

  • @garrett-eclipse said that when the changes landed in trunk with several bugs popping up all over, he was leaning towards the pull, but now that the team seems to have addressed and crushed the majority of them, he’s more in favor in keeping the changes.
  • @clorith reminded that while they are worth doing, he agrees on the fact that the changes may have come a bit late in the cycle with limited time for testing and exposure.
  • @mapk asked if the a11y improvements at the cost of design worth immediate and rapid merging, or if we can take the time we need to fully test and address issues?
  • @samuelsidler asked about the items of concerns/tasks that can not or will not be fixed before 5.3 Release Candidate.
  • @melchoyce answered @samuelsidler about tasks that can’t/won’t be fixed before 5.3 RC:
    • Wider design changes to account for the shift in the hierarchy; because the new form fields are so much darker than the list tables, any page where both exist is thrown off a little.
  • @mapk answered @samuelsidler saying that he believes there are other design explorations to address and a committed testing cycle for a large release.
  • @karmatosed shared some worries she has about this:
    • Documentation: those that write tutorials and might find their screenshots out of date.
    • Testing: A longer testing phase for her would be better just like during mp6 project. She thinks that 5.4 should be a focused release, with testing, time and iteration feel safer.
  • @joemcgill said that since he has not been part of the discussions, he would be more concerned by process problems keeping a11y improvements from shipping rather than shipping changes that improve a11y and then iterating on the design.
  • @afercia clarified that most of the design changes come from design and were implemented on top of the a11y improvements. He also mentioned that from an a11y perspective all the matters are:
    • Removing the fixed heights from the input fields etc.
    • Improving contrast
  • He also said that all the other changes are unrelated to a11y and came from design feedback.
  • @samuelsidler asked @melchoyce if there is a plan in place to fix/iterate on those visual issues for the future? If yes, when in the future? He also asked if those improvements happen in 5.3.x or they would need to be in 5.4 or later?
  • @melchoyce replied to @samuelsidler and said that he thinks they would be wide-reaching enough that the design team would need to ship them in 5.4.
  • @earnjam expressed that he would personally lean toward a more cautious approach and allowing further iterating as a feature plugin with an earlier merge in a release cycle to allow more time to catch/fix the bugs. He also feels like we’re trading one set of bugs/issues for a different set and doing it during the beta period.

This discussion has continued with different arguments from design and a11y team members and with other contributors as well. You can read the discussion in its entirety here.

Calls for components maintainers have been skipped for this chat.

Open Floor

@azaozz noted that he’s started to get concerned by the 100+ tickets that are still open for 5.3. He invited maintainers and committers to review and comment on tickets that must be in the release and move the rest to the Future Release milestone.

@afercia said that while the a11y team is committing a lot of things, they will need urgent feedback on #47069 and #43037. @ryokuhi gave a brief explanation about the last ticket.

@davidbaumwald said he’s planning a last-minute scrub due to the high number of tickets that are remaining for 5.3. The schedule for 5.3 scrubs can be found here. Again, everyone is welcomed to attend scrubs and also to organize them.

@justinahinon shared a “Special interest” he has about developer documentation, dev-notes, and WordPress codebase. You can read about it on the chat agenda comments.

@davidbaumwald reminded that they will be doing a lot of punting at the end of the week, so two things:

  • If you have a ticket you absolutely want in 5.3, get moving.
  • If not, at least leave a comment on feasibility for 5.4, or he’ll be moving everything to Future Release if they haven’t seen any movement in a while.

@desrosj clarified that the tickets owned by committers and maintainers have largely been left in the 5.3 milestone to allow those owners to make the decisions they feel are appropriate. If those tickets are not gardened in the next few days they will be punted.

Finally, @azaozz added that the best would be the component maintainers to decide what is good to be in 5.3 and what is going to be in 5.4 of future releases.

That’s the end for this long, lively and important devchat.


#5-3, #dev-chat, #summary

Dev Chat Agenda for October 2nd 2019 (5.3 week 7)

Here is the agenda for the weekly meeting happening later today: Wednesday, October 2, 2019, 20:00 PM UTC. Please share any items you’d like to include in the comments below!

  • Announcements and highlighted posts
  • Upcoming Release Discussions
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-3, #agenda, #dev-chat

Dev Chat Agenda for September 25th 2019 (5.3 week 6)

Here is the agenda for the weekly meeting happening later today: Wednesday, September 26, 2019, 11:00 PM GMT+3. Please share any items you’d like to include in the comments below!

  • Announcements and highlighted posts
  • Upcoming Release Discussions
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-3, #agenda, #dev-chat

Dev Chat Agenda for September 4th 2019 (5.3 week 3)

Here is the agenda for the weekly meeting happening later today: Wednesday 4 September 2019 at 20:00 UTC. Please share any items you’d like to include in the comments below!

  • Announcements and highlighted posts
  • Upcoming Release Discussions
    • 5.2.3 Updates
    • 5.3 Updates
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-3, #5-2-3, #agenda, #dev-chat

Dev Chat Summary: July 31

This post summarizes the weekly devchat meeting from July 31st, 2019 ( Slack Archive).

Announcements

@chanthaboune reported that she was recently told what a patient and welcoming group Core is. Kudos to all for being so welcoming!

The following announcements were posted requesting feedback in the last week:

Also, PHP 7.4 has hit the beta stages and is target for public release in late November.

@kadamwhite asked what the most productive way to express support for the proposed plan to raise the minimum PHP version. The fear expressed was that +1 comments would be unproductive noise. @miss_jwo confirmed she was OK with +1 comments.

Upcoming Releases

5.3 Update

@chanthaboune has a few updates that she still needs to post.

However, after reaching out to a few people (and being proactively reached out to by several others), the picture being painted indicates an early November release is feasible. This would mean a post WordCamp US (November 1-3) but pre US Thanksgiving (November 28) timeframe.

Some attendees expressed hesitation to committing to a release date too soon after WCUS. But there seemed to be a sentiment that with enough advance notice and an early enough release candidate (early October at the latest), a date within this general timeline could work. There is currently no new default theme planned for 5.3.

5.2.3

A few people thought that 5.2.3 could still be warranted between now and November. #47797 was raised as a possible ticket (and anything else needed to prepare for a PHP version bump in 5.3) for inclusion in 5.2.3.

Component Maintainers:

The following upcoming meetings were called out by component maintainers in attendance:

  • Media – Thursday, August 1, 2019 @ 13:00UTC
  • REST API – Thursday, August 1, 2019 @ 1800 UTC

@jorbin also called out that now is a great time to make the push for PHP 7.4 compatibility. Getting the 7.4 job to pass in Travis is a good first step.

#dev-chat, #summary #5-3

Dev chat summary: July 17

@earnjam led the meeting. @marybaum took notes and is writing this summary.

Announcements

Gutenberg 6.1

@earnjam announced the release of Gutenberg 6.1 last week. New features include animations/motion to block reordering, improved messaging for REST API errors and more.

Check out the release post for more details: https://make.wordpress.org/core/2019/07/10/whats-new-in-gutenberg-10-july/

Look for version 6.2 RC to land next week.

PHP Coding Standards

@pento posted a followup to some proposed coding standards changes from a few months back.
See the decisions on these changes here (they might surprise you!): https://make.wordpress.org/core/2019/07/12/php-coding-standards-changes/

And keep in mind these affect only the code for WordPress Core. In your own Themes and Plugins, use the coding conventions that make sense for you.

Releases

5.2.3

With four tickets in the queue and none of them affecting functionality, it’s still not clear that they warrant a separate 5.2.3 release. Scheduling for that is still pending further info on a roadmap for 5.3, which should land in early fall.

5.3

As yet the Core team is progressing on current open tickets — there are 57 in the queue — while @chanthaboune continues gathering data from component maintainers on feature priorities for 5.3.

Component maintainer updates

Core-media

@azaozz asked for more eyes on #40439.

If you can help test, please check out the ticket or head to #core-media.

Site-health

@clorith pointed to the call for input for bumping the PHP recommendation and said that soon a Make blogpost will outline next steps—and next versions.

For now, the site-health team isn’t looking to raise the hard minimum. This will be a soft bump up to nudge users toward the minimums that will follow.

Open Floor

Triage Team

@joyously asked about progress from the Triage Team, and the responses came from several quarters.

@desrosj posted a link to his three-month summary: https://jonathandesrosiers.com/2019/06/wordpress-triage-team-3-month-reflection/ and plans to post more often on https://make.wordpress.org/updates.

@karmatosed mentioned that Design holds two triages a week, and that from where she sits, triage seems to be going gangbusters and spreading across the WordPress Project.

@azaozz pointed the group to his efforts on TinyMCE: https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&component=TinyMCE&order=priority

@marybaum mentioned having been in an accessibility triage last Friday.

Gutenberg Phase 2

Newcomer @Lu asked about the timing of Gutenberg Phase 2, with a particular interest in widget blocks. @earnjam answered with a summary of the release discussion earlier in the chat.

Strings

@marybaum asked the group for their thoughts on a more systematic, global approach to the copy in strings.

For now, the group agreed to have #meta add two keywords to tickets—needs-copy-review and has-copy-review.

Props to @garrett-eclipse, who opened meta#4609 and its counterpart meta#4610 on the spot.

Right at the close of the official chat, @audrasjb linked to https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/#style-and-substance

#dev-chat, #gutenberg, #releases, #strings, #triage-team

#summary