Paal Joachim Romdahl 7:42 am on December 7, 2021
Tags: core-editor ( 451 ), core-editor-summary ( 95 ), gutenberg ( 293 ), meeting notes ( 144 ), summary

Editor chat summary: 1 December, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, December 1 2021, 03:00 PM GMT+1 in Slack. Moderated by @jorgefilipecosta.

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 releases

What’s new in Gutenberg 12.0.0.
Gutenberg 12.1 RC1 released.
Parts of 12.0 and 12.1 were backported into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and will be part of WP 5.9.

WordPress 5.9

Beta 1 was released 30 November.
Help is needed: tracking issue for development notes for WP 5.9. Contact @mkaz if you have any questions about writing a development note.
Check out the various issues on the WordPress 5.9 Must-Haves project board.

Key project updates

Based on the scope for Site Editing projects.

Template Editor

@paaljoachim

@get_dave

All of the “Must Have” items for Nav block were merged in time for WP 5.9 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.
We now switch focus to resolving the [Type] Bug issues.
Please do pop into #feature-navigation-block-editor on 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/. if you have a question or wish to contribute.
Feel free to raise an Issue to report a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.. Be sure to label it with the Block: Navigation label.
Navigation Block Tracking issue.

Global Styling

@jorgefilipecosta

It is now possible to edit all the default, theme and user color palettes.
Edit gradient palette.
Transparency color support on all global style elements.
Multiple UIUI User interface enhancements. E.g. color picker positioning mechanism, border, margins etc.
Bug fixed: when applying some presets by value instead of slug (class or var).
Added opt-in mechanism so themes can provide palettes and completely disable the default palettes.
Themes now has a flag that allows future design tools to be enabled by default. This will allow an user of the specific theme to take advantage of future enhancements without needing to update the theme.

Patterns

@jorgefilipecosta

Automatically load patterns located in the theme’s /patterns subdirectory. It would simplify the registration of the pattern as one would not need to call any function to register a pattern.

Mobile Team

@Antonis Lilis

Shipped:
Turned on auto-migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of v1 Gallery blocks to v2 format when edited
Fixed:
An issue where the font size value did not update
An issue with the preformatted block background color
RN iOSiOS The operating system used on iPhones and iPads. E2E tests failure related to environment not available
An iOS scroll update issue when typing in RichText component
Undo/redo functionality in links when applying text format
Other:
Updated configuration to use tarball instead of git tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) for reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/.-native-editor forked dependencies
In Progress:
Upgrade to React Native v0.66.
Finalizing GSS Font size, line height and selected text colors.

Components Team

@mciampini

Shipped:
We merged a new ConfirmDialog component intended to serve as a replacement for the editor’s current uses of the native confirm function, providing a more cohesive UI and addressing some browser compatibility concerns.
Fixed:
The DateTimePicker component now correctly handles values for hours when “PM” is selected in the component’s is12Hour mode.
In Progress:
We’re working on improved and more consistent support for larger variations of several input components used in the typography panel. These variations are mostly implemented with custom style overrides currently, and we’d like to provide a more declarative and consistent 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. for them.

Task Coordination

@paaljoachim

Highlighting:
Site Editor list screen issues.
Allow users to edit the “default layout” in the Global Styles panel.
A PR that fixes the Image Caption alignment with smaller images.

There were no other tasks shared during the Task Coordination.

Open Floor

@Fabio Blanco

Fabio is trying to follow and learn about Gutenberg development.

@jorgefilipecosta

For code contributions.
Block Editor Handbook: Getting Started With Code Contribution
After setup is ready feel free to fix some Gutenberg issues. Ask in the #core-editor channel on Slack if you need any help.

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

Justin Ahinon 7:15 am on December 1, 2021
Tags: core-media ( 48 ), meeting ( 86 ), performance ( 24 ), performance-chat ( 11 ), summary

Performance team meeting summary – November, 30 2021

This is the agenda for the meeting. You can read the logs here on Slack.

Focus groups updates

Images

@adamsilverstein gave a great update on the progress of the focus. First, all issues and ideas related to focus will be tracked in this GitHub project. This will facilitate asynchronous contributions and discussions. The top priority issue on the project is this one, for creating a WebP module, and port the code to the repository.

On top of that, the focus meeting last Thursday was a success and the team is planning to hold a next one. Keep an eye on the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site) and the #core-media 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/. to keep up with the agenda.

There were also several discussions about the main projects of the focus: WebP by default in WordPress Core and the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of existing images into the WebP format. Here are the links to the discussion pieces on Slack:

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

Since most of the people in this focus are deeply involved in the next release, there are no major updates at the moment.

Measurement

For this focus, there were some discussions about starting a dedicated side conversation (see thread). Currently, the team is still thinking about the best form for this conversation, chat or video call. If you have any opinions, feel free to leave a comment in the thread linked above or on this post.

Performance features development coordination

There is currently this issue on the 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/ repository regarding the code infrastructure of the performance modules. This step is very important to move forward, so feel free to leave a comment or feedback on the issue.

Open Floor

Jérôme Vieilledent (@lolautruche on Slack) mentioned before the meeting that Blackfire and Platform.sh are willing to support the WordPress Performance team initiative. Blackfire might be interested in donating an account to the 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/ organization for the team’s purposes. See Slack discussion here.

#meeting, #performance, #performance-chat, #summary

David Smith 9:01 am on November 30, 2021
Tags: core-editor ( 451 ), core-editor-summary ( 95 ), summary

Editor Chat Summary: 24th November 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-11-24 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 releases

Gutenberg 12.0.0 was released (after the meeting) – thanks to @welcher for leading this one.
Highlights post will be released on Make blogblog (versus network, site) soon.

WordPress 5.9 status updates

The release schedule for WordPress 5.9 has been revised. It will now land on 25th January 2022.
This is primarily due to features relating to FSE needing additional work in order to land a complete experience and the inability to ship these in isolation from one another (if you’d like details you should read @hellofromtonya’s post which does a great job of explaining things).
According to @noisysocks (Editor Tech Lead) we now have until the 26th November (that date as now passed) to land any Gutenberg PRs that we want in WordPress 5.9 Beta 1.
Here are the list of WP 5.9 pending issues and blockers.
Please remember to add the Backport to WP Beta/RC 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/ label on any PRs that need to land in WP 5.9.
@mkaz reminded us about documentation needs. Please take the list of the larger project board and this dev note tracking issue.

Updates based on the scope for Site Editing projects

Updates were requested for the key projects:

Native Mobile Team

@antonisme provided the update:

Shipped

Added Clipboard Link Suggestion to Image blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. and Buttons block
Added auto opening of media upload options to new Gallery block

Fixes:

Only set font sizes for block based themes
Reverted erroneous native editor package version bumps

In Progress:

Upgrade to ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native v0.66.
Finalizing GSS Font size, line height and selected text colors.

@get_dave provided the update:

A list of “Must Haves” for the Navigation block for WP 5.9 were published.
We’re tracking these items on the main 5.9 overview issue.
Navigation Areas (including the block itself) are not going to be in 5.9. In fact they are now deprecated due to concerns and lack of community consensus around the UXUX User experience.
Reusable Navigations (via the wp_navigation Custom Post) will be shipping in 5.9.
The final experience we are targeting for the Nav block for 5.9 is outlined here.
We recognise this is not perfect and we fully intend to iterate and improve upon this process in WordPress 6.0. However, our priority is to land a stable experience in 5.9.
We’re seeking folks to help review the final PRs prior to the 26th deadline.

Components Packages

@mciampini provided an update:

Shipped

ToolsPanel has an improved README and Storybook stories illustrating its usage. This component is used to group related sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. controls, grouping them and providing a standard UIUI User interface for showing and hiding them.
We’ve added an example for adding a chevron icon in the Item component for certain types of navigation used in Styles.

Fixes:

The ZStack component’s offset prop now supports RTL languages properly.

In Progress:

We’re working on improved and more consistent support for larger variations of several input components used in the typography panel. These variations are mostly implemented with custom style overrides currently, and we’d like to provide a more declarative and consistent 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. for them.
We’re improving support for the vertical orientation and RTL languages in the Divider component.

Templates

@annezazu stepped in to provide an update based on her recent knowledge:

Work has been done to merge the initial template list page for the site editor.
This creates a scaled down browsing experience that allows you to see your full list of templates and template parts along with the ability to edit your homepage.
Work remains though to refine the experience with blockers and more shared in this overview issue.

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@annezazu:

Update on my end — lots of testing/triaging for 5.9 in GitHub, helped ship the recent /News post highlighting a 5.9 video a crew of us worked on.
Continued amplifying & responding to the latest FSE outreach call for testing.
Shared some personal thoughts on why I voted to delay 5.9, and nearly done with draft of Styles user doc (needed for the welcome guide).
After this next week, I’ll have far more time to focus on documentation and testing efforts so plan to continue to shift attention there (have a presentation due this week about 5.9).

@get_dave:

Been focused on the “Must Haves” for 5.9. Particularly the Navigation block.
I would really appreciate reviews and testing on this PR which is trying to implement a sensible default fallback for the Nav block when it’s rendered on the front end of the site.

@zieladam:

I’m helping with making the navigation block ready.
Right now working on giving new menus a name in https://github.com/WordPress/gutenberg/pull/36760.
I just noticed a few bugs stemming from the complexity, so I want to follow-up with a 2-in-1 PR: simplification and bugfixes.

Open Floor

Get involved in the latest call for testing

@annezazu – I just want to deeply encourage folks to get involved in the latest call for testing: https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/.
It goes over some of the newest features coming to 5.9 and it goes a long way to have folks running through these flows!
You’ll also get a lovely Test contributor badge on your profile for participating as a thank you and recognition of your efforts.

Alan Smodic asked for some insight or guidance on some issues that he and his team have flagged and added comments to. Wondering if these have ever been talked about before or how best we can help to potentially solve.
Publish datepicker time zone is server time instead of user time: #29306.
DateTimePicker Time Zone Selection: #31522.
Timepicker time resets when using AM/PM toggle: #29720.
@get_dave suggested getting @talldanwp to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. in the bi-weekly triage meetings.
@talldanwp suggested following up post 5.9.
@mciampini said he will flag it to the rest of the components folks,

Normalize Github labels to a single “[Type] Documentation” label

@mkaz informed us that there is a label in GitHub for “developer docs”, which is intended for issues specific to the developer documentation site.
He’s not sure the distinction is necessary and the additional label is confusing, as many docs are being labeled with one of the two labels.
Marcus proposed we remove the “developer docs” label and make sure any issues and PRs that have that label also have the “[Type] Documentation” label.
Folks in the meeting agreed with this proposal.

Call for input: can we run DB upgrade scripts as part of Gutenberg upgrade process?

@get_dave raised this Issue whereby meta tags were added to the post content on “Paste”.
The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. issue has now been fixed but contributors are asking whether Gutenberg can add a one time operation on upgrade which runs a DB cleanup operation on all posts to remove this erroneous tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.).
I’d like to understand whether there is any prior art for achieving such a thing in Gutenberg – any input from @youknowriad or other Core folks would be appreciated.

Wrap up

Thanks to everyone who attended the meeting!

#core-editor, #core-editor-summary, #summary

Dan Farrow 3:38 pm on November 25, 2021
Tags: core-css ( 187 ), summary

CSS Chat Summary: 18 November 2021

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

Announcements & housekeeping

The next meeting will be on Thursday 25 November at 17:00 UTC. Please add your name to the Meeting Facilitator schedule document if you would like to contribute by facilitating this or any future meetings
@notlaura suggested breaking for holidays after December 16th and starting up again January 6th 2022
@khoipro pointed out that the new meeting time is midnight in APAC which led to a short discussion about meeting times. The conclusion was that we can revisit the meeting time again in the future

CSSCSS Cascading Style Sheets. Custom Properties (#49930)

@joyously observed that themes which override custom admin properties could break backwards compatibility with older versions of WordPress, as the custom properties they override will not be defined by the adminadmin (and super admin) CSS. She gave the example of the recent addition of a custom property for admin bar height, with a fallback of 0 to indicate that the admin bar is not shown. On sites running older versions of WordPress the custom property would not be defined, so the fallback of 0 would be used by the theme. This is something we could possibly address with a PostCSS script

Thanks everybody!

#core-css, #summary

Tonya Mork 9:19 pm on November 24, 2021
Tags: 5-9-release-leads, 5.9 ( 59 ), dev chat ( 494 ), summary

Dev Chat Summary for November 24, 2021

@hellofromTonya led the weekly meeting at 20:00 UTC. Here is the meeting agenda.

Link to this <devchat> in #core on 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/..

Notable News and blogblog (versus network, site) posts

Team Reps

@marybaum will be a new Core Team Rep for 2022.
Thanks to @francina for serving in this role!
@audrasjb will continue in this role until another team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. is found.

Interested in being a Core Team Rep? Reach out to @audrasjb.

WordPress 5.9

Editor update November 19, 2021
WordPress 5.9 Revised Release Schedule
A Look at WordPress 5.9 – Highly recommended watching and sharing!

@jeffpaul asked if there are any 5.9 blockers that are in specific need of help and asked what type of help they need (engineering, design, testing, etc).
@hellofromTonya posted an update on 5.9 blockers and scheduling. Design help is needed for Global styles & Design tools.
There is an open Call for Testing for Safari.
Everyone is invited to help wherever possible.
The release squad is keeping a daily close eye on progress, needs, and any blockers that might surface. Discussions and updates are centralized in the #5-9-release-leads channel on Slack.

Component Team Updates

Build/Test Tools

@sergeybiryukov gave an update:

Dependabot scanning is now configured for GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Actions. This eliminates the need to manually check all GitHub Actions used within workflow files for updates. See ticketticket Created for both bug reports and feature development on the bug tracker. #54503 for more details.
NodeJS is pinned to the 14.x version in the .nvmrc file to ensure contributors are able to contribute without issue until compatibility with version 16.x can be confirmed in both trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. and 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/ repository on GitHub. See ticket #54502 for more details.
Some PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher warnings from stdClass::__invoke() callback mocks were fixed in 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/. tests. See ticket #53844 for more details.
The timeout for GitHub Actions jobs was lowered so runaway or stalled processes don’t risk running for the default timeout duration of six hours. See ticket #53363 for more details.

Date/Time, General, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks

@sergeybiryukov shared: No major news this week

Open Floor

@afragen asked for feedback on the Plugin Dependencies project for WordPress 6.0. Reach out to @peterwilsoncc if you wish to have editing access.
@jeffpaul asked how we are progressing on the Pre Beta 1 tasks and asked if there are any items that need help.
@hellofromTonya replied that there are some 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. that need to be compiled and published.
@audrasjb has been marking tickets that need Dev notes.
@mkaz noted that documentation for WordPress 5.9 could use some help and posted a link to the requirements. Contributors are invited to reach out to @mkaz with any questions.
@jeffpaul is working on the WordPress 5.9 HelpHub page.
@abhanonstopnewsuk noted that the latest checks for the About and Help page were carried out on Monday November 22, 2021. The next check is on Monday November 29, 2021 at 20:30 UTC.
@audrasjb will be leading a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub on November 25, 2021 at 21:00 UTC. See the 5.9 Bug Scrub schedule.
With Thanksgiving taking place in the US on November 25, 2021, @hellofromTonya thanked the community for all contributions.

Props to @costdev for writing the devchat summary.

#5-9, #dev-chat, #summary

Justin Ahinon 9:42 am on November 24, 2021
Tags: meeting ( 86 ), performance ( 24 ), performance-chat ( 11 ), summary

Performance team meeting summary – November, 23 2021

This is the agenda for the meeting. You can read the logs here on Slack.

Focus group projects discussion

Image focus

@adamsilverstein shared an update for the Image focus. The group plans to go through the ideas in this document to discuss the impact, level of difficulty, etc. and generally prioritize our work. Also, in addition to taking some time during the regular media meeting, the group members are proposing a regular second “performance image focus” meeting in a friendly timezone to APEC contributors. The first try for that meeting will be November 25, 2021, at 02:00 UTC.

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. focus

The JavaScript focus update was shared by @gziolo. The team is still collecting ideas for issues to work on in this document. They also discussed during the last week during #core-js office hours how to bring ES Modules and Import Maps to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. The next office hour, focused on issues prioritization is planned on next Tuesday.

Object caching focus

@spacedmonkey put together a list of related tickets he is willing to work on.

Measurement focus

@wp-source stated that the team has some interesting projects ideas. Now, there is a need for some short and regular sync chat for the focus group members to discuss this project. If you are interested in attending one of these chats, please share your interest in this thread on Slack.

Performance features development coordination

@flixos90 shared some insights about the coordination repository proposal. Here are the main outcomes of these:

WordPress has historically relied on feature plugins to test future WordPress core features “in the wild”. The proposal here is to follow that approach, however by creating modules in a single “performance features wrapper 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”.
By centralizing these efforts in 1 plugin instead of x plugins, the hope is to significantly reduce maintenance, encourage cross-collaboration between different performance efforts, and have a centralized place for any performance-related conversations.
For example, a central 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/ repository could be used to open issues with new performance enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ideas, discuss them etc, even if they don’t right away lead to a new performance module.
A single wrapper plugin also can help from an adoption perspective, essentially interested users can install the plugin once and then will get access to any new performance features as soon as they are added – they can then enable whatever they are interested in to try out.

There have been several discussions about where this repository should be created. The main locations being the Gutenberg repository, and under the GitHub WordPress organization.

After a vote, the repository has been created under the GitHub WordPress organization, and you can find it here.

#meeting, #performance, #performance-chat, #summary

Paal Joachim Romdahl 10:41 pm on November 18, 2021
Tags: core-editor ( 451 ), core-editor-summary ( 95 ), gutenberg ( 293 ), meeting notes ( 144 ), summary

Editor chat summary: 17 November, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, November 17 2021, 04:00 PM GMT+1. in Slack. Moderated by @paaljoachim.

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 releases

Gutenberg 11.9.1 and Gutenberg 12.0 RC were both released on the 17 November.

WordPress 5.9

WordPress 5.9 Beta 1 delayed
WordPress 5.9 roadmap and priorities.

@mkaz and @mamaduka

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/ tracking project: Documentation for WP 5.9 release and the Dev Notes Tracking Issue.
Reminder: Please pick up an issue or two from the WP 5.9 Must-Haves board.
Overview of WP 5.9 pending issues and blockers.