Dev Chat Agenda, September 13, 2022

(Update September 14, 2022, 20:30 UTC – walkthrough transcript added to Section 4, Releases. @webcommsat)

The weekly WordPress Developers Chat will take place on Wednesday September 14, 2022 at 20:00 UTC.
All are welcome to join the chat in the #Core channel of the Make 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/..

1. Welcome

Summary from the Extra Dev Chat at WordCamp US Contributor Day on September 11, 2022

2. Announcements

Any new announcements? Nothing received for the agenda.

3. Blogblog (versus network, site) posts

Canonical Plugins Revisited post (September 11, 2022) – posted by @matt.

WebP in Core for 6.1 post (September 11, 2022) – posted by @matt.

Discussion under Focus group updates (images) in the Performance team meeting about WebP after announcement about it and 6.1 release.

Let’s make WordPress officially support SQLite proposal posted by @aristath.

A Week in Core (September 14, 2022) – thanks to @audrasjb.

Feedback request for Proposal to add a dominant color background to images posted by @pbearne.

Welcome to the new team reps for the Performance team: @shetheliving and @flixos90 (Slack IDs @shetheliving and @flixos90).

Have a post on WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ to share for dev chat? Add it to the comments.

4. Upcoming releases

a) The next major is 6.1.

Update from the release squad and any questions.
6.1 development cycle
Bug scrub cycle

Update on the 6.1 product walkthrough and transcript (September 14, 2022).

b) Minor releases

Update if needed.

c) Discussion on early timeframe

Is there anything new on this discussion?

5. Components and tickets

Are you a component maintainer? Shepherding a ticketticket Created for both bug reports and feature development on the bug tracker.

6. Open floor

Please add any items for dev chat to the comments.

#agenda, #dev-chat

Devchat summary, September 11, 2022

1. Introduction and welcome

Start of the meeting on the #core channel of the 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/.

@marybaum led this extra 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. US 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/. Developers Chat in-person and virtual on this agenda.

A huge welcome to our new WordCamp US contributors to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.!

2. Announcements

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/ 14.1 RC1 will land September 13. 14.1 will be the last version that merges into WordPress 6.1. More details in this Editor chat summary.

3. Blogblog (versus network, site) posts of note

Block-based template parts for Classic themes – highlighted in the core-editor meeting

Improving DevHub code references

A week in Core, September 5, 2022 – thanks to @audrasjb

Ending security updates for WordPress versions older than 4.0

Thanks to dev chat cohost, @webcommsat for the links and running a dev chat check-in at the usual meeting time in core on Wednesday. Summary from the check-in are in the comments on this post.

Summary from last week’s dev chat on August 31, 2022 – Props to @webcommsat for doing the notes, @marybaum and @costdev for review.

WordPress 6.1 Release Product Walk-through, Thursday September 13, 2022, 16:00 UTC. All welcome to join. The zoom link will be shared before the event.

Block-based template parts for Classic themes – highlighted in the core-editor meeting.

Add a dominant color background to images proposal – shared in the Performance team last week.

4. Upcoming releases

The next major is 6.1. Bug scrubs are happening on schedule.

The next minor will be 6.0.3, if tickets show there is a need for it.

5. Components and tickets

@costdev raised an enhancement ticket on Trac to revise the ticketticket Created for both bug reports and feature development on the bug tracker. screen. Link to the discussion on Slack.

And in honor of #WCUS, @jorbin raised a good first 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. in #56547.

6. Open floor

@matt highlighted two core blog posts.

WebP in Core for 6.1

Canonical Plugins Revisited

Nothing else was raised during the session. If anyone has items to add, please do so in comments.

The next dev chat will take place on Wednesday September 15, 2022, at 20:00 UTC

Props to @dpotter05, @leeseoftbc, @rcorrales, and @leeseoftbc for finding out about dev chat and for learning about writing the summaries, to @marybaum for leading the meeting.
Props to @webcommsat for editing the post, and to all those who attended,
helped or supported core tables on Slack or in person

#dev-chat, #summary

Canonical Plugins Revisited

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 is great, but many plugins are controlled by a single dev or company, and often end up going a direction of a premium or pro version, sometimes even removing functionality that used to be in a plugin and pushing it into the pro version. This can also create an incentive to put something into a SaaS service that is easily done in a more distributed fashion locally to the site. Even accepting donations can create some weird incentives for how to divide those among a number of contributors.

WordPress itself thrives because it’s a collaborative effort of many people with many varied interests, but coming together to create something that is explicitly 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., free, and available to all. We need to evolve the plugin directory to make it easier to accept code and documentation contributions. (We’re pretty good with translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. contributions already.) Also I think we should build on the successful history of canonical plugins like MP6, 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/, and 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/. to have more community-developed plugins, called canonical because they will be the official first-choice recommendation by coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and w.org for an area, that share in the ethos and approach of WordPress itself but to a more niche area that might not be right for core.

We are reaching a point where core needs to be more editorial and say “no” to features coming in as ad hoc as they sometimes do, and my hope is that more Make teams use this as an opportunity to influence the future of WordPress through a plugin-first approach that gives them the luxury of faster development and release cycles (instead of three times per year), less review overhead, and and path to come into core if the plugin becomes a runaway success. I am very conscious that when people are aiming to have something in core, a “no” or “not now” can be frustrating and sometimes create artificial pressure to put something in before it’s ready, as I believe happened with the REST API in WP 4.4.

Canonical plugin ideas for each make team:

Design: More adminadmin (and super admin) themes.
Mobile: (not sure)
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): An alternative 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.-based admin designed for accessibility and simplicity.
Polyglots: Inline translation submissions for core and plugins and themes.
Support: Related threads or documentation pages dynamically loaded from w.org for the “help” dropdowns on every page.
Documentation: Experiment with adding more inline documentation to wp-admin interfaces. Gather opt-in stats on what is actually read and used, which links to .org get clicked on.
Themes: Better previews of theme customizations, activation workflows that allow customization of colors / images / typography.
Plugins: Inline rating and feedback for plugins, crash and compatibility data reporting back.
Community: Experiment with the 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. that promotes events to call to action for organizing when there’s not a local meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area., and better incorporates online events including workshops and cohort classes.
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.: Login with .org login account. Dashboard with all of your linked WPs on w.org. Monitor versions, install plugins with one-click, etc.
Training: Courses or training in every help dropdown.
Test: Opt-in JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. or PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher error catching that reports back to a tracking server.
TV: Integration with help dropdowns, inline tutorial videos.
Marketing: Widgets and blocks for people to link back to W.org, like super-charged “powered by”, and promote their liked or favorite plugins and themes.
CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.: N/A.
Hosting: Experiment with standard 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., icons, and menu items for hosts to link or embed things like email, domains, contacting support.
Tide: Show the data more places in wp-admin.
Openverse: Should actually just come into core more, but perhaps plugin would be a good place to experiment with submitting something to openverse and CC licensing any media upload. Community and collaborative tagging of uploads and openverse items.
Photos: Similar to openverse, make it possible to submit uploads and search directory.
Core performance: WebP conversions for new uploads and batch processing to convert old images. Show before-after space usage and page performance. (Previous post on WebP in 6.1 that inspired this.)

This is not meant to be an exhaustive list, and I’m sure the teams themselves could come up with much better ideas and options, but I hope it sparks discussion at 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/. and beyond on how we can utilize plugins better to increase the speed of evolution for WordPress, keep core light, fast, and opinionated, and do so while saying “yes” to more ideas and experimentation.

WebP in Core for 6.1

I’ve been reading through all the conversation and issues here. I am interested in supporting new formats and improving performance, but I think this change being pushed by default to users when they upgrade to 6.1 is a lot for right now, including with some of the clunky interactions OSes still have around webp (and HEIC!) files.

I’m happy for support for working for webp and HEIC files to stay in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., as we should be liberal in what we accept and work with, but not with the change to convert everything to webp when JPEGs are uploaded.

This is excellent territory for a canonical 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, a concept I think every Make team should be exploring a lot more as a place to experiment and push functionality, much like we have with MP6 and 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/ in the past. I think the plugin directory needs more collaborative, community-developed, and non-commercial or no-upgrade plugins that do something well, and make teams are the perfect groups to develop and maintain those. It’s the ethos and process of core applied to plugins, that then we can officially recommend and feature in the plugin directory, and also allows us to keep core light or give more time for the ecosystem around something (like WebP) to mature.

Will do a second post on canonical plugins.

WordPress 5.9 Release Squad

Update on 5.9, the schedule and more on the 5.9 Development cycle page.

WordPress 5.9 is full steam ahead towards the December 14, 2021 release date. With the Go/No Go deadline behind us, the necessary roles required for this version’s release squad have become more clear, and the team is starting to take shape.

Below is the list of roles the squad roles for the 5.9 release with confirmed contributors listed. Any role listed with a hand raised emoji (✋) still need contributors and volunteers.

  • Release LeadRelease Lead The community member ultimately responsible for the Release.: @matt
  • Release Coordinators:
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads: @chaion07, @audrasjb.
  • Editor Tech: @noisysocks, @mamaduka.
  • Editor Design:
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech: @hellofromtonya. ✋
  • Theme Leads: @kjellr, @jffng.
  • Technical Writer: @psykro. ✋
  • Documentation Leads: @mkaz, @milana_cap.
  • Marketing & Communications: @chanthaboune. ✋
  • 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) Lead:
  • Test Leads: @boniu91, @annezazu.

Some Notes

  • The release squad list on the 5.9 development cycle page has also been updated. As additional contributors are confirmed for the positions needing volunteers, they will only be added to the development cycle page (not accompanied by an additional post here).
  • @noisysocks is coordinating a group of feature-specific contributors, and will be the main information person for all editor related features.
  • All WordPress 5.9 related coordination will happen inside of the #5-9-release-leads 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/. room. This room is a public viewing area for transparency (and knowledge sharing!), but is a workspace for that release squad so please limit posting as much as possible for those not on the release squad.

Props @chanthaboune and @jeffpaul for peer review.

#5-9

DevChat meeting Summary – April 28, 2021

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

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

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

Announcements and news

Feedback on posts requested

  • @iandunn needs your input on the topic of assisting 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 to avoid specific bugs that result in WordPress end users having a bad experience. He has suggested potential solutions including static code analysisStatic code analysis "...the analysis of computer software that is performed without actually executing programs, in contrast with dynamic analysis, which is analysis performed on programs while they are executing." - Wikipedia, and has provided a list of questions to help guide the discussion. Do read it and provide feedback from your perspective.
  • @francina: Would Stats Dashboards Help Your Team? Read this post for more details. Would folks in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. feel that any sorts of stats on a dashboard would support in their work in core?
  • New team CC Search to join WordPress. CC Search, a CC0 (Creative Commons Zero) image search engine, is joining the WordPress project with more than 500 million openly licensed and public domain images discoverable from more than 50 sources, audio and video soon to come. Read this post for more information @chanthaboune: more news and context coming in the next few weeks.
  • Wonderful design reference for those looking for ways to quickly prototype WordPress UIUI User interface in Figma. Read this blog post
  • WP Briefing podcast. @jeffpaul: these are super quick to digest, provide a good on-ramp to what’s latest in WordPress. Check out all the episodes at this link and find links to subscribe in your favorite podcast app.

WordPress 5.8 Release

@francina gave an update – Thanks to everyone who volunteered and right now I can confirm these roles:

Release leadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg (@matt)
Release Coordinators: Jeff Paul (@jeffpaul) and Jonathan Desrosiers (@desrosj)
Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead: Luke Carbis (@lukecarbis)
Core Tech Lead: Helen Hou-Sandí (@helen)
Editor Tech Lead: Riad Benguella (@youknowriad)
Marketing and Communication Lead: Josepha Haden-Chomphosy (@chanthaboune)
Documentation Lead: Milana Cap (@milana_cap)
Support Lead: Mary Job (@mariaojob)
Testing Lead: Piotrek Boniu (@boniu91)

  • @francina: “If I have messaged you and asked to join the release as part of the supporting crew, thanks for being part of the collaborative work that makes WordPress so great. Everyone! Join us in the channel #5-8-release-leads
  • If you have any questions about releases which you are following along, and if you want to ask questions: #core and #core-editor are the right channels
  • 5.8 release team

Full Site Editing (FSE) related items

  • Open call to send in your questions on Full Site Editing (FSE) Round 2 – reminder from @annezazu that you can submit questions, no matter who you are. The call closes 12 May 2021. This is part of the collaboration in #fse-outreach-experiment
  • [More posts on FSE in the posts requesting feedback section above]
  • Marketing has social media text available which can be reused to promote the different FSE calls 
  • @helen making a 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. based theme with the full site editor

Component maintainers and committers update

  • @sergey: Work has continued on further fixing some long-standing coding standards issues in core, see ticketticket Created for both bug reports and feature development on the bug tracker. #52627 for more details.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: No major news this week.
  • @clorith: Site Health catching up a bit on older and unanswered tickets
  • @audrasjb: Menus, Widgets, Upgrade/Install: nothing new. I scrubbed some tickets in the Menus component but no major news to share.
  • Following on from discussion last week @marybaum nominates @abhanonstopnewsuk as co-maintainer for the Help/ About page component 
  • In the last week, they have been going through the tickets since and will give an update in future devchats.

jQuery

  • @Hareesh: some attention requested on #52163. With this out of the way, we would have less jQuery migrate warnings, and it would be easier to fix any remaining warnings.
  • @clorith: jQuery UI hasn’t been updated yet, we are still waiting on their release, which I believe is scheduled for the end of May/start of June 
  • @davidb: jQuery release is right before 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 then, if the dates hold
  • @clorith: Yeah, which is a bit tighter than I’d like, but it is what it is… we’ll have a look once it’s ready to see what’s going on and what the best approach is. Building from source while they’re still modifying it isn’t really an option in my opinion.

Open Floor

  • @notlaura: feedback requested on ticket #53070. Establish a Core CSSCSS Cascading Style Sheets. deprecation path, and ask if anyone is interested in working on it! This is something we’ve been discussing in #core-css

Community

  • @chanthaboune: As you may be aware, many of our fellow contributors are experiencing disruptions in their lives right now above and beyond the (seemingly) routine disruptions of this pandemic life. From big earthquakes to big spikes in COVID cases to unrest right outside their doors, some of your WordPress pals are hurting more than usual.
  • For my part, I can say take whatever time you need to take care of yourselves. You are important and WordPress is not more important than your health and well-being.
  • For all of us, if you haven’t reached out to your friends to see how they are, please do.

Thanks to @meher and @webcommsat for the devchat notes and @marybaum for her help with them.

#5-8, #dev-chat, #fse, #fse-outreach-experiment, #jquery

A Week in Core – April 26, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between April 19 and April 26, 2021.

  • 20 commits
  • 27 contributors
  • 38 tickets created
  • 2 tickets reopened
  • 31 tickets closed

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component.

Code changes

Bootstrap/Load

  • Add Function for reliable timing data – #39163
  • Improve get_bookmark() test coverage – #52988
  • Remove Internet Explorer 11 from the browserslist#53077
  • Update the caniuse-lite database – #52624
  • Update several dependencies – #52624
  • Add seeking support to stream test library – #52922, #52826

Coding Standards

  • Remove loose comparison in wp-admin/includes/plugin-install.php#52627
  • Use strict comparison in wp-admin/includes/update-core.php#52627
  • Use strict comparison in wp-admin/includes/class-wp-terms-list-table.php#52627
  • Fix minor, inline spacing issue in wp-admin/setup-config.php#52627

Code Modernization

  • Bring consistency to preparing some fields on Networknetwork (versus site, blog) Settings screen: – #51423

Documentation

  • Add a @since note to wp_mail() about using is_email() for validation – #52628

Editor

  • Shape 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 filters to work better with 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/ 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#52920
  • Abstract block editor configuration – #52920

External Libraries

  • Update Underscore to version 1.13.1 – #45785
  • Update Moment.js to the latest version – #52853

Plugins

  • When loading a plugin in a “sandbox” on activation, do it once – #31104
  • When loading a plugin in a “sandbox” on activation, do it in a separate function – #31104

Posts, Post Types

  • Pass the post object to the_password_form 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.#29008

Upgrade/Install

  • Prevent possible type errors during installation – #51423

Users

  • Share current user instance across functions – #28020

Props

Thanks to the 27 people who contributed to WordPress Core on Trac last week:

@peterwilsoncc (3), @hellofromTonya (3), @SergeyBiryukov (2), @jrf (2), @hellofromtonya (2), @hareesh-pillai (2), @matt (1), @xknown (1), @youknowriad (1), @nosolosw (1), @jeremyfelt (1), @andraganescu (1), @azaozz (1), @jorbin (1), @silb3r (1), @andy (1), @chaion07 (1), @mensmaximus (1), @DrewAPicture (1), @dd32 (1), @Mike_Cowobo (1), @TimothyBlynJacobs (1), @rmccue (1), @lukecarbis (1), @donmhico (1), @chriscct7 (1), and @shital-patel (1).

Congrats to our 2 new contributors of the week: @silb3r, and @Mike_Cowobo ♥️

Core committers: @sergeybiryukov (7), @peterwilsoncc (4), @desrosj (4), @davidbaumwald (2), @gziolo (2), and @jorbin (1).

#5-8, #week-in-core

WP5.8 Squad Call for Volunteers

Edit: 4/23/2021 @ 19:10 UTC – changed the references to contributors in the last paragraph to WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ usernames to help to make the connection. – @desrosj

With the schedule finalized and parts of 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/ phase 2 getting ready to merge, it’s time to put together a squad of focus leads for WordPress 5.8.

You can read more about the different roles in the handbook.

Here are the squad roles available:

The roles of release leadRelease Lead The community member ultimately responsible for the Release. and marketing/communications lead will be filled by @matt and @chanthaboune, respectively.

Expectations

Focus leads should be available for at least 5-6 hours a week to perform their tasks, with more time as milestones like Betas, Release Candidates, and General release approach. On the days of those milestones, you might need to dedicate 4-6 hours to WordPress on one day.

There are no limitations to where you come from. We are a global community, open 24/7 so you will schedule scrubs, if needed, according to your availability and potentially find a deputy to cover other timezones.

Because 5.8 is going to be a busy release, the squad won’t have mentorship or ride-along opportunities, like it did in the past, but as Josepha mentioned there is a public channel for the team to coordinate so that others can learn through observation.

This doesn’t mean you need to have all the answers to volunteer. 🙂 There will be a bunch of people available to help and support (the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team representatives, long-time contributors, etc…).

Are you interested?

Please leave your name in the comments with the role you are interested in or reach out to me (@francina), @audrasjb or @chanthaboune if you have any questions before raising your hand.

Thanks!

#5-8, #planning

Proposal: Treat FLoC like a security concern

Google is rolling out Federated Learning of Cohorts (FLoC) for the Chrome browser.

TL;DR: FLoC places people in groups based on their browsing habits to target advertising.

Why is this bad? As the Electronic Frontier Foundation explains in their post “Google’s FLoC is a terrible idea“, placing people in groups based on their browsing habits is likely to facilitate employment, housing and other types of discrimination, as well as predatory targeting of unsophisticated consumers.

This is in addition to the privacy concerns of tracking people and sharing their data, seemingly without informed consent – and making it more difficult for legislators and regulators to protect people.

So What Now?

WordPress powers approximately 41% of the web – and this community can help combat racism, sexism, anti-LGBTQ+ discrimination and discrimination against those with mental illness with a few lines of codeLines of Code Lines of code. This is sometimes used as a poor metric for developer productivity, but can also have other uses.:

function disable_floc( array $headers ) : array {
	$permissions = [];
	if ( ! empty( $headers['Permissions-Policy'] ) ) {
		// Abort if cohorts has already been added.
		if ( strpos( $headers['Permissions-Policy'], 'interest-cohort' ) !== false ) {
			return $headers;
		}
		$permissions = explode( ',', $headers['Permissions-Policy'] );
	}

	$permissions[] = 'interest-cohort=()';
	$headers['Permissions-Policy'] = implode( ',', $permissions );
	return $headers;
}
add_filter( 'wp_headers', 'disable_floc' );

What About Admins Who Want FLoC?

Those websites who want to opt into FLoC are likely to have the technical know-how to simply override this proposed 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. in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

When balancing the stakeholder interests, the needs of website administrators who are not even aware that this is something that they need to mitigate – and the interests of the users and visitors to those sites, is simply more compelling.

Furthermore, for WordPress versions that support privacy settings, we can easily add an on-off toggle to enable websites to opt in. This would only require a few more lines of code and only a couple of new strings.

What Do You Mean By “Treat It Like A Security Concern”?

  1. Include the 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 next 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., rather than waiting for the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.;
  2. Back-port the patch to previous versions of WordPress.

Why Treat It That Way? Why Not Just Wait For The Next Major Release?

Well, keep your eyes peeled, because there is a ticketticket Created for both bug reports and feature development on the bug tracker. for future releases on its way!

While it is indeed unusual to treat a new “feature” this way, there is precedent in that something that was not strictly a security vulnerability in comments was back-ported to previous versions for the good of the community as a whole.

Currently, 5.8. is only scheduled for July 2021. FLoC will likely be rolling out this month.

Furthermore, a significant number of WordPress sites only update to minor versions. By back-porting, we can protect more sites and more visitors to those sites – and amplify the impact.

Request For Comment

Please join the discussion below!

Whether want to show support, disagree vehemently, or just want to make the implementation the best that it can possibly be, please have your voice be heard.

I’m aware that there is a lot of discussion on other platforms, including Twitter on this matter, but we won’t see all of it, so in addition to spreading the conversation there, please comment here too, so that it can be considered when this is discussed at development meetings and when the ticket is created (consensus building first – and that is done here 😉 )

YOU DO NOT HAVE TO BE A DEVELOPER TO PARTICIPATE. There will be a ticket on core.trac.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ where we will discuss all of the technical stuff. I’m tremendously grateful that there are so many developers, Core, 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. and others, around, but blogblog (versus network, site) posts on make.wordpress.org are the places that are accessible to techies and non-techies alike 🙂

Version Control:
1. Edited to add clarification that treatment like a security concern refers to the process / procedure (accelerated development and back-porting).
2. Code snippet updated based on suggestions below. Thank you to Tom for the snippet and to everyone who suggested conditionally appending, rather than replacing.
Added some more info to the Request for Comment.
#core-privacy