Tonya Mork 4:54 pm on January 12, 2023
Tags: , , , ,   

DevChat Summary: Wednesday, 11 January 2023

This post summarizes the latest weekly CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team’s DevChat meeting (agenda, slack transcript), held 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, on Wednesday, January 11, 2023, 18:00 UTC.

Posts to Highlight:

A curated list of Make/Core posts from this past week:

Announcements

@bph shared an update of The Developer Blogblog (versus network, site):

Current Release Cycle

WP 6.2:

  • Main landing page for the 6.2 development cycle is https://make.wordpress.org/core/6-2/.
  • Proposed schedule which:
    • proposes Feature Freeze and BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 on February 7th.
    • is asking for volunteers to join the release squad

Interested in being part of the WP 6.2 Release Squad? If yes, then in the comments of the proposed schedule post, please raise your hand for a role you’re interested in being considered for.

Component Maintainers

@sergeybiryuko shared a status report of completed work of the last week: PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8+ compatibility work of renaming reserved PHP keywords #56788 and 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. WP_Locale array property initialization #57427.

Open Floor

@hellofromtonya shared an experiment being run for improving backporting (copying / synchronizing) code from 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/ to Core: early, continuous, smaller backports throughout the development cycle. Action item: Make/Core post to share the details.

@sc0ttkclark asked for initial input (feedback) on the direction of the rebooted Fields API project and gave a brief overview of the focus: “the Settings 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. and a new modernized Fields API that isn’t tied to the Customize API” 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) improvements from the accessibility team”.

@afragen asked for VirtualBox users to test a proposed new move_dir() function which is packaged in this self-contained plugin, as part of the Rollback feature. Testing instructions will be available in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.

@ironprogrammer asked if there are plans for an early 6.2 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. @audrasjb will host the scrub on Thursday, January 12, 2023, 20:00 UTC (details are in the scrub post).

@webcommsat shared that by the end of this week, 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. Asia needs to know Core Team’s plans for 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/. tables. If you are attending and interested in leading a table, please reach out to Abha.

Props to @webcommsat for proofreading this summary.

#6-2, #core, #dev-chat, #meeting, #summary

Abha Thakor 12:25 am on January 12, 2023
Tags:   

Can you help with topics for the WordPress Developer Blog?

The tenth article has just been published on the WordPress Developer Blog! Check out A walk-through of layout classes in WordPress 6.1 and the other posts available on this new venture.  

The blogblog (versus network, site) has a content board on GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ and you can add directly to the discussions on topic ideas. You can add new ideas, help to flesh out the topics already suggested, or volunteer to be involved in writing a post. Below is the current list of topics ideas:

Before you get started, check out How to contribute and the Tips and Guidelines for Writers pages on the site. There will be more information on these pages as the blog moves out of 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..

You can ask questions and join discussions async in the #core-dev-blog 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/.. 

Monthly meetings take place every first Thursday of the month at 13:00 UTC. The next meeting will take place on February 2, 2023.

Props to @bph for co-authoring and reviewing this post.

#core-dev-blog

Abha Thakor 11:22 pm on January 11, 2023
Tags: ,   

Developer Blog – Editorial meeting: January 5, 2023

January 5, 2023 meeting

Start of the meeting in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-Developer-Blogblog (versus network, site) 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/..

Attending live during the meeting: @bph, @webcommsat, @milana_cap, @greenshady, @bcworkz, @ndiego, @psykro, @mburridge. Async updates: @marybaum

 1. Project status

Project Board on the Developer Blog repo on GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/.

Notes from the November 2022 and December 2022 Editorial meetings.

@bph update: Since the last meeting four posts have been published: Huge thank you to the contributors and their reviewers.

Authors @mburridge, @greenshady, @dsas – reviewed / edited by @milana_cap, @bph, @webcommsat, and others.

Posts in the works

Assigned, discussions in progress:

Posts in progress:

2. Approval of topics

Discussion on Topic Ideas from the discussion board.
A few of the topics in the pipeline were discussed. They are not all ready to proceed, but some have writers who are considering the topics.

The topics in the list below were agreed and ready proceed.

Topic ideas that are still looking for input and writers:

Some writers volunteered during the meeting. It was agreed to promote a call for input and writers wider and various options were discussed to encourage awareness, mentor and share learning, and increase the number of voices. Options included: Month in WordPress newsletter, a P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. blog post and cross-posting to other teams and in specific meetings, individual networks on social.

The core dev blog is still in 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., so a larger promotion /marketing campaign will be at the end of the current cycle. Post-beta stage, there could be more analysis on referrers to the core dev blog and identifying developer advocates who may be able to help promote awareness.

Work on the beta version continues, with identified issues to address with design and 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.. No date as yet for the marketing launch. GitHub repo for more information on design areas.

3. Open Floor

Discussion on the approval process for topics as it develops.

The next meeting will be on February 2, 2023, 13:00 UTC

Reviewed by @bph

#core-dev-blog, #summary

Jb Audras 10:12 pm on January 11, 2023
Tags: ,   

Early bug scrub schedule for WP 6.2

With the 6.2 cycle underway, the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team will organize a 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. scrub, specifically focused on tickets marked “early”.

It will be hosted by @audrasjb on Thursday January 12, 2023 at 20:00 UTC on 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/. team #core channel.

There are currently 8 tickets marked early in the milestone.

These “early” tickets need to be committed as soon as possible in the 6.2 development cycle, to give them enough time to be properly tested before the feature freeze on February 7, 2023. That’s why this first “early” bug scrub is planned ahead of the regular weekly bug scrubs that will be scheduled by the WP 6.2 Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads.

As the call for 6.2 Release Leads ended on January 10th, a full bug scrub schedule will probably be announced within a few days by the 6.2 Triage Leads.

#6-2, #triage

Andrei Draganescu 5:27 pm on January 11, 2023
Tags: , , , ,   

Editor chat summary: Wednesday, 11 January 2023

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor 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, on Wednesday, January 11, 2023, 14:00 UTC.

General Updates

  • Gutenberg 14.9.1 has been released
  • 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/ 15.0 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). will be released today

Async key project updates

Read the latest updates directly from the following tracking issues:

Task Coordination

@mamaduka would like some eyes on Global Styles: Don’t remove Custom CSS for users with the correct caps because the tests pass locally but not on GithubGitHub GitHub is a website that offers online implementation of git repositories that 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/.

@andraganescu has been working on various items related to Navigation List View: Introduce navigation editable tree view in the inspector controls

Open Floor

@ribaricplusplus wanted to highlight his PR for Global Styles: Save and Delete functionality for user variations to @joen ‘s issue

@hellofromtonya mentioned that Webfonts 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. architecture should be unblocked by Monday Jan 16th for giving courtesy time this week for CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers to weigh in on the API renaming from “Webfonts” to “Fonts”.

@fabiankaegy brought up @wordpress/eslint-plugin package does not support node.js 18 and will also ask in the core-js how to go about updating node support

@luehrsen raised awarness on a ticketticket Created for both bug reports and feature development on the bug tracker. Drop “local($font_family)” CSS while registering font-family in webfonts_handler and got feedback from @hellofromtonya

@bph invited people to check out the developer blog and called for contributors to topics open for publishing

If you are interested in contributing to the WordPress Developer Blogblog (versus network, site) check out How to contribute and the Tips and Guidelines for Writers.

@hellofromtonya asked that if there is a bugfix, feature, or enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ready to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. to Core, please open a TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket for it and create a PR. Instead of waiting until before Feature Freeze.

@paaljoachim opened a discussion to be had around the meeting time. Should we move it 1h later?

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

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

JuanMa Garrido 3:43 pm on January 11, 2023
Tags: , interactive-blocks, ,   

Update on the work to make building interactive blocks easier

Over the last ten months, a group of contributors has been working on a way to make it easier to build interactive blocks. These plans were first made public in the Exploration to enable better Developer and Visitor Experiences with blocks post, and the work they’ve been doing since then has been shared publicly in this GitHub repository. Additionally, @poliuk, who has been involved in this exploratory work, presented a talk sharing the group’s vision of the future of WordPress frontend at 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. Europe, held in June 2022 in Porto.  

As stated in this post from April, these are some of the questions that have been explored:

How to enable a much more powerful interactive and dynamic Visitor Experience with blocks? 
How to have a much more delightful Developer Experience when building blocks? 
How to offer a standard way to create interactive blocks so 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. developers don’t have to reinvent the wheel? 
How to ensure the block editor takes care of performance optimizations for visitors?
How to enable nice and faster page transitions with blocks? 

This new update is to share with the community that there has been progress on these areas and to announce that an initial proposal that could positively impact WordPress’ DX & UXUX User experience will be shared soon. The goal of this proposal is to create a new standard that simplifies building rich interactive web applications with WordPress using declarative and reactive programming principles.

If you can’t wait until the initial proposal gets published and are curious about the work done so far, please visit this GitHub repo. 

Here’s a list of the main areas where these contributors have been working on: 

  • WordPress Directives 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 (tracking issue) by @cbravobernal, @santosguillamot, @darerodz, @luisherranz & @czapla: An installable plugin that adds a set of basic directives and client-side transitions.
  • Directives Hydration (tracking issue) by the same contributors: This issue tracks the work done to implement this mechanism to hydrate the DOM.
  • Stress testing (tracking issue) by the same contributors: This issue tracks the work done to test the performance and resilience of the Directives Hydration mechanism.
  • Server-side rendering of directives (PR) by @bernhard-reiter: Experimental PR to use WP_HTML_Tag_Processor to transform wp- directives into markup that’s ready for client-side hydration.
  • Client-side navigation of the Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. block using directives (PR) by @luisherranz: An experiment to implement client-side transitions in the Query Loop block.
  • Replicate Navigation block using directives (PR) by @luisherranz, @santosguillamot, & @darerodz: An experiment to switch from micromodal + imperative code to declarative directives.

Stay tuned for the next update, in which they’ll explain these areas of exploration in more detail, demonstrate how they fit together, and outline the alternatives that were considered. 

Meanwhile, anyone who wants to contribute will be warmly welcomed, so if you want to join in with this work and get involved, please raise your hand in the comments section below or open a conversation in this Discussion board.

Thanks to @luisherranz, @priethor, @poliuk, @bph, @bernhard-reiter, @cbravobernal, @czapla, and @mburridge for reviewing and helping shape this post!

Special thanks to @poliuk, who wrote the initial draft of this post.

#block-developer-experience, #interactive-blocks, #interactivity-api, #visitor-experience

Paal Joachim Romdahl 7:16 pm on January 10, 2023
Tags: , , ,   

Editor Chat Agenda: 11 January 2023

Facilitator and notetaker: @andraganescu

This is the agenda for the weekly editor chat scheduled for Wednesday, January 11 2023, 03:00 PM GMT+1. 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/..

Release of Gutenberg plugin 14.9.1.

Key project updates:

Task Coordination.

Open Floor – extended edition.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • 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.

#agenda, #core-editor, #core-editor-agenda, #meeting

Bethany Chobanian Lang 5:18 pm on January 10, 2023
Tags: , , , , , , ,   

Performance Chat Summary: 10 January 2023

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

Discussion: Unbundling Performance Lab

  • @flixos90: Want to emphasize that we should decouple how we develop these features from how we distribute them, with this conversation focused on the latter. We can keep working in a mono repo to keep development overhead low no matter which approach we choose for distribution.
  • @olliejones: It seems like any attempt to figure out what 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” is might be a waste of time, as it’s up to Matt, not us
    • @flixos90: The canonical plugins topic is related but not really connected. Agreed it’s not on us to decide, but also don’t think we need to do that to determine how to unbundle Performance Lab. The ask is to distribute the features as individual plugins – whether or not they’ll become “canonical” plugins isn’t directly relevant to the unbundling.
  • @flixos90: As comment notes, we’ve considered three options so far:
    • Option 1: Keep PL as is, but additionally deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. modules as individual plugins
    • Option 2: Make PL a “wrapper” focused on central infrastructure and recommendation of individual plugins
    • Option 3: Deprecate PL completely in favor of individual plugins
  • @masteradhoc: Don’t see SQLite as something that needs to be in PL and WebP can also be standalone. How do you define if a feature should get into the plugin or be standalone? Would go for option 3 to keep everything separated and have some sort of list to keep track on what is being worked on. However, this still doesn’t solve the bigger issue – what happens if the argument is still to not merge them into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.? What will make a canonical plugin in the end? How can we really move WP further in performance?
    • @flixos90: The idea is that all modules of PL are standalone features, so option 3 would mean each module would become its own plugin. The PL plugin has a lot of benefits that we would lose if we go with this option, which is why it’s the most unfavorable to me. There are several feature plugins that weren’t merged into core – either they continue to be developed to eventually get there or they get archived.
    • @masteradhoc: In that case, think more of option 2. Wouldn’t do option 1 as it seems like duplication.
    • @flixos90: Yes, there would be duplicates, but it’s not necessarily bad. It’s the best of both wolds, similar to how Jetpack works as of today.
  • @spacedmonkey: Could a feature be both a standalone plugin and in PL?
  • @olliejones: We have one canonical plugin now, Akismet, that’s available to every WP install but not required – is that what Matt wants for performance?
    • @flixos90: Nothing would be pre-installed; let’s focus on unbundling as opposed to canonical plugins since we don’t know what those are
  • @spacedmonkey: It seems to only make sense to break off larger feature like WebP or SQLite into separate plugins
    • @masteradhoc: I wouldn’t install a plugin just to get additional Health Checks
    • @flixos90: It’s a blurry line – it would require the overhead of a discussion on every single feature to decide if it should be a standalone plugin. Would be in favor of a single consistent decision to save ourselves the overhead later. This is how feature plugins have always worked. FWIW several plugins have only ~50 installs because they’re so specific.
  • @spacedmonkey: Could have a Performance Lab module and a GH repo template for them, would help with maintenance
  • @joegrainger: If we deploy modules as individual plugins, will they have their own repos and if so will they be in the WordPress organization?
    • @flixos90: Yes, only on wp.org would there be separate repos
  • @mxbclang: Are we comfortable that keeping PL and deployingDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. separate plugins fulfills Matt’s request? We would still have a single plugin with all of these features
    • @flixos90: We’ll have to see of course, but main ask was individual plugins
    • @adamsilverstein: Not sure this really meets his requests, he very explicitly said of SQLite that we should “stop putting additional things like this into Performance Lab”
    • @flixos90: From my perspective, since Jetpack does Option 1, this should be a reasonable approach
  • @spacedmonkey: Jetpack is an example of a mono repo with multiple plugin projects: https://github.com/Automattic/jetpack/tree/trunk/projects/plugins, which is a good example of how Option 1 would work
    • @kraft: Jetpack system uses composer packages for things shared between plugins and they get called in via them, happy to answer any questions about the setup
  • @mxbclang: Option 3 is also a burden for support, since each plugin has its own support forumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations. that would need to be monitored
  • @spacedmonkey: Marketing is also an issue, where do we push people to?
    • @flixos90: Depends on the context, likely PL primarily, but individual plugins would also be available. A feature proposal post would highlight both as equal options for testing.
  • @olliejones: Option 1 lets us keep moving on development, but it carries the risk of Matt pushing back
    • @flixos90: FWIW both Options 1 and 2 carry that risk
    • @adamsilverstein: Makes me lean toward Option 2
    • @flixos90: Benefit of Option 1 is that it would continue to work as is for the people who have PL currently installed; Option 2 would require a complex migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. that users likely would not understand
    • @adamsilverstein: Good point, thinking more of the end user who hasn’t tried “feature X” yet and having a separate plugin might be a better experience
    • @flixos90: Options 1 and 2 would be have separate plugins for each module
  • @spacedmonkey: Having each functionality in its own plugin helps with testing
  • @spacedmonkey: What defines a module? Would the current Site Health checks all be together, for example? SQLite and WebP are clearly their own modules, but what about smaller things?
    • @flixos90: Great question and another thing to discuss for the future
    • @spacedmonkey: Defining how we break the plugin up helps with what option we pick – don’t want a bunch of “sub”-plugins
    • @flixos90: Yes, but this doesn’t affect which option we choose
    • @spacedmonkey: It does for Option 3
  • @olliejones: Plugin discoverability is a huge issue in today’s WP ecosystem and Option 1 helps discoverability. The categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. “canonical plugin” does seem to help with discoverability.
    • @flixos90: Fair to say that discoverability would suffer with Option 3.
    • @spacedmonkey: Marketing and support would also suffer
    • @adamsilverstein: Not sure about discoverability, if I want a SQLite feature for my site, a canonical plugin that does just that would be easier to discover than a feature within PL
    • @flixos90: Yes, but the standalone plugin would always exist with any option
  • @spacedmonkey: If there’s a standalone plugin, will anyone bother with a PL plugin? What’s the point of it?
    • @flixos90: Depends on the audience. There are people that want one feature at a time and others who want everything in one place.
  • @olliejones: Happy with Option 1 for now. Taking a step back, discoverability is a REALLY big problem for WP themes, plugins, etc. The reason I suggested working on the definition of “canonical” is that it has the potential to address that. Know that we can’t solve that problem but it’s what Matt cares about.
    • @masteradhoc: Agree, maybe next meeting could focus on how these initiatives can be moved forward
  • @spacedmonkey: Personally think that all PL functionality should be opt-in
  • @adamsilverstein: Love the idea of canonical plugins at install time, Drupal does something exactly like this with their 10-minute install
  • @flixos90: That’s how I’ve been thinking about canonical plugins, as well, with WP core providing contextual recommendations
  • @spacedmonkey: Maybe we could have a setup wizard where you opt-in to the features that you want, like Web Stories
  • @olliejones: Is there any way to get Matt’s approval of our choice, or do we have to do a bunch of work and risk it getting shot down?
    • @flixos90: We’d definitely reach out to him with a proposal once we have alignment within the team; we wouldn’t start any work before having buy-in from him
    • @olliejones: Who will do that?
    • @flixos90: Potentially, will help in figuring out how to do that
  • @flixos90: For next week, perhaps: I think are our options when it comes to the scope of how the current modules would be distributed as plugins:
    • Every module becomes its own plugin
    • Modules are grouped together based on their focus into a few “topic specific” plugins
    • Decisions are made individually, some modules become standalone while others are grouped into a topic specific plugin

Voting on an approach is now open in this GitHub comment through Friday, January 20.

Our next chat will be held on Tuesday, January 17, 2023 at 16:00 UTC in the #core-performance channel in Slack.

#core-js, #core-media, #performance, #performance-chat, #summary, #hosting-community

#core-performance, #meta

Ajit Bohra 4:10 pm on January 10, 2023
Tags: , , , ,   

Editor chat summary: Wednesday, 4 January 2023

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor 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, on Wednesday, January 04, 2023, 14:00 UTC.

General Updates

Async key project updates

Read the latest updates directly from the following tracking issues:

@ntsekouras Updates on Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.

  • Fetch terms suggestions dynamically
  • Connect scoped block variation to inserter variations
  • Moving color block support to the Post Template 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.

Task Coordination

@poena

@hellofromtonya Update on the WebFonts API

  • Status: Blocked by architectural work. (Dec 12/19)
  • Done:  The major architectural redesign (See #41481) is now merged. The new architecture is a code rewrite which has breaking changes. Some high-level details:
    • Changes data structures and publicly exposed functions/methods.
    • Includes a temporary backwards-compatible (BC) layer that throws deprecation notices to alert developers of where they need to modify their code to use the 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.. This BC layer will not be backported to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • Next:  There are 2 more architectural tasks that need to be completed to unblock the remaining bugs, performance, and feature work can continue.

@annezazu
Latest Phase 2 work update As expected, a number of PRs are now stalled due to folks taking time off. This is a wonderful and expected pause in the work! Some brief things to note:

@carlosgprim Update from the mobile team
Recently fixed/improved

Open Floor

@wildworks
[New Block] Add post time to read block #43403 I believe the code base is almost complete, but I would like your advice on ideas for moving forward with this PR or if it is releasable.”

@bph

The  WordPress 6.2 Planning Schedule Proposal is out and there are open slots on the release squad.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Read complete transcript

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

Jb Audras 8:12 am on January 10, 2023
Tags: , ,   

A Week in Core – January 9, 2022

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 January 2 and January 9, 2022.

  • 16 commits
  • 19 contributors
  • 27 tickets created
  • 3 tickets reopened
  • 34 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 and/or focus.

Code changes

Buyild/Tests Tools

  • Bring some consistency to mocking HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. requests in unit tests – #56793, #56792
  • Use correct variable in _fake_download_url_non_200_response_code() – #56793

Bundled Themes

  • Twenty Twenty-Three: Fix incorrect gradient values in Aubergine theme – #57245

Code Modernization

  • Rename parameters that use reserved keywords in phpunit/includes/spy-rest-server.php – #56788
  • Rename parameters that use reserved keywords in phpunit/includes/utils.php – #56788
  • Rename parameters that use reserved keywords in phpunit/tests/block-supports/elements.php – #56788
  • Rename parameters that use reserved keywords in phpunit/tests/compat/mbStrlen.php – #56788
  • Rename parameters that use reserved keywords in phpunit/tests/cron.php – #56788, #56788
  • Rename parameters that use reserved keywords in phpunit/tests/customize/manager.php – #56788

Coding Standards

  • Correct alignment in wp-includes/option.php – #56791
  • Fix WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards. May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. issues in phpunit/tests/pluggable/wpMail.php – #28407

Mail

  • Allow custom attachment filenames in wp_mail() – #28407

Networks and Sites

  • Mark required fields as such in New User Form – #38460

Pings/Trackbacks

  • Remove a mention of the “Page” post type from the Discussion 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. box – #57429, #11346

Query

  • Stop priming posts twice in WP_Query – #57373

Props

Thanks to the 19 people who contributed to WordPress Core on Trac last week: @sergeybiryukov (7), @jrf (7), @aristath (7), @poena (7), @justinahinon (7), @sabernhardt (3), @flixos90 (2), @johnjamesjacoby (1), @jackreichert (1), @syntaxart (1), @swissspidy (1), @ritteshpatel (1), @wildworks (1), @peterwilsoncc (1), @spacedmonkey (1), @virgar (1), @audrasjb (1), @jeremyfelt (1), and @afercia (1).

Core committers: @sergeybiryukov (11), @audrasjb (3), @spacedmonkey (1), and @johnjamesjacoby (1).

#6-2, #core, #week-in-core