Devchat notes – 3 February 2021

Agenda for the two meetings. Thanks to @thewebprincess and @hellofromtonya for leading the 05:00 and 20:00 UTC devchats respectively.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements and news

WordPress 5.7 Beta 1 is out and available for testing.

WordPress 5.6.1 landed after devchat.

Month in WordPress for January 2021 (published 3 February 2021)

Reminder from Marketing, @webcommsat: we start our marketing planning well in advance, so if you are working on something for later in the year or that could be in the Questions and Answers on 5.7 or 5.6.1, please let @webcommsat, @yvettesonneveld, and @meher know. 

Week in Core – edition 1 February 2021

What’s next in Gutenberg?

Full Site Editing (FSE)

Component maintainers and committers update

Post from @chanthaboune on encouraging and recognizing committers and maintainers following on from discussions – Committers, Maintainers and Emeriti. This will also help show which areas need support in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

  • Discussion during the meeting:
    • making it easier for people to see how they can become committers
    • using official emeritus status outside core for particular roles
  • Specific comments:
    • @hellofromtonya: Any concerns with deactivating their commit status with a path to reactivate when/if they become active again? No one in the meeting raised any concerns on this.
    • @sergey: A place to mentor potential new committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component..
    • @webcommsat: This would help so much with the recruitment and longer term contribution of committers too.
    • @nalininonstopnewsuk: Suggested more promotion on what skills and computer facilities potential committers would need. Supports the emeritus idea.
  • @annezazu and @hellofromtonya are interested in discussing a mentorship program.

Updates from component maintainers


Build/Test Tools: The Sass implementation that Grunt uses has switched from node-sass to Dart Sass. That’s because LibSass and node-sass have been deprecated. Ticketticket Created for both bug reports and feature development on the bug tracker. #51763 for more details.

  • General: The get_home_url() function now consistently returns an httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. URLURL A specific web address of a website or web page on the Internet, such as a website’s URL if the current request is already https, both for the adminadmin (and super admin) and front end. This fixes a previous inconsistency between the admin and front end URLs. See ticket #52421 for more details.
  • Date/Time, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks: No major news this week 


Upgrade/Install, Menus & Widgets: no major new this week, except that all our enhancements and features were finally committed before 5.7 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1.


  • 5.7 Beta 1 is out in the wild and ready for you to test and give feedback
  • It includes 143 tickets with 68 new features and enhancements 
  • Now the focus shifts to defects as well as supporting your feedback on the beta releases
  • There are currently 118 tickets open in 5.7 [ listing ]. Please help get as many as we can into the release during the beta cycle.

Update on WordPress 5.6.1 from @audrasjb:

Update and discussion on 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 Plugin Directory or can be cost-based plugin from a third-party/Theme Rollback

  • GitHub details on the plugin/ theme rollback update
  • @hellofromtonya: We had planned to include plugin/theme rollback in WordPress 5.7, but it will become a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. first. @afragen is doing the building, and it’s almost ready to submit to 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.
  • @ipstenu will flag it as an official beta for review
  • @davidbaumwald: is that plugin slated to roll over to the WordPress GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. account, or is it a gap-filler that doesn’t require that? @afragen: not sure it needs lots more actual work. But whatever the usual process is will be fine.
  • @hellofromtonya: currently, it’s set for feedback to validate if there are performance issues that could cause additional update failures.
  • Question: should it remain as a separate plugin repo (not on the WordPress GitHub) until we know more? Thoughts invited. @afragen: It will also be very difficult to evaluate that, but I’m open to saying if there’s a server timeout it could be related.
    • some support for moving it to WordPress GitHub account
    • @davidb suggested gaining more visibility would help and following view of the maintainers. Agreement from the meeting of the benefits of extra visibility. @audrasjb shared how promoting visibility had helped a lot for plugins and themes auto-updates, and he will share what was done for that feature plugin
    • @hellofromtonya: Getting more on it will also help us to further improve plugin and theme updates. Hoping to collect more information on the root causes for update failures
    • @sergeybiryukov: My concern is that the plugin in its current state doesn’t seem to follow the direction outlined in comment 56 on the ticket. More discussion planned for the next #core-auto-updates meeting.
    • #51857: Add rollback for failed plugin/theme updates – I don’t think that comment was as much about rollback as making the update process more robust. I think that was suggested as an alternative to rollback that would have fewer performance concerns. We could probably have both.
    • @hellofromtonya: improving the update process itself is important! If we get robust enough, it negates the need to rollback when a failure happens. That assumes though that failures will never happen, which not sure if that’s a reasonable assumption.

Next steps:

Open Floor

Who is moderating feedback on the Code Reference? @audrasjb once a week and @crstauf more regularly. This is part of the Docs Team’s work.

#5-6-1, #5-7, #dev-chat, #fse, #plugin-theme-rollback

Devchat meeting summary – May 20, 2020

@francina facilitated the chat on this agenda.
Meeting recap by @audrasjb and @marybaum.

Full meeting transcript on Slack


Just a few hours before the chat, the hardworking team behind the plugins and themes auto-updates feature committed it to Core! Congrats to all!

Check out this related ticketticket Created for both bug reports and feature development on the bug tracker. that adds Help Tabs text to update-core, themes and plugins WP-Adminadmin (and super admin) screens: #50215

If you’d like to be part of the Full Site Editing outreach experiment, the sign-up deadline is now May 22. @chanthaboune noted that’s just to show interest, not a commitment yet.

Highlighted posts

Upcoming releases

WordPress 5.5

The next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of WordPress is in active development (Alpha cycle).

@francina noted the team is not quite complete, but it’s confirmed that @matt will return as release leadRelease Lead The community member ultimately responsible for the Release.@davidbaumwald as co-lead in the role of Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM and @sergeybiryukov as Core tech lead. The 5.5 team will also mentor the 5.6 team.

WordPress 5.4.2

@audrasjb shared that there are 20 tickets in the milestone. Of those, 17 are closed as fixed.

@whyisjake leads this point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality., and the group firmed plans for a release candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). on June 3 and a final release June 10.

Components check-in and status updates

@whyisjake was exuberant that the core team was able to merge the auto-updates code today. This is going to do a great deal to help people stay on top of updates for a safer WordPress ecosystem.

The merge is just the latest significant step toward the master plan for 2020. Lazy-loading of images merged a few weeks ago, and XML sitemaps is making great progress as well.

On the 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). ( side, @audrasjb shared that most of the accessibility team’s main projects for 5.5 are moving forward. Alternate views for posts, users, and comments lists should be ready for review soon.

@johnbillion wanted to note that weekly meetings for Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site have restarted, on Tuesdays at 17:00 UTC in #core-multisite. Come join them!

In Site Health, @clorith pointed out that the Theme Review Team has implemented requirements for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher headers in themes. That move should push users in the right direction for updates.

As well, the Site Health component team has had discussions with hosting about bumping the version for Servehappy dashboard nags.

Open floor

@dlh wanted to highlight #48416. He recently encountered a use for it again. If you’re interested in the taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. component, please give it a look.

@sippis reminded everyone to register for WCEU 2020 Online 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 There are many teams that people can participate in, each with a different focus., which is Thursday, June 4, 2020 at 13:00 UTC. If you don’t register, you won’t get the emails you’ll need in advance, so don’t forget to register.

#5-4-2, #5-5, #dev-chat, #feature-autoupdates, #fse, #summary, #wceu, #wceu-2020

An Experimental Outreach Project for Full Site Editing

Update: following some discussion about themes as they relate to full site editing, I’ve extended the deadline for expressing interest in this program for an additional week, closing on 22 May, 2020. – Josepha

As we approach the second release of 2020 with an eye toward WordPress 5.6, I’ve got full site editing (FSE) on my mind. During the WordPress 5.0 retrospective, one of the things that came up routinely was the need for better engagement with users*. It was generally agreed (from all levels and areas of contribution) that users* will be most impacted by GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc., but that users* are also the group we have the least channels of communication to.

To help get user feedback to WordPress developers a little more seamlessly, I am going to try an experimental outreach project. With FSE set to launch by the end of the year, this experiment aims to get feedback about pain points to the right people faster and help keep us on track for Phase 2.

If you are interested in testing early versions of upcoming releases that will make FSE work better for you, your customers, or anyone who is building or maintaining a WordPress site, please fill out this interest form between now and May 14th. By filling out the interest form below, you’ll get more information about the program when it launches: 

Sign me up for more information!

I’m still working on the finer points of this experiment, but the intention is to use Gutenberg in as close to a client setting as possible. Time to provide feedback is flexible but could be up to 3 hours a week on average. Thanks in advance if you’re able to help us shape this work!

The interest form will be open until May 14th, 2020!

#testing #FSE

*Users can be defined in many ways, but in this case, I’m referring to those who build with WordPress (not those who build WordPress) and those who maintain WordPress sites (not those who visit sites).