Dev Chat Summary: February 24, 2021

This post summarizes the weekly dev chat meeting from February 24, 2021 (Slack Archive). There was no APAC timed dev chat this week.

Announcements

WordPress 5.6.2 was released on Monday, February 22, 2021.

WordPress 5.7 RC1 is also available for testing!

5.7 Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. & developer notes

The WordPress 5.7 Field Guide has been published! All developer notes for the 5.7 release are included. Head on over and dive in!

All 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. related to the 5.7 release can also be found by browsing the 5.7 and dev notes tags. Props to @audrasjb for making sure every ticketticket Created for both bug reports and feature development on the bug tracker. needing a 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. had a guardian.

Blogblog (versus network, site) post highlights

Component maintainer updates

  • Build/Test Tools: @sergeybiryukov shared #33043, #52643.
  • Upgrade/Install: @audrasjb reiterated the call for feedback on the Rollback Plugin Update Feature Plugin post.
  • Date/Time: No major news to share this week.
  • General: No major news to share this week.
  • 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.: No major news to share this week.
  • Permalinks: No major news to share this week.
  • Menu/Widgets: No major news to share this week.

Open floor

  • @davidbaumwald proposed adding an officially recognized needs-testing-info keyword to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. that can be used to request better documented steps for testing a proposed 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.. The Meta-#5634 ticket has been opened to field feedback.

Next week

The next dev chat meetings will take place on Wednesday, March 3rd, 2021 at 5:00 UTC and Wednesday, March 3rd, 2021 at 20:00 UTC in the #core 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/. channel.

Props @hellofromtonya, @cbringmann, and @audrasjb for proof reading.

#dev-chat, #summaries, #summary

CSS Chat Summary: 18 February 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • @ryelle volunteered to run next week’s 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. scrub (Thursday 25 February @ 21:00 UTC) – thanks @ryelle!

Discussion: Deprecation flow for base styles

  • Last week’s bug scrub brought up this Gutenberg issue about an SCSS variable that was removed from the wordpress/base-styles npm package
  • The issue asks if a deprecation policy & notice period exists, or should exist, for SCSS variables, since they may be used by developers in contexts other than coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • After some discussion @ryelle suggested the #core-editor meeting might be better equipped to delve into this issue
  • @notlaura offered to bring this up at the next #core-editor meeting (Wednesday 24 February @ 14:00 UTC)

Updates

Color Scheming (#49999)

CSSCSS Cascading Style Sheets. Audit (#49582)

Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. testing (#49606)

Open Floor + CSS Link Share

With that the meeting drew to a close.

Thanks everyone!

#core-css, #summary

CSS Chat Summary: 11 February 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Housekeeping

  • Happy Birthday CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. Chat! We shared a pleasant moment reflecting on & celebrating the achievements of the group’s first year
  • @kburgoine asked for somebody to raise the profile of upcoming 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 by posting a note an hour before in #core (for TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.) & #core-editor (for 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/). @notlaura offered to do this
  • @tellthemachines offered to announce the regular bug scrubs in the APAC dev chat, and
    @kburgoine offered to do the same in the EMEA dev chat

Discussion, continued: Introducing CSS Custom Properties to WP Adminadmin (and super admin)

  • @notlaura summarised last week’s discussion where there was general agreement that an abstraction layer was the way to move forward with custom properties, starting with a small piece and prefixing the property with --experimental to indicate caution to 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 developers
  • @notlaura suggested starting with a variable from the abstraction layer as outlined in @ryelle’s blog post, for example the button abstraction
  • Discussing the colour scheme colours required by buttons, @notlaura identified 5:
    • Background regular
    • Background hover/focus
    • Text regular
    • Text hover/focus
    • Border focus
  • A helpful next step would be to mock up a button with custom properties in Codepen or similar, in order to iterate on naming decisions
  • The discussion briefly touched unifying admin styles and Gutenberg styles which, while not formalised, we tentatively agreed should be a long term goal

Project updates

CSS Audit (#49582)

Open Floor + CSS Link Share

The meeting ended with virtual slices of Core CSS birthday cake. Thanks everyone!

#core-css, #summary

Dev chat Meeting Summary: 17 Feb 2021

Full meeting on Make WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/.

Main discussions from 05:00 meeting:

  • @afragen: the Rollback Update Failure repo (here)
  • @tellthemachines: CSSCSS Cascading Style Sheets. themed 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 in #core-css (here)

Announcements

5.7 -related

  • 5.7 Beta 3 is here! Thanks you for testing, and to all the awesome people who have been tirelessly working on making WordPress happen—even going into this second year of pandemic.
  • WordPress 5.7 Docs Focus update: @audrasjb
    • Several 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. are just about ready, pending final review from component maintainers or by the corresponding ticketticket Created for both bug reports and feature development on the bug tracker. authors.
    • A list of the HelpHub pages that need updates once 5.7 launches.
    • If you worked on a ticket labelled needs-dev-note, or if you want to work on a devnotedev 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., please get in touch with @audrasjb to keep everything coordinated. (Ed. note: And the release squad knows where to send your props!)
  • Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. is still planned for RC1 next week. Co-ordinating with component maintainers taking place.

Minor releases

WordPress 5.6.2. RC 1 now available – @desrosj 5.6.2 

  • This one is a very small release, and the majority of the bug testing could be done in 10-15 minutes.
  • Additional testing available, raise tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets if any issues found. Focus to continue on 5.7
  • 5.6.2 will be pushed out on Monday 22 February 2021.
  • Aim is to try out a much smaller minor 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., which fixes a small handful of user-facing bugs that were finished and ready to go.
  • If it’s received well, we could potentially explore more frequent, smaller minor releases.
  • If you have any feedback around that, please feel free to share with @chanthaboune, @desrosj, or one of the Core team reps.

What’s new in 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/ 10.0.0

  • Version 10.0 is here!
  • It landed on 17 February 2021 and marks 100 releases of Gutenberg.
  • Congratulations to the Gutenberg team and all contributors involved.

Highlighted posts

Here are the latest 5.7 dev notes: 

Core editor front:

Full Site Editing:

  • work is going strong. Test, give feedback, ask friends to try it if they have never seen WP before and write down (with their consent of course) how they interact with the UIUI User interface, how does the UXUX User experience feels, etc.
  • @annezazu: The #fse-outreach-experiment needs you, no matter what you do with WordPress. The next call for testing will likely be this week, alongside a comprehensive update that follows the open submission for questions related to FSE.
  • If you want to test now, use this “How to Test” handbook page for FSE testing, and please share your feedback. (Though you don’t have to!)
  • Discussion: how to get more people sending feedback and asking questions, especially from people who do not follow the Core blogs.
    • @francina: raised questions on how to get more part, particularly students and meetups
    • @webcommsat: In Marketing, we are also helping non-tech users understand better what is happening on FSE and the benefits it will bring. This will help with future marcomms too. If anyone from a non tech background would like to add to the discussion session from this week, contact the Marketing Slack for the documents. We also work with community on newsletters and social to Meetups.
    • @timothyblynjacobs: Should we consider doing another Core dashboard 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./callout like was done for 5.0?
    • @nalininonstopnewsuk: request to let Marketing know please if this is planned at a future date to include in the schedule. 
    • @annezazu: Latest call for questions is closed, 47 questions received. There will be future rounds for open questions so we can continue to refine the general ‘reach’ going forward.
    • @lukecarbis: We’re starting to think about restarting meetups here in Australia, so maybe we could even do some in-person click-around testing, if there is a script.
    • Where is the best place to encourage outreach on this— #fse-outreach-experiment (not 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. channel) or somewhere else? @annezazu suggested #core-editor channel on Slack. @Clorith suggested FSE-outreach channel to get testing and feedback on the feature before it lands in core.
  • Discussion to continue after the meeting.
  • A Week in Core – February 15, 2021 
  • Making WordPress Releases Easier from @chanthaboune.

Updates from component maintainers

Build/Test Tools update – Updates shared by @sergeybiryukov

  • Single-and 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 PHPUnit test runs on 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/ Actions are now separate jobs so they run in parallel and finish faster. Total duration was ~26 minutes; now it finishes in ~16 minutes. Thanks @johnbillion. Ticket #52548: Run Multisite tests in parallel during CI for more details.
  • Work keeps going to add missing @covers tags to PHPUnit tests, for better tracking of coder coverage. Ticket #39265: Missing @covers in the comment blocks in PHPUnit tests for more details.

General: noindex robots metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) was added to search results, to keep search engines from indexing internal search results (and guard against reflected web spam attacks). Ticket #52457: WordPress vulnerable to search-reflected webspam 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 

More from Build/Test Tools@desrosj
The GitHub Action workflow files are now backported all the way through 3.7, to bring back automated testing for those branches if they need a security release. He will publish a post with the overall status of the work on 18 February. 

Upgrade/Install:

@fragen: Feature plugin Rollback Update Failure needs testing—just install and activate.

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 will create a zip of the current plugin/theme version in wp-content/updates/rollback. The first test: check whether or not the process uses too many server resources. Does it cause a server timeout? There’s a filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to simulate a failure.

@audrasjb  shared major news: @afragen has joined us as component maintainer

General component news:

@francina: Has started reaching out to component maintainers, both to gauge the situation of features/tickets for 5.8 and check how many are active. Those who aren’t will be moved to an emeriti status, like the one used for committers, as Josepha illustrated in the post Committers, Maintainers, and Emeriti

If you:

Open Floor 

@Eclev91: Raised ticket #43495: Use Semantic Versioning for releases and asked for it to be reopened. “I’ve reviewed the discussion that took place in Slack that prompted the ticket, which noted that because core is currently on a base-10 versioning system, new and ready-to-launch features like ServeHappy and GDPR were blocked behind Gutenberg development slated for 5.0 (the idea of a 4.10 to launch these features was unheard of and untested). I added my thoughts to the ticket outlining a variety of QOL improvements for both core development and core consumers (devs like myself who maintain many WP sites) that could be gained by moving to semantic versioning. I imagine folks with hosting companies working on automating updates would also have $.02 to add.” If anyone has feedback, please post it in the Trac ticket.

Testing instructions

  • @justinahinon: a WordPress testing instructions document was drafted at the 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 https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at Yoast (doc). Feedback about toning, phrasing, etc requested. Views on how it could work with the Core Handbook User Testing guide.
  • @jeffpaul: suggested a potential use could be in Make WordPress Test Handbook rather than the Core handbook .
  • @desrosj: this document is one that will be impossible to maintain over time. But it looks like each of the items you’ve detailed here so far look like great E2E test cases!
    • Some of these use cases could be used for user testing at meetups, or any other group of people that want to work on something together.
    • The steps change far too often release to release, and unless someone owns updating this document (or page) with each release, it will quickly become outdated. But if each of these are a test case, then they will fail when changes occur.
    • Not trying to discount having a document for testing at all! But feel this is far too detailed/intricate to maintain effectively for that purpose. 
    • @justinahinon: But if each of these are a test case, then they will fail when changes occur.

Growing Make Test Team

  • @francina: Interest in reviving the Test Team. It has been dormant for a while: no team reps, no chats.
  • During 5.6, @monikarao and others started weekly test scrubs.
  • @jeffpaul: queried whether weekly test scrubs were enough to consider people as leading the Test Team into action again. Worth encouraging.
  • Discussion: agreed.
  • @Desroj: Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. team actually falls under the Test team’s umbrella now. Results of that team’s efforts are usually posted to each individual ticket as we go through them. But that is just one form of testing.
  • We have a group of dedicated people showing up every week and that is amazing. At least one person on the team scrubs tickets present on a nearly daily basis.
  • @nalininonstopnewsuk: we are planning a promote a team every month idea in marketing. If you decide to put a plea out for testing team, let us know to feature it in the schedule. Agreed.

Thanks to @nalininonstopnewsuk, @webcommsat. and @marybaum for the dev-notes this week.

#5-7, #core, #dev-chat, #summaries, #summary

CSS Chat Summary: 04 February 2021

The meeting took place here on Slack@notlaura facilitated and @danfarrow wrote up these notes

Housekeeping

  • The next bugscrub (Thursday February 11, 9pm UTC) will be for 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/ issues with the styling label
  • UPDATE @kburgoine has agreed to run the bugscrub

Discussion: Introducing CSSCSS Cascading Style Sheets. Custom Properties to WP Adminadmin (and super admin)

  • @notlaura shared some links to provide context for the discussion
  • @joen outlined two high level hopes for the project:
    • Start simple – it’s easier to add complexity than to remove it
    • Build on the work already done on 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
  • @joen expressed concern about the number of variations in @ryelle’s base colour palette
  • @ryelle clarified that the palette is intended as a set of Sass variables to be compiled into a smaller set of function-based, public colour variables
  • If we followed that approach, the final choice of public colour variables would form the public APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. which would require ongoing support, so choices should be made carefully
  • @joen shared details of how the block editor uses a single focus style which adds a “spot colour” border – in dark mode a white halo is added to ensure sufficient contrast
  • @notlaura suggested a simple starting point for adding an abstraction layer: introduce 1 or 2 abstractions into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and track their success over a fixed review period
  • The initial abstraction variables could be hidden behind a feature flag or prefixed as --experimental
  • Time was running out but the discussion will continue in future meetings

Project Updates

CSS Audit (#49582)

  • @notlaura reported having added a comment to the ticketticket Created for both bug reports and feature development on the bug tracker. summarising progress in recent months
  • There were no updates for Color Scheming (#49999) or Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606) this week

Open Floor + CSS Link Share

On that polarising note the meeting closed. Thanks everybody!

#core-css, #summary

DevChat meeting Summary – February 10, 2021

@marybaum and @metalandcoffee 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

Announcements and news

Amongst other news, there is one interesting news to share: according to W3Techs, 40% of the web uses WordPress 💥

As said in the W3Techs blogpost, “The incredible success story of WordPress continues by reaching another milestone: 2 out of every 5 websites use it now.”

Upcoming WordPress releases

WordPress 5.6.1

WordPress 5.6.1 was released on February 3, 2021.

The minor 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. squad plans to release a quick 5.6.2 after some issues were discovered with Classic Editor. 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. is being worked on in ticketticket Created for both bug reports and feature development on the bug tracker. #52440.

WordPress 5.7

WordPress 5.7 beta 2 was released on February 9, 2021.

@metalandcoffee: 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. 3 is next, then RC1, RC2 and finale release.

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/ 9.9 was released last week! It’s the final release that will be included in 5.7 and contains some fun improvements and lots 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.

@melchoyce shared that the about page is in progress. The marketing team plan to work on the copy. @melchoyce asked to post the work-in-progress in ticket #52347.

@audrasjb started to work on 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. and to prepare the field guideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.. The first one was published a couple hours before the devchat. He will now reach out to ticket owners and component maintainers to ensure we have everything in time for RC1. Also, he started to identify what HelpHub pages (documentation for end-users) will need to be updated. @clorith mentioned the FAQ & Troubleshooting page, which is going to be recommended to users when there’s been a fatal error on their website.

Component maintainers updates

Build/Test Tools (@sergeybiryukov):

  • Work has completed on upgrading older branches to run on NodeJS LTS (currently 14.x), and backporting the local Docker environment to them. These changes unblock the ability to move automated testing over to 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/ Actions. See tickets #52341, #48301, and #50401 for more details.
  • The WordPress Importer 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 is now installed when installing the Docker-based local environment. See ticket #49720 for more details.

Thanks to @desrosj who is working on these tasks!

Date/Time, General, 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.

Customize (@dlh): #50781 has a new patch that could use review and testing.

Site Health (@clorith): Nothing new and exciting to report this week, lots of late-cycle ticket made it in though.

Upgrade/Install (@afragen & @audrasjb):

Editor (@noisysocks):

  • There are some editor issues the editor team would like to draw attention to:
    • Image 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.: Duplicate copies of media files created in library #25805
    • Cover: 9.8 does not migrate content position correctly #28656
    • Reusable block can’t be converted to a regular block #26421
    • Can’t paste text into editor on IE 11 #26988

Open floor

WordPress 5.8 release squad:

Discussion about Internet Explorer 11 support:

  • Global usage is now 1%
  • It might go up again though
  • Let’s discuss during next release cycle
  • Let’s prepare a Make/Core post to announce a potential end of support for IE 11

News from Training/Learn WP, by @webcommsat: “We are also continuing to work with Training and Learn WordPress about how we can bring all the extra information and resources post release together to support users, and looking forward to continuing to chat to Support and Docs too. This kind of working together is great and thanks to everyone who has been involved.”

#5-6-1, #5-7, #dev-chat, #summaries, #summary

CSS Chat Summary: 28 January 2021

The meeting took place here on Slack@notlaura facilitated and @danfarrow wrote up these notes

Housekeeping

  • @paaljoachim suggested that the bi-weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. 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 alternate between TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets & Gutenburg 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/ issues
  • @tellthemachines agreed & suggested triaging issues under the CSS styling label
  • @notlaura suggested doing this at the next bug-scrub which is scheduled for 11th February

CSS Audit (#49582)

  • @ryelle reported that the CSS Audit report is now updating & being generated automatically with changes to core – the automated commits reveal changes to core CSS as they happen
  • @notlaura suggested generating the report as 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. first, to enable changes to be tracked over time, to which @ryelle suggested adding a second action that generates a JSON report
  • @notlaura observed that this news will be a great update to add to the CSS audit ticketticket Created for both bug reports and feature development on the bug tracker.

Color Scheming (#49999) & Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)

Visual Regression Testing

  • @tellthemachines reminded us that her PR is still open & has received some review feedback
  • She plans to add more tests in the coming week, followed by tests for mobile breakpoints
  • She is also considering the basis on which the tests should be automated with Github Actions

Open floor & CSS link share

Thanks everybody!

#core-css, #summary

Media Meeting Recap – January 28, 2021

The following is a summary of the weekly Media component meeting that occurred on Thursday, January 28, 2021 at 15:00 UTC. Weekly media meetings are held every Thursday at 15:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @antpb, @paaljoachim, @hellofromtonya, @joedolson, @ricjcs, @audrasjb, @mista-flo, @mkaz, @chaion07

Open Floor

This meeting’s focus began with an open floor for discussion on outstanding tickets and issues members wanted to address.

#47839: Extended file management in Media Library – @ricjcs brought up this ticketticket Created for both bug reports and feature development on the bug tracker. containing design samples of what folders could look like in the media library. Discussion occurred around what this feature would entail from a backwards compatibility perspective.

#52372: Ability to Replace image on the “attachment details” screen – This feature has been explored and ultimately closed after this comment in #49096. Per @antpb, “This is another one where I don’t think it’s a bad idea, in fact, it’s great, but it’s very much in 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 territory to make the decisions for your individual site. What may be good for one site may not be good for all. Offering the ability to replace media by default offers folks ways to unintentionally break old content.”

5.7 Tickets

#52192: REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.: Add batch image editing This ticket is currently in review with @antpb and is aiming to be committed before alpha. It was discussed that this endpoint is low risk as it does not impact any existing endpoints and adds new ones.

#50025: Media Library not showing new uploads when filtering by date – This ticket is currently in review after it was found to have issues with the classic 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. media flow. @antpb is testing and will be aiming to commit before alpha.

#39004: Alt attributes should be searchable in media library – This ticket was discussed as being close to ready for commit, but talks after the meeting indicate it may need further testing with larger media libraries.

#52387: adjacent_image_link returns a link with no accessible text@antpb has given an initial review and is aiming to commit soon after more testing.

Bug Scrub

There are a number of enhancement tickets that still need to be scrubbed. A 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. scrub has been scheduled for Monday, February 1 at 16:00 UTC to go over these tickets. Please join us if you would like to contribute!

Props @antpb for proofreading and final review.

#core, #media, #summary

Editor chat summary: 27th January 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-01-27 14:00 UTC in Slack. Moderated by @andraganescu

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/ 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 Release

  • Gutenberg 9.9 RC has been delayed for January 29th 2021, to sync with the upcoming 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 of WordPress

WordPress 5.7 Beta 1

  • WordPress 5.7 Beta 1 is due for release on the 2nd February 2021.
  • Beta 1 will represent the cut-off point for new commits/features for 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.
  • The deadline for changes is Gutenberg 9.9 RC on the 29th January.
  • There is a WordPress 5.7 project board where you can follow along and keep up to date with progress.
  • WordPress 5.7 will include versions 9.3 to 9.9 of Gutenberg

Monthly Plan & Key Project updates

  • We requested updates on the key projects.

Full Site Editing

Global Styles

  • not many updates but issue 27506 is a good starting point to gauge GS status 

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. / Navigation Editor

@andraganescu provided an update for the widgets editor:

@mkaz added an update on the ongoing additions to the Navigation block:

  • The Navigation Block tracking issue is here, though we are also working on issues raised for items needed to help develop themes. So that list my get supplemented with a few additional issues. (edited) 

@grzim added an update about the navigation editor:

  • The work on menu name edit is back on track Issue 24581 . There is an ongoing discussion in #feature-navigation-block-editor about moving name edition to a side panel.
  • UXUX User experience and 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) issues have been fixed Issue 28183 , Issue 24369
  • Also inconsistencies in e2e tests are being fixed.

Task Coordination

@hypest provided a

short update about what the native mobile folks have been up to:

  • Reusable blocks rendered in-editor (only available in DEV builds for now)
  • Audio block close to merge
  • Fix for blocks auto-scroll when the keyboard appears
  • Fixes for issues resulting from some GB-web side changes
  • Fix for File block’s automated test.

@bernie will continue to work on some release tooling automation soon. Afterwards, there are two things on the automated testing front that I’d like to work on:

  • Run e2e tests in FF (draft PR).
  • Visual diffs (to avoid block regressions) (issue)
  • Anyone interested in helping with those? Experience with puppeteer would be especially helpful for the e2e tests!

@annezazu is working on the “What’s Next” post for February and the FSE program. For the FSE program, I’m trying to find creative ways for more people to help through sharing various roles for the program (helping write calls for testing, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. feedback, etc), updating documentation with more information about the process I’m loosely following/creating, and sharing an idea around how we can include polyglot communities! I wasn’t here to announce the how to triage in GitHub course is live on LearnWP too! Working on another course this week/next week for more 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/ basics 

@paaljoachim is Working on consolidating setup local dev environment + testing instructions for Gutenberg and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
Triaging Design and Gutenberg issues.
Working on a Dev site for support structure. Experimenting with the design for Learn and more. 

@mcsh updates:

  • Fixed a fatal infinite recursion issue in Reusable Blocks (@gziolo now fixing the same in Template Parts)
  • Code reviews
  • Too many conversations to name, but recently: with @ella about Footnotes, with @ntsekouras about focus bugs and other issues related to ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. refs, @gziolo about how we do e2e testing, table of contents block, etc.

@andraganescu did mostly code review and testing on widgets and navigation editors

@joen has been working on a bunch of small navigation block user experience related things:

  • Menu item word wrap
  • URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org cutoff
  • Menu item overflow menu polish
  • Button block appender
  • Space between

@itsjonq is Continuing his efforts to work on integrating the new Component System into Gutenberg (working on it directly as well as coordination). He is also tinkering with new UIUI User interface tools for Gutenberg in parallel, focusing specifically on background/color tools at the moment.

@ntsekouras updates:

  • Lot’s of triaging and GH reviews with some fixes
  • `Preferences` modal is probably ready to merge (PR /28329) – thanks @joen for the styling polish there

Open Floor

Will there be Global Styles also in the Post Editor? Or is that only to be for the Site Editor?

The general consensus on @paaljoachim‘s question was that the post is a place which lacks enough visibility for the impact the changes would have so most likely the answer now is no.

What’s Next post for February

@annezazu brought up the next focuses:

  • Preparing for 5.7
  • Global Styles
  • FSE
  • Block-based Widget Editor

Global styles in WordPress 5.7

@mcsf mentioned that whatever pieces of GS that may land in 5.7, they will concern the theme.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. structure and won’t impact users. At best, there will be experimental APIs that devs may use in Core, following in the footsteps of the well-known add_theme_supports extensions

AMA session about FSE and a dedicated FSE feature channel

@annezazu proposed to great enthusiasm an AMA session about FSE and also the creation of a dedicated feature channel for FSE.

A plan to standardize the use of feature channels

@priethor suggested a plan to standardize the use of feature channels:

  • Gather feedback on the overall feeling about these channels, whether folks think this segmentation improves communication or makes it more difficult.
  • If feature channels are agreed to be an improvement, create feature-specific channels for other feature projects such as FSE.
  • List these channels on the Feature Projects Overview page and promote them in automated welcome messages, as suggested by @annezazu.

@francina mentioned that “having multiple channels dilutes the attention of contributors, issues are not developed in a silo and are interdependent, so I am not sure having a myriad of channels is really helping, but willing to try”.

Internal 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 https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at Yoast on February 5th

Also @francina mentioned:

We are doing an internal Contributor Day at Yoast on February 5th. Let me know if there are some PRs that need developers and/or users testing

This is a great opportunity to bubble up things in need of testing or extra development hands!

Input wanted on the editing of a menu’s name in the navigation editor

Lastly @grzim called attention on PR 25343 where editing a menu’s name is added to the navigation editor, for sharing opinions on the approach taken there to make it as user-friendly as possible.

Thanks to everyone who attended!

#core-editor, #core-editor-summary, #meeting-notes, #summary

CSS Chat Summary: 21 January 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes (I’m trying a more bullet-pointy format this time – hope you like it!)

Housekeeping

@kburgoine has volunteered to lead next week’s 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. scrub which will begin at 9pm UTC on Thursday 29 January.

CSSCSS Cascading Style Sheets. Audit (#49582)

  • @ryelle is ready to merge some recent PRs on the audit tool [UPDATE now done, thanks!]
  • @notlaura is considering ideas for restructuring the property-values audits within the config file
  • @notlaura later mentioned that the !important audit report probably satisfied the requirements of #26350 and suggested that @kburgoine could bring it up at next week’s bug-scrub

Color Scheming (#49999) & Visual Regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. Testing (#49606)

  • @ryelle has had some feedback on her reduced colours PR and is hoping for one more nod from Design so she can commit in the next few days
  • @ibdz kindly offered to provide feedback this weekend
  • Next step for #49999 would be more CSS cleanup, plus picking up the previous conversations around design system, tokens & custom properties
  • @tellthemachines PR for #49606 is ready for testing – let’s go!

Open floor & CSS link share

  • @ryelle brought up #51763, a ticketticket Created for both bug reports and feature development on the bug tracker. about moving from node-sass to dart-sass, which needs 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.. @desrosj has offered assistance and @ryelle is happy to partner with anyone interested in helping
  • @notlaura shared a link to this CSS WG thread discussing ideas for expressing @media conditional values more tersely
  • @notlaura also shared this CSS WG thread about SCSS stats in the wild, with data analysis based on 300K SCSS stylesheets revealing that “inline if() is the second most used function (after darken() ) and accounts for 14.5% of all function calls

Thanks everyone for attending this week!

#core-css, #summary