Upgrade/Install Component meeting summary – October 13, 2020

These are the weekly notes for the Updates/Install component meeting that happened on Tuesday October 13, 2020. You can read the full transcript on the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-auto-updates 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.

The meeting was focused on the component’s major project for 5.6: an UIUI User interface for opting in to core auto-updates: #50907.

@audrasjb sent a first 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. for this feature and shared a screenshot of the first workaround:

This approach adds two checkboxes, to provide the ability to enable/disable auto-updates for both minor and major auto-updates.

@pbiron pointed out that disabling auto-updates for minor releases was already discussed during previous meetings, and the decision is that it is not an option the Core team wants to provide to end-users. It needs to be disabled by 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 or by using the existing hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. or PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 constants. @audrasjb will update his patch accordingly, so there will be only one available option: opt-in for major releases auto-update.

@estelaris added that there is already 4 buttons on this screen. It would be nice to avoid adding a new one. She added that we should use a toggle button instead of a checkbox + a submit button. @audrasjb answered that there is no existing toggle component in WordPress Core for now. This eventual new component also would need to be designed, developed, and its 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) would need to be tested and reviewed. It doesn’t look realistic for WP 5.6 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.

@paaljoachim proposed to move the auto-updates opt-in to General Settings. @pbiron and @audrasjb are not enthusiastic about this proposal as for now, the Updates screen seems to be the more natural place to find Core auto-updates settings.

@karmatosed pointed out that this screen is already a very dense interface. She will share some alternative designs this week on this Figma file, to help design decisions. @audrasjb will work on the patch implementation at the end of the week.

For beta 1, the team agreed that a robust technical implementation is needed, so we have a UI basis for this new feature. Then, the team will focus on phrasing and on polishing the interface elements.

@estelaris asked for documentation about plugins and themes auto-updates. The team shared all the existing documentation:

#auto-updates, #core-auto-updates, #upgrade-install

Editor Chat Agenda: 14 October, 2020

Facilitator and notetaker @andraganescu.

This is the agenda for the weekly editor chat scheduled for 2020-10-14 14:00 UTC.

This meeting is held in the #core-editor channel in the Making 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/..

  • Gutenberg 9.1 (Released 30 September)
  • 5.6 Project board
  • Monthly Plan for October 2020 and key project updates. With focus on issues, what is being done and help that is needed.
    • Global Styles.
    • Widgets screen.
    • CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. screen.
    • Full Site Editing.
  • Task Coordination
  • Open Floor

Even if you can’t make the meeting, you’re encouraged to share anything relevant for the discussion:

  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#core-editor, #core-editor-agenda

Dev Note Scrub for WordPress 5.6

With 5.6 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 approaching fast, there will be 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. 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 on 10/19/2020 19:00 UTC in the #core 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/..

The objectives are:

  • Recruit potential dev-note writers
  • Review 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.

This scrub will focus on 5.6 TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets that have the needs-dev-note keyword. Here’s the report: https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=closed&status=new&status=reopened&status=reviewing&keywords=~needs-dev-note&milestone=5.6&col=id&col=summary&col=status&col=milestone&col=keywords&col=owner&col=type&col=priority&col=component&col=changetime&order=changetime

What is a dev note?

A Developer note (or “dev note” for short) is a blogblog (versus network, site) post on the Making WordPress Core blog that details a technical change in an upcoming release and what developers need to know about that change.

Writing developer notes CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Handbook

Come join us.

This post was proofread by @hellofromtonya and reviewed by @davidbaumwald

#5-6, #bug-scrub, #dev-notes

Dev Chat Agenda: October 14th…

Dev Chat Agenda: October 14th 2020

Here is the #agenda for this week’s meetings happening at:
Wednesday, 14th October 2020, 0500UTC and Wednesday, 14th October 2020, 2000UTC .

Please share any items you’d like to include in the comments below.
* Announcements
* Highlighted blogblog (versus network, site) posts – (None at the time of posting this agenda)
* Calls from component maintainers and/or focus leads
* Open Floor
If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday, 14th October 2020, 05:00UTC and Wednesday, 14th October 2020, 2000UTC. These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack .

#agenda #5-6

CSS Chat Summary: 08 October 2020

Full meeting transcript here on Slack. @notlaura facilitated the meeting.

Housekeeping

@notlaura reminded attendees that she will be unavailable on 22 October and needs somebody to step in and run the meeting. If you’re up for it please let her know!

CSSCSS Cascading Style Sheets. Audit (#49582)

@notlaura reported progress on her PR to add the HTML report to @ryelle‘s super CSS Audit tool which now adds support for a --format=html command line option.

There is a remaining issue with the property-values audit, and contribution is still needed towards improving the design and info formatting.

@notlaura also mentioned an issue she added about the need for property-value audit groupings. A short discussion about possible solutions followed, which gravitated towards adding support for .json config files. @ryelle offered to write up an issue to outline the format she envisages for discussion in 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/.

@notlaura clarified the approaching milestones of merging her PR, updating the tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker., and enabling more progress on styling the report which @danfarrow (me!) has started contributing to.

@notlaura pointed out a failing test (Colors › should ignore colors in non-color properties) which @ryelle confirmed she had left as an aide-mémoire for herself to fix the associated issue. @ryelle suggested that this issue might be a good self-contained task for a new contributor to tackle.

Color Scheming (#49999)

@ryelle reminded us of her demo site where people can appraise the reduced-colors testing tool – details in this Slack message. Some issues have already been added to the github repo but wider testing is required.

The plan is to post in #design and #accessibility with info on how to access the tool, how to submit new issues, and prompts to help fix the issues.

@notlaura put out a call for somebody to help with this small task, and offered her assistance to clarify what’s required & to review the message before it’s posted. @ryelle added that she can still write the post if nobody else volunteers (although she had mentioned earlier in the meeting that this month is super busy for her so please consider helping out!)

CSS links share + Open floor

@notlaura shared a link to this CSS-Tricks article about the widening responsibility of front-end developers. @Andrew Joyce added a recommendation for an earlier article by the author on the same theme, The Great Divide.

We reflected about a time when writing CSS involved just writing CSS, and on that poignant note the meeting was closed.

Thanks to everybody who attended!

#core-css, #summary

CSS Chat Agenda: 8 October 2020

Note: One hour before the meeting this week, @ryelle will lead the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.! Triages are every other week one hour before the weekly chat, at 4pm EDT.

This is the agenda for the upcoming CSS meeting scheduled for Thursday, October 8, at 5:00 PM EDT.

This meeting will be held in the #core-css channel in the Making 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/..

If there’s any topic you’d like to discuss, please leave a comment below!

  • Housekeeping
  • Updates
    • CSS Audit (#49582) – grouping property values audits, audit for shorthand properties
    • Color Scheming (#49999)
  • Open floor + CSS link share

#agenda, #core-css

CSS Chat Summary: 01 October 2020

Full meeting transcript here on Slack. @notlaura facilitated the meeting.

Housekeeping

If anybody is interested in being a note-taker for these meetings we would love to have your help!

CSSCSS Cascading Style Sheets. Audit (#49582)

@notlaura recapped last week’s discussion of her PR to add report generation to @ryelle‘s nifty CSS Audit tool. A git rebase was required for @notlaura‘s PR which she reported is mostly done.

@ryelle reported that the PR is nearly ready to merge. @notlaura sought clarification from @danfarrow (me!) about whether it’s important to have a separate template partial for each section of the report. I was able to (eventually) respond that I believe it is indeed important because the data structure can differ between different report sections.

@ryelle reported having sketched out a promising 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/ action which would commit the generated report back to the repo, bringing us closer to the goal of automated reports with a version history.

Color Scheming (#49999)

@notlaura recapped last week’s progress where we had design team confirmation of the color list, plus a possible volunteer to help.

@ryelle reported an exciting update – she has set up a demo site on Pantheon for the reduced-colors test. The access details are here in Slack.

@ryelle added that anyone who would like to help or who needs adminadmin (and super admin) access can DM her with their email and she will create an individual admin account for them. She suggested that the wp-core-color-list repo would be a good place to track issues.

@notlaura questioned if we could make it clearer to testers where they can post issues by adding a 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. to the demo site with some instructions about how to contribute.

@ryelle agreed to add this, but also suggested that it would also be helpful for testers to run the branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". under their own setups to get a broader view of compatibility with various plugins, and in particular 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 setups.

There was a short discussion about the value of testing admin schemes at this stage, the outcome of which was “it wouldn’t hurt to check just in case”.

@notlaura pondered the best way to announce this to testers, and suggested notes in #design and #accessibility. @ryelle agreed to add notices to those channels.

CSS link share / Open floor

I (@danfarrow) shared a link to an app I found which is an interactive glossary of CSS vocabulary & terminology http://apps.workflower.fi/vocabs/css/en

It seems like a really useful learning tool, and was received with enthusiasm! There’s also an HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. glossary http://apps.workflower.fi/vocabs/html/en

And with that the meeting was concluded. Thanks everyone!

#core-css, #summary

Editor chat summary: 7 October, 2020

This post summarizes the weekly editor chat meeting (agenda here) held on 2020-10-07 14:00 UTC in Slack. Moderated by @get_dave.

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 updates

  • Attendees were reminded that the release of Gutenberg 9.2.0 will be delayed by 1 week in order to better sync with 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 for WordPress 5.6.
  • This means that October 19th will be the RC for Gutenberg 9.2 and the stable release will be on October 21.
  • We reviewed @youknowriad‘s “What’s new in Gutenberg” post focusing mainly on the last major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. of Gutenberg 9.1.0. Highlights included:
    • 200 commits and 77 contributors!
    • new `ComboBoxControl` component – useful for making a selection where the number of entries can be very high.
    • Lots of 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) enhancements.
    • Category selection for Block Patterns.
    • “Open in new tab” feature for the Social Links 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..
    • Image Size control for the Media & Text block. 
  • 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. release for Gutenberg 9.1.1 was also published during the chat which contained fixes for the 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. screen.

Preparation for WordPress 5.6 Beta 1

  • WordPress 5.6 will be the third and final major release of WordPress for 2020. As mentioned above Beta 1 is due on October 20th and this represents the cut-off point for new commits/features.
  • The focus for Gutenberg this month will be on deciding what can/cannot be ready for inclusion in WordPress 5.6.
  • A reminder that the Navigation Screen has already been removed from 5.6 in order that we can focus hard on refining the Widgets Screen (and associated editor APIs) with the aim of having it ready for inclusion.
  • Follow along with where things stand on this WordPress 5.6 Must Haves project board.

Monthly Plan & Key Project updates

Widgets screen

@mapk, @andraganescu and @zieladam provided the update:

  • Moved out of experimental status.
  • Big focus for this month in an effort to have it included in WordPress 5.6.
  • @mapk has created some issues around keyboard navigation in widgets screen and will complete all design related issues today (hopefully).
  • @zieladam noted that bringing the new editor into the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. is quite a challenge. We would appreciate commenting with any and all ideas anyone might have on this issue.
  • @zieladam said they’re also hoping to bring custom blocks and reusable blocks into the widgets editor soon (right now only coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks are available).
  • Please help with testing – there’s a call for testing and a place to share Issues identified.
  • Follow the project board for the Widgets Screen.

Global Styles & Editor focused APIs

@jorgefilipecosta provided the update:

  • Editable color palette ready to be merged.
  • PR that passes the editor settings dynamically, so when a setting is edited on the edit site screen the block editor shows immediately without a need for a reload.
  • Important proposal for a mechanism to automatically generate the preset classes (e.g.: themes will not need to create classes for colors, gradients, font sizes etc anymore).
  • Many follow up PR’s that we need to do after merging this ones:
    • Generate preset classes on the client-side
    • Make sure the palettes that appear on the global styles blocks are the ones associated with that block not the global ones (currently it just uses what useEditorFeature returns and it seems to be returning the global ones).
    • Make sure we use the presets vars on global styles. E.g.: if we set a preset font size, the style output should be font-size: var( –wp…) and not the value.

Full Site Editing

No one was available to provide an update so @get_dave provided some from his notes:

@vindl then stepped in to provide more detail on Milestone 2:

  • The template selector has been moved to the navigation sidebar. The pages dropdown will likely follow suit in the next couple of days, with which we’ll complete the removal of those dropdowns from the 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. area.
  • There is a PR open that adds the basic dropdown for Document Settings in the site editor. The exact content for it still needs to be decided by design.
  • Nice progress on template part visibility. The entity spotlight mode is ready to be merged, and the same goes for template part hover interaction provided that it’s approved by design.

Customizer

No one was available to provide an update. If anyone would like to provide this async, then please leave an update in the comments.

Task Coordination

Open Floor

All items this week came from the agenda comments:

The switch to taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. terms for FSE template post theme tracking

Moving forward with the Accordion block

  • @paaljoachim questioned how we can move forward with the Accordion block as it seems to have stalled.
  • Request for feedback and input on the PRs.

Will the Gutenberg repo participate in Hacktoberfest?

  • @zzap asked if Gutenberg will mark any of 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 for Hacktoberfest?
  • @get_dave noted that Hacktoberfest was affiliated with Digital Ocean.
  • @aaroncampbell corrected that Hacktoberfest is actually a wider-reaching movement (beyond Digital Ocean) – generally a kind of concerted effort to pitch in an help out open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL..
  • It was noted that Hacktoberfest can be super spammy as people submit dozens of low-quality PRs just so they can get a free t-shirt.
  • @paaljoachim and @aaroncampbell suggested it might still be a good way to get feedback on the project and get others involved.
  • @get_dave noted we already have a Good First Issue tag which could be used to direct Hacktoberfest contributors to.
  • It was noted that a repo must opt in to Hacktoberfest – it was suggested that @youknowriad and the Core team should leave their opinion and decision in the meeting notes (that’s here!).

Thanks to everyone who attended.

Dev Chat Summary 8th October 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, October 7th, 2020, 05:00 UTC and Wednesday, October 7th , 2020, 20:00 UTC, following this agenda .

05:00 UTC core dev chat
@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here .
20:00 UTC core dev chat
@laurora facilitated the meeting and @thewebprincess took notes. The full Slack archive can be viewed here .

Both groups followed this agenda: https://make.wordpress.org/core/2020/10/06/dev-chat-agenda-weds-7th-october-2020/

Announcements

No announcements today!

Highlighted Posts

  • https://make.wordpress.org/core/2020/10/01/whats-next-in-gutenberg-october/ No action needed, but posted for awareness as there are notes for 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. or 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 devs and in invite for those interested in contributing.
  • Requests for comments on Starter Content https://make.wordpress.org/core/2020/10/06/revisiting-starter-content-on-org-and-beyond/ – which is a request for comment.
  • Progress update on https://make.wordpress.org/core/2020/10/06/update-wordpress-5-6-release-progress/. No action required though a request for a graphic depiction of what the Full Site Editing simple, routine user flows was discussed. This will help give people a sense of how it’s likely to work when it does come into core as it’s currently hard to visualise something we’ve not seen before.

Updates from Component Maintainers/Focus Leads

  • Build/Test Tools, General: Continued work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 8 support:
    • The PHP 8 Docker image has been updated to use the same PHP extensions for PHP 8 that we have on PHP 7.x
    • A new NPM task has been added to use the Composer-installed version of PHPUnit
    • * There is an ongoing effort to fix some function argument type issues reported by PHPStan (a static analyzer): #51423.
    • * Next steps: More testing on PHP 8, expanding test coverage, and creating tickets for any issues found. A call for testing was published earlier this week: https://make.wordpress.org/core/2020/10/06/call-for-testing-php-8-0/
      Question was asked: Does PHP8 support need more people involved? A: Follow the issues here PHP8 Tag in trac
  • 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., Date/Time, Permalinks: No major news this week.
  • Site Health has had some attention in the past week to go over 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.-refreshes and tickets
  • External Libraries: jQuery update has some progress too #r49101 has updated jQuery and jQuery UIUI User interface. Please test!
  • Upgrade/Install: our main ticketticket Created for both bug reports and feature development on the bug tracker. ( 50907 ) is still in progress.

Open Floor

  • The Marcomms team noted that they’re inviting feedback in relation to the About Page for 5.6 in thisGoogle form feedback is are also welcome via tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. but this form will help make it more accessible to the wider community who might not be familiar with trac and its processes.
  • It was observed that the titles for the dev chat entries in the calendar weren’t updated with the UTC specific timings so @peterwilsoncc updated them to Core Development Weekly Chat (0500 UTC) and Core Development Weekly Chat (2000 UTC)
  • #40351 (Term post re-counts scale poorly, are common and difficult to avoid) – WordPress Trac which is slated for 5.6 has a patch, but the question was asked whether there’s enough time to test properly before adding to the release, after discussion, the plan is for further testing this week, if nothing breaks it will be added to the release.
  • Discussion then went on to explore options for dummy content for testing andthe contingent posted numerous options according to individual preferences to answer the inquirer.
  • #50658 was highlighted for review: ‘has patch. Tested. Has screenshots. Missed wp5.5 deadline and tagged for 5.6. Action: pings sent to the component maintainers for review
  • Ticket https://meta.trac.wordpress.org/ticket/5463 was highlighted for feedback in relation expediting updating process for component and focus teams. Please comment on that ticket if you have feedback.
  • https://core.trac.wordpress.org/ticket/50907 needs more eyes on it and feedback added to the ticket.
  • The Yoast team have put together a short term team to focus on Twenty Twenty-One development, they’ve created a project board which you can follow here to track progress of issues
  • Reminder: next test scrub on Friday October 9th 13:30 UTC
  • Requests for testing: of https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/ and

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 7, 2020, 05:00 UTC and Wednesday, October 7, 2020, 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. Please feel free to drop in with any updates or questions.

Props to @francina for the proofread.

#5-6, #summary

X-post: Block-based Themes and WordPress 5.6

X-post from +make.wordpress.org/themes: Block-based Themes and WordPress 5.6