DevChat Notes – June 16, 2021

Thanks to @peterwilsoncc and @jeffpaul for leading the 05:00 and 20:00 UTC dev chats respectively.
Agenda followed for both the meetings.

Link to 05:00 UTC devchat meeting archive in Slack // Link to 20:00 UTC devchat meeting archive in Slack

Thanks to @nalininonstopnewsuk and @webcommsat for the dev chat notes. 

Blogblog (versus network, site) post highlights

Thanks to all everyone who published items and helping document and share knowledge across the project.

Blog posts that need attention

  • 5.8 Beta 2 Post – Testing required for 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. to help ensure as smooth a release as possible. Thanks to all those involved in testing, contributing to Beta 2 and the post.

Beta and bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs

We are now in the Beta period where focus shifts to tasks and regressions found in Beta releases.

Bug scrub schedule for 5.8

Next milestone: Beta 3 on Tuesday 22 June 2021.

Final Beta release before 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). 1 on Tuesday 29 June 2021.

Contributors needed/ attention:

  • Theme contributors to test the new blocks in the default themes. Contact @jeffpaul or @desrosj

More information from the Slack discussion 

  • Open Trac Tickets that need various forms of assistance (patches, testing, etc). Josepha called especially all sponsored contributors to help get over the finish line.
  • Contributors skilled on WP-CLI needed for Meta Ticket 5737 – block.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. strings not being extracted  
  • Feedback on:
    • Core Trac Ticket #53428 part of the work to style new coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks for the default themes, and related 
    • Core Trac Ticket #53389  Bundled Themes: Add styling for blocks added in 5.8, and 
    • Core Trac Ticket #53398 Twenty Twenty-One: Polish new blocks added in 5.8

Updates related to 5.8

  • About Page and MarComms
    • A timeline for the About Page has been set so that the copy can be ready for Beta 3. Two days set aside for fact-checking. Deadline for final copy and design is RC1. Marketing post on plans for discussion on the text.
    • Design to date on the About Page ticket
    • Josepha: From that content we will also build some of the other marketing pieces including the release post. If you want to give it an early, pre-editing read there are links in #marketing. This will be more than content on the About Page. 
    • Thank you to everyone who contributed to the marketing collaborations and to @chantabourne, @marybaum and @webcommsat for organizing, supporting contributors, and giving time. You can still add to the text discussions on content for multi-purpose use – details in the #Marketing channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Josepha has extended the collaboration for 15-16 hours to give extra time.
    • Josepha shared there would be additional broader marketing aspects when new role (advertised in February) joins
    • @mkaz: WordPress News has been publishing articles and podcasts highlighting many of the upcoming changes too.
    • @clorith: highlighted @desrosj has started identifying things and making individual items for them, which he suggested would be the right way forward. Highlighted the need more clarity on what is an isn’t included in 5.8, and some sanity checks on some of the defaults going in
    • @oglekler: Core Trac Ticket #52762: Suggestion for an About Page widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. to dashboard  
  • @youknowriad: follow-ups highlighted
    • Make sure default themes are adapted properly for the default template
    • Request for help from themers (test and adapt the theme styles as needed) 
    • TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. a bug related to media uploads
    • Provide a way to define a different default template per theme

Component maintainers updates

  • @sergey: build / test tools, date/ time, general, Ii8N, Permalinks: no major news this week
  • @audrasjb: no major news from upgrade/ install, menus, widgets
  • @clorith and @afragen: Site Health’s got nothing big this week

Open floor

@mkaz: we’ve started publishing dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. around the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor. More to come during the next few weeks.

@chanthaboune: request for “some general signal boosting on what FSE in and isn’t in WordPress 5.8. There’s a lot of confusion, but also a lot of documentation (both existing and to come) so we can use some help spreading that around.”

@chanthaboune: “I wanted to underline how much I appreciate the thoughtfulness and care that has gone into this release. I know you have plenty of options about where you can spend your time, and this release is going to be a great building block for full site editing. Big thank you to everyone working on this as we head into our final weeks of this marathon!”

#5-8, #dev-chat

Dev Chat Agenda for June 16, 2021

Here is the agenda for this week’s developer meetings to occur at the following times: June 16, 2021 at 5:00 UTC and June 16, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Schedule Review

  • 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. 2 released yesterday, final Beta release in 6 days on Tuesday, June 22nd
  • Focus now fully on tasks in the milestone and regressions found in Beta releases
  • Next Beta Scrub before Beta 3 is Monday, June 21st 20:00 UTC
  • RC 1 in 13 days on Tuesday, June 29th
  • 5.8 release in 34 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

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

#5-8, #agenda, #dev-chat

Dev Chat Summary: June 09, 2021

@peterwilsoncc and @desrosj led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC. Here is the meeting agenda.

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

Blogblog (versus network, site) Post Highlights

@audrasjb shared the weekly recap of code changes and contributors in the latest issue of A Week In Core: 07 June 2021. Thanks to the 72 (!) people who contributed, the 12 (!!) new contributors, and the 11 💖 core committers who helped land these changes last week.

@annezazu shared Editor team updates on Full Site Editing, Navigation BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., Mobile Editor, and Block Based Widgets Editor from their last meeting: Editor Chat Summary: 02 June 2021.

@danfarrow shared CSSCSS Cascading Style Sheets. team updates on Color Scheming, CSS Audit, and CSS Deprecation Path, but click through to the meeting notes for a CSS Trick that you won’t believe! For more information, see CSS chat summary: 03 June 2021.

@priethor shared details on what’s coming up in Gutenberg including final polishes for WordPress 5.8, Widgets Editor, Navigation Editor, Full Site Editing various milestones.

Kudos to @adamsilverstein for publishing the first dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. of the release covering the addition of WebP support. Click through to learn how WebP helps you, how to create and use WebP images, plans for the future, and some FAQ items.

@chanthaboune announced a new Make/Project site for all-project communications and cross-team collaboration, so drop your email in that subscribe form and stay up-to-date on all the important topics across the WordPress project.

@jorbin shared the dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. on Bootstrap/Load Changes in 5.8.

@chanthaboune also shared initial designs on a forthcoming News blog design update, its so lovely go check it out.

Blog posts that need feedback

@annezazu has a reminder for us that the current FSE call for testing has one week left until June 16th, so please try crafting a Polished Portfolio.

WordPress 5.8 update

A ‘Big Thank You’ to everyone that helped get everything in order so that 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 could be packaged on time this week! The 5.8 Beta 1 post does not itself need feedback so much as testing from anyone and everyone able to in order to help ensure as smooth a release as possible next month.

Please check the post for details on highlights from the release and links to get you on your way to testing. As it’s still in development, it’s not recommended to run on a production siteProduction Site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing. but testing on development and staging servers would be most helpful. The simplest way of testing is to use the beta tester plugin. In terms of ongoing development, WordPress 5.8 now focuses on tasks in the milestone and on regressions (bugs) found during the beta testing cycle.

Our next milestone will be Beta 2 in SIX days on this coming Tuesday, June 15th.

@chaion07 led the final bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs this past week. The next bug scrub is due to be run on Monday, June 14, 2021, 20:00 UTC.

Components check-in and status updates

  • Plugins: The Requires PHP and Requires at least 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 headers could previously be specified either in the plugin’s main PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher file or in readme.txt as a fallback. This has now changed for WordPress 5.8, only placing them in the plugin’s main PHP file will be supported from now on. Same goes for themes, the Requires PHP and Requires at least headers should be placed in the theme’s style.css file instead of readme.txt. The reason for this change is that any data in readme.txt is meant for the Plugin or Theme Directory only, and not for WordPress core. Core should retrieve all the necessary data from the plugin’s main PHP file or the theme’s style.css file instead. See changeset [51092] and ticketticket Created for both bug reports and feature development on the bug tracker. #48520 for more details. Thanks @afragen for working on this!
  • Help/About: Work will begin this week on the 5.8 About page. Join in on the discussion over on #52775.
  • All other components: No major updates to report.

Open Floor

@webcommsat pointed out on the video content in Matt’s talk at WCEU which would be valuable to re-highlight when those features land too. Additoionally, Abha thanked everyone for the Contribute to WP resources, workshops and discussion areas at WCEU. The content will continue to be available on the site and we are adding new resources submitted. It will help bridge and encourage people to discover Make WordPress materials and the Learn Project.

Props @desrosj for peer review prior to publishing.

#5-8, #dev-chat, #summary

Dev Chat Agenda for June 9, 2021

Here is the agenda for this week’s developer meetings to occur at the following times: June 9, 2021 at 5:00 UTC and June 9, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Schedule Review

  • 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 released yesterday, so now in Beta window with Beta 2 in 6 days on Tuesday, June 15th
  • Focus now fully on tasks in the milestone and regressions found in Beta releases
  • Next Beta Scrub before Beta 2 is Monday, June 14th 20:00 UTC
  • RC 1 in 20 days on Tuesday, June 29th
  • 5.8 release in 41 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

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

#5-8, #agenda, #dev-chat

DevChat meeting Summary – June 2, 2021

@peterwilsoncc and @jeffpaul led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC. Here is the meeting agenda.

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

Blogblog (versus network, site) post hightlights

In the last “Week in Core” issue, @audrasjb featured 98 contributors, 13 new contributors to WordPress source code and 12 core committers.

@priethor shared details on Gutenberg 10.7 including new features like the persistent List View in the Post Editor, responsive navigation menus, many design tools for blocks, and enhancements to the top toolbar, as well as iterative performance improvements and a lot of bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes.

@danfarrow shared CSSCSS Cascading Style Sheets. team updates on color scheming, CSS audit, and CSS deprecation path from their last two meetings. For more information, see CSS chat summaries for May 20th and May 27th.

Blog posts that need feedback

@annezazu extended the FSE Program Testing Call #7 from June 9th to June 16th, so please check the post to learn about the feature overview, how to set up your testing environment, and the desired testing flow to help out on this.

@webcommsat has a related ask ahead of Friday’s deadline for suggestions of external channels for the promotion/info share on FSE to various audiences. Everyone is welcome to review and add suggestions in the comments.

@meaghanthompson shared a call for testing the WordPress iOS 17.5 beta, so please check the post to learn about what’s new in the release, what’s most in need of testing, how to set up the test app, and how to report issues you find.

WordPress 5.8 update

@jeffpaul shared a 5.8 schedule reminder: we are now in the Feature Freeze period where focus shifts away from enhancements and feature requests to defects and tasks.

@chaion07 and @francina led different bug scrubs this past week. There’s a final bug scrub on Monday, June 7th at 20:00 UTC to work to clear the milestone before the 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 release the next day. Here is the full bug scrubs schedule.

The next milestone will be Beta 1 on Tuesday June 8, 2021 after which point the focus will shift to testing and fixing bugs discovered during the 3 weeks beta period.

There are two “big” remaining tasks and a call for help from @youknowriad:

  • The Query blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. where the 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. https://wordpress.org/gutenberg/ team had some feedback about it being too powerful (need to find better heuristics to disable editing there). Feel free to contribute to the discussion. There is also a subset of this issue.
  • A proposal to change in how edited block templates are linked to themes (using theme mod instead of taxonomies). The Gutenberg team would appreciate some thoughts here from Core folks familiar with these APIs (theme mods, performance, database).

Also, these are the dev notes that need to be written for the editor.

@youknowriad shared that he consider that the Core team is ready for Beta 1, ideally, we’d have some improvements for the Query block by then but not sure if it’s necessary for beta 1.

WP 5.8 Docs focus update

@milana_cap shared that out of 165 tickets, 35 (Gutenberg excluded) are marked for some sort of documentation:

  • 28 for dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.
  • 5 for updating DevHub
  • 12 for updating HelpHub

Gutenberg will have:

  • 10 dev notes (as per the list shared by @youknowriad)
  • 12 updates for dev docs
  • many updates for end user docs

Everything except block editor end user updates can be found in this spreadsheet. Block editor end user updates can be found in this Drive folder.

Docs needs the most help with end user documentation. For block editor in particular. Some changes from 5.6 and 5.7 are still not published and we had a significant drop in number of contributors due to pandemic situation. Anyone interested in getting involved please pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @milana_cap (zzap on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.). 

Components check-in and status updates

Build/Test Tools, 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 (@sergeybiryukov): No major news this week.

Upgrade/Install (@audrasjb): @francina hosted the weekly meeting and posted the meeting notes.

Menus, Widgets (@audrasjb): no major news this week.

Open floor

@poena has a request on the agenda post for anyone with knowledge on adminadmin (and super admin) pointers:

Theme Check is a 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 used to analyze themes submitted to the theme directory. I’m looking for someone who knows about admin pointers and if this issue from 2016 is still valid. Does the core team want themes with wp_enqueue_script( ‘wp-pointer’ ); or wp_enqueue_style( ‘wp-pointer’ ); to be blocked from the theme directory? The theme would not be able to be uploaded.

If you’re experienced with admin pointers, please respond to the comment on the agenda post or respond in the linked 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. https://github.com/ issue above.

@webcommsat pointed out that WordCamp Europe is Monday to Wednesday next week!

#5-8, #dev-chat, #summary

Dev Chat Agenda for June 2, 2021

Here is the agenda for this week’s developer meetings to occur at the following times: June 2, 2021 at 5:00 UTC and June 2, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Schedule Review

  • Now in Feature Freeze leading up to 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 in 6 days on Tuesday, June 8th
  • Focus now fully on defects and tasks in the milestone
  • Final Bug Scrub before Beta 1 next week on Monday, June 7th 20:00 UTC
  • RC 1 in 27 days on Tuesday, June 29th
  • 5.8 release in 48 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

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

#5-8, #agenda, #dev-chat

Dev chat summary for May 26, 2021

Happy birthday, WordPress!

Our favorite software is 18 years old today.

And now, devchat.

@peterwilsoncc led the 05:00 devchat, and @jeffpaul led the 20:00 chat. Both used this agenda.

Highlighted blogblog (versus network, site) posts

@audrasjb posted the latest Week In Code, highlighting the work of 120 contributors—11 new folx!—and 11 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committers who landed those changes.

@annezazu published Contextual Patterns for Easier Creation. That’s the idea that the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor should surface patterns based on the block you’re working on right now, to keep you in your flow and make your life easier.

Anne also published the latest FSE Program call for testing. It’s called “Polished Portfolios”, and your feedback is due June 9.

@danfarrow shared a CSSCSS Cascading Style Sheets. Chat summary that featured updates on the color scheming, CSS deprecation and CSS audit projects.

Finally, @paaljoachim and @andraganescu shared Editor chat summaries that highlight monthly priorities on Global Styles, Block-based WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor, Navigation Block, Full Site Editing, Mobile, and the Refactored gallery block.

Please note:  *Navigation Block, Post Author Block, and refactored Gallery Block did NOT make it into WordPress 5.8 before the Feature Freeze*.

Details are here: https://make.wordpress.org/core/2021/05/25/editor-chat-summary-19-may-2021/ && https://make.wordpress.org/core/2021/05/26/core-editor-meeting-notes-26-may-2021/.

After this extensive list, @chanthaboune commented, “Gosh, but we are prolific writers here …” and added, “… I love it”.

The group reacted with a flurry of positive emojis.

Posts that need feedback

Are you a host? @javiercasares and the Hosting team recommend you offer the `PHP-intl` extension by default to all of your users.

The Tide team would like some help testing their refactor to Node.js on a local installLocal Install A local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer.. Specifically, where do their docs seem unclear? Where are they confusing? Please offer your help in their chat summary.

@chanthaboune shares that she’s ready to experiment with a public channel for Team Reps across the project to collaborate in public. She’d like your feedback in the comments through the end of the week.

Upcoming releases: WordPress 5.8

@jeffpaul reminded the group that 5.8 is in Feature Freeze, as of Monday, May 24. That means the work now shifts to fixing bugs, finding defects and finishing tasks. To that end, @boniu91 and @lukecarbishave scheduled a Test Scrub on Friday, May 28, and two bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs on Monday.

(Ed. note: No word on how the scrubs will affect mosquito activity in the US over the holiday weekend, which traditionally involves eating meals outdoors. 😜 )

The next milestone is 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, on Tuesday, June 8. At that point the work shifts again: to testing every change that made it in, and to fixing the bugs that come out of that testing.

(Ed. note: Most betas, release candidates and launches happen on Tuesdays, in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., and you’re invited to join the group that gathers there and helps test the brand-new software packages. You don’t need any special skills, and it’s a great way to start contributing. So mark your calendar for every Tuesday between June 8 and final release in July!)

After that announcement of the impending milestones, @jeffpaul asked for calls for help.

@chanthaboune brought up ticketticket Created for both bug reports and feature development on the bug tracker. #31935 as a high priority, and @clorith surfaced #30910 which also needs a push.

@francina said she’s changed #51809 to future-release from the current milestone, because it needs to start with a lot of discovery. Component maintainer @marybaum (disclosure: your faithful reporter) suggested a more specific discussion, around starting with a message strategy, when interested parties have the time.

Components check-in

@sergeybiryukov reported on Comments and Themes.

The Comments screen for a single post has acquired a link to View Post, per #52353. And in Themes, in the Adminadmin (and super admin) menu next to the Themes item, there’s an update button with the number of updates — just as there has long been for Plugins — per #43697.

He reported no major news on the other components he helps maintain.

@clorith reported on Site Health: it has a good first bug up for grabs in #52642, if you’d like to jumpstart your code contributions. He says he’s available to help show you how to make a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing..

@audrasjb had no major news on Widgets (Classic) or Upgrade/Install, but announced that #21603 made it in before Feature Freeze. He gave props to @maxpertici and @joedolson.

Open floor

@chanthaboune, on the 18th birthday of WordPress:

Tomorrow is WordPress’ 18th birthday :tada: and a post will go up on /news tomorrow with a little celebration page. also, props to the polyglots who have been working on that page this week.

@marybaum noted she’d been looking for 3D-content plugins in 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 Directory. It was no surprise to her that the best one (for her) has a familiar author: @sergeybiryukov!

#5-8, #dev-chat, #summary

Dev Chat Agenda for May 26, 2021

Here is the agenda for this week’s developer meetings to occur at the following times: May 26, 2021 at 5:00 UTC and May 26, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

Blog posts that need feedback

5.8 Schedule Review

  • Now in Feature Freeze leading up to 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 in 13 days on Tuesday, June 8th
  • Focus now shifts to defects and tasks in the milestone
  • Test Scrub on Friday, May 28th at 13:15 UTC in #core-test
  • Bug Scrubs next week on Tuesday, June 1st 20:00 UTC and Wednesday, June 2nd 04:00 UTC
  • RC 1 in 34 days on Tuesday, June 29th
  • 5.8 release in 55 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

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

#5-8, #agenda, #dev-chat

Dev chat summary: May 19, 2021

@peterwilsoncc and @jeffpaul led the two chats–05:00 and 20:00 UTC—on this agenda.

Featured blogblog (versus network, site) posts

A Week in Core comes from @audrasjb and recognizes 90 contributors, of whom 18 were new last week.

What’s new in Gutenberg? Find out from @vdwijngaert.

An update on the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor from @itsjusteileen talks about that team’s monthly priorities:

  • Global Styles
  • Navigation
  • Widgets Screen
  • FSE
  • Mobile Projects

@francina reports on the Upgrade/Install meeting from Tuesday, May 18.

@desrosj took to the News blog to announce that Core is dropping support for IE11 in 5.8, what that means and how it will affect themes.

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). (https://en.wikipedia.org/wiki/Accessibility) team has a proposal for updating TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keywords. They’d like another round of review, according to @joedolson’s post.

And finally, @mattchowning posted an apology for any consequences folks have suffered as a result of Gutenberg’s dual-licensing issues. In the 20:00 UTC meeting, @jeffpaul also blamed himself and other folx for the project’s overall approach to getting consent. Jeff recommends that if you’d like to discuss the situation further, please comment on the post respectfully and professionally.

Posts that need feedback

Jeff highlighted @andraganescu‘s post asking for help testing the Widgets editor and asked everyone involved with Core (ed. note: including you, dear reader) to blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. out some time to do that.

@drewwestcott and @daisyo shared some feedback on the instructions, and @webcommsat reported that Marketing is encouraging Meetups to promote the tests.

Next release: 5.8

Both facilitators issued a reminder: Feature Freeze is now five days away, on May 25, according to the full schedule.

In the 20:00 chat, @desrosj flagged that the 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. https://wordpress.org/gutenberg/ feature freeze is today, May 20, with RC1.

At that point, @jeffpaul pause[d] for what will feel like an uncomfortable amount of time to allow for calls for help…

@clorith pointed out that his component, Site Health, has a number of tickets marked ‘Good First Bug’ that could land in 5.8, if new contributors want to pick them up. Since he was mobile during the meeting, @desrosj compiled this list.

Other tickets mentioned:

#53212, from @pbiron, which @davidbaumwald said he’d review this week.

From @mte90: #44098, #15145, and #17025. @audrasjb said he owes @mte90 some feedback on those tickets, and @francina indicated she has an interest in the outcome.

Component maintainers

@jeffpaul moved the chat on to ask component maintainers to share plans and needs for help for 5.8.

@sergeybiryukov reported several items.

Plugins: Core finally supports the Update URI 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 headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes., so third-party plugins no longer risk getting overwritten by an update of a similarly named plugin from the WordPress.org Plugin Directory. See changeset [50921] and ticketticket Created for both bug reports and feature development on the bug tracker. #32101 for more details.

General: `wp-config-sample.php` has some new language that makes it clear that custom values should go in specific places, not just at the end of the file. Details are in #37199.

@desrosj brought in an update from @youknowriad on Core-editor.

@antpb reported on some meeting-time changes for Media.

@chanthaboune: Marketing is switching from pre-merge to post-merge, pre-release work—that means boosting the signal for testing features and the 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., and building general awareness of FSE.

@audrasjb on Menus: Still planning to ship #21603 before feature freeze. On (Classic) Widgets: no major news.

@milana_cap on Docs: Starting collaboration with Docs team, especially with @bph for Block Editor user docs, and to get every handbook ready before release. She has also started populating the spreadsheet for tickets that need dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase..

@sabernhardt shared that the Toolbars component has two tickets in the milestone: #28569 and #26933.

Open Floor

@jeffpaul led off Open Floor with two 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. announcements:

1) WordCamp Northeast Ohio Region is this weekend.

2) WordCamp Europe tickets are going fast; register for your FREE ticket now. 

@clorith announced the Support team is looking for another deputy or two. Their workload has been growing over the years, and it’s more than what one rep can comfortably do these days. And, he pointed out, it’s a great opportunity to get involved without writing code. Details are here.

#5-8, #core, #dev-chat, #meetings, #summary

Dev Chat Agenda for May 19, 2021

Here is the agenda for this week’s developer meetings to occur at the following times: May 19, 2021 at 5:00 UTC and May 19, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

Blog posts that need feedback

5.8 Schedule Review

  • Final Alpha Scrub focused on features and enhancements before Feature Freeze on May 24, 2021 at 20:00 UTC
  • Feature Freeze in 6 days on Tuesday, May 25th
  • 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 in 20 days on Tuesday, June 8th
  • RC 1 in 41 days on Tuesday, June 29th
  • 5.8 release in 62 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

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

Props @desrosj for peer review.

#5-8, #agenda, #dev-chat