Bug Scrub Schedule for 5.9

With 5.9 well underway, we’re ready to schedule the 5.9 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 sessions. These 5.9 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Scrubs:

Hosted by @audrasjb

Hosted by @chaion07 (APAC-friendly)

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. Scrubs:

Focus: issues reported from the previous beta.

  • TBD

RC Scrubs:

Focus: issues reported from the previous RC

  • TBD

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

The above 5.9 scheduled bug scrubs are separate and in addition.

For your reference, here are some of the recurring sessions:

  • Twenty Twenty-Two Triage: Every Monday 15:00 UTC in the #core-themes channel.
  • 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/ Design Triage: Every Tuesday 16:00 UTC in the #design channel.
  • 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) Scrub: Every Friday 15:00 UTC in the #accessibility channel.
  • Testing Scrub: Every Friday 13:15 UTC in the #core-test channel.
  • CSSCSS Cascading Style Sheets. Scrub: First Thursday of every month 20:00 UTC in the #core-css channel.
  • Upgrade/Install Component: Every Tuesday at 17:00 UTC in the #core-auto-update channel.
  • Help/About Component: Every Monday, 20:30 UTC in the #core channel.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at anytime? Yes, you can!

How? PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @audrasjb or @chaion07 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/. and let us know the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 5.9-focused? Awesome! We’ll add it to the schedule here. You’ll get well deserved props in the weekly Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 5.9 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 5.9 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @audrasjb or @chaion07 on slack.

Thanks @jeffpaul for proof-reading.

#5-9, #bug-scrub

X-post: Block-based Themes Meeting Agenda: December 8, 2021

X-post from +make.wordpress.org/themes: Block-based Themes Meeting Agenda: December 8, 2021

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

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

A Week in Core – December 6, 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 November 29 and December 6, 2021.

  • 66 commits
  • 62 contributors
  • 62 tickets created
  • 16 tickets reopened
  • 51 tickets closed

The Core team is currently working on the next major release, WordPress 5.9, and the beta 1 was released last week 🛠

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

Administration

  • For blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes, link to Site Editor interface instead of CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. in Dashboard’s welcome panel and Themes interface – #54460

Build/Test Tools

  • Remove the replace:emoji-banner-text Grunt task – #44632, #44306, #53363
  • Revert ignore prop change in [52272]#54506
  • Fix typo in a WP_Test_REST_Posts_Controller test method name – #53363
  • Rename classes in phpunit/tests/block-supports/ per the naming conventions – #53363
  • Rename classes in block template tests per the naming conventions – #53363
  • Replace assertEquals() with assertSame() in block template tests – #53364, #53363, #54335
  • Update WP_REST_Global_Styles_Controller_Test “Custom Styles” string after [52280]#54518

Bundled Themes

  • Twenty Fourteen: Adjust capability queries when using version before WordPress 5.9-alpha – #16841
  • Twenty Twenty-Two: Sync updates from 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/#54318
  • Twenty Twenty: Restore Editor post title styles after 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/ 11.4.0 updates – #54056

Coding Standards

  • Break the $path reference after a foreach 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. in block_editor_rest_api_preload()#54558
  • Address a few coding standards issues after [52312] – #54558

Docs

  • Add missing @param to wp_set_unique_slug_on_create_template_part()#53399
  • Add missing @since 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.) to WP_Theme_JSON_Schema functions – #53399, #54336
  • Add missing summary for WP_Theme_JSON_Resolver::get_merged_data()#53399
  • Docblockdocblock (phpdoc, xref, inline docs) corrections in _disable_block_editor_for_navigation_post_type()#53399
  • Docblock typo correction in WP_Theme_JSON_Schema#53399
  • Fix typo in some get_edit_term_link() test DocBlocks – #50225, #53399
  • Further update some @since notes in WP_Theme_JSON methods for clarity – #53399, #54336
  • Misc Docblock corrections in duotone.php file – #53399
  • Miscellaneous Docblock corrections for block-template-utils.php file – #53399
  • Miscellaneous Docblock corrections in several /block-supports files – #53399
  • Replace @since 5.9 with @since 5.9.0 in block-template-utils.php#53399
  • Some documentation improvements for WP_Theme_JSON and WP_Theme_JSON_Resolver classes: – #53399, #54336
  • Use a duplicate hook reference for theme_file_path in WP_Theme::get_file_path()#51506, #53399
  • Various docblock corrections – #53399

Editor

  • Allow child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/. PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher templates to take precedence over parent theme block templates – #54515
  • Allow theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. to take precedence in setting the root level element’s reset margin value – #54550
  • Avoid undefined index notices in the Template Parts Editor – #54558
  • Avoid a JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. console error on the Navigation block view – #54456
  • Do not translate the title of “Custom Styles” specific posts – #54518
  • Enable incomplete unit tests in Tests_Block_Template_Utils:: test_get_block_template_from_file()#54551
  • Hide visibility and status settings for wp_navigation post type – #54407
  • Remove Navigation Areas – #54506
  • Resolve template request ?_wp-find-template=true for new posts and pages – #54553
  • Update wordpress packages – #54487
  • Update wordpress packages – #54487
  • Site Editor: Add site export 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/. endpoint – #54448
  • Restore block PHP to canonical version in wordpress/block-library – #54506
  • Update wordpress packages – #54487

External Libraries

  • Further fix jQuery deprecations in WordPress core – #51519

Feeds

  • Remove reference to wp-atom.php in Atom feeds xml:base attribute – #47955

Formatting

  • Handle non-scalar types passed to sanitize_key()#54160

General

  • Add MariaDB in the readme.html requirements – #41490

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. 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.

  • Fix classname WpOrg\Requests\Proxy\Http in WP_Http::request()#54562
  • Revert changeset [52244] – #54562, #54504
  • Revert changeset [52315] – #54562, #54504

Internationalization

  • Remove redundant default text domain parameter in some __() calls – #53359

KSES

  • Accept port number in PDF upload paths – #54261
  • Allow attributes to be restricted via callbacks – #54261
  • Use the polyfilled PHP 8 string functions in _wp_kses_allow_pdf_objects()#54261

Media

  • Featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. modal loads only selected image when infinite scroll is disabled – #53765
  • Fix TypeError and improve wp_exif_frac2dec() to only return int or float#54385
  • Replace tests/phpunit/data/images/sugar-mountain.jpg test image – #54385
  • Use infiniteScrolling global setting in js/media/controllers/featured-image.js and js/media/controllers/replace-image.js#53765

Options, 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. APIs

  • Improve error handling in sanitize_option()#53986

Plugins

  • Correct the documented allowable types for to the $callback parameter of various hook related functions – #54440

REST API

  • Ensure that the rest_after_insert_ action is executed in the templates controller – #54520
  • Fire wp_after_insert_post later in new post object endpoints – #54536
  • Replace hardcoded wp/v2/ preloaded paths – #54536
  • Use global transients for URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org details endpoint – #54499

Upgrade/Install

  • Check that WordPress is installed before scheduling cleanup of the temp-backup directory – #51857
  • Make some adjustments to the move_dir() function: – #54166, #51857

Props

Thanks to the 62 people who contributed to WordPress Core on Trac last week: @peterwilsoncc (8), @costdev (8), @hellofromTonya (5), @spacedmonkey (5), @SergeyBiryukov (4), @audrasjb (3), @desrosj (3), @poena (3), @noisysocks (3), @bernhard-reiter (3), @dd32 (3), @mukesh27 (3), @zieladam (3), @sabernhardt (3), @antonvlasenko (3), @get_dave (2), @swissspidy (2), @malthert (2), @TobiasBg (2), @youknowriad (2), @talldanwp (2), @ramonopoly (2), @adamsilverstein (1), @tobiasbg (1), @kjellr (1), @onemaggie (1), @hellofromtonya (1), @jameskoster (1), @matveb (1), @stevegs (1), @sergeybiryukov (1), @hilayt24 (1), @mamaduka (1), @oandregal (1), @praem90 (1), @shireling (1), @jrf (1), @mai21 (1), @dlh (1), @pbiron (1), @szaqal21 (1), @wpnomad (1), @johnbillion (1), @alexeydemidov (1), @kafleg (1), @Boniu91 (1), @ocean90 (1), @Pento (1), @xknown (1), @iCaleb (1), @mkaz (1), @afragen (1), @toro_unit (1), @dariak (1), @joedolson (1), @Mamaduka (1), @walbo (1), @chaion07 (1), @Clorith (1), @presskopp (1), @promz (1), and @tw2113 (1).

Congrats and welcome to our 2 new contributors of the week: @wpnomad and @alexeydemidov ♥️

Core committers: @sergeybiryukov (19), @audrasjb (18), @hellofromtonya (15), @noisysocks (4), @peterwilsoncc (4), @spacedmonkey (3), @johnbillion (2), and @jffng (1).

#5-9, #core, #week-in-core

Editor Chat Agenda: 8 December 2021

Facilitator and notetaker: @fabiankaegy

This is the agenda for the weekly editor chat scheduled for Wednesday, December 8 2021, 03:00 PM CET.

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

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

Performance Chat Agenda: December 7, 2021

Here is the agenda for this week’s performance team meeting to occur on December 7, 2021, at 16:00 UTC.

Focus group projects discussion

  • Progress check for the Object Caching group
  • Progress check for the 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/. group

Performance features development coordination

  • A couple of PRs have been merged in the performance 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 repository:
  • There are also some PRs that require attention:

Open Floor

Blackfire and Platform.sh are willing to support the WordPress Performance team initiative (see 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/. discussion here). What are your thoughts about this?


This meeting happens in the #performance channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Dev chat summary, December 1, 2021

The agenda followed for the meeting.

The meeting was led by @marybaum and summary written by @webcommsat.

The full meeting starts at this link in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel

1. Welcome

2. Announcements

WordPress Beta 1 is out (30 November 2021)

3. Useful posts

4. Update on journey to 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. 2

@hellofromtonya: Beta 2 is planned for next week, 7 December 2021.

Until that time, focus shifts towards triaging, investigating, and fixing issues found in Beta 1 or just prior to it.

Issues

There are 4 issues identified during the release party and after which need contributors to help test, share feedback, investigate, and resolve:

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/

Work continues on bugs in Gutenberg too though currently not seeing blockers and progress on the list of important is proceeding well.

How can you help?

Test, Test, Test. Give feedback through a test report that shares your findings, even if it’s “can’t reproduce”.

And thank you to all contributors. Your contributions help to make WordPress.

@costdev: For test reports, you can use this template (screencast optional).

For test reports, you can use this template (screencast optional).

Just a note that the test report template is also very useful for including in the original description in a ticketticket Created for both bug reports and feature development on the bug tracker. when you’re reporting an issue.

Letting us know the environment that the issue occurs on lets us:

  • Try to reproduce using that environment
  • Try to reproduce using a similar environment
  • Try to reproduce in totally different environments

@marybaum: Thanks @hellofromtonya and @costdev. For our #Marketing and other observers, this kind of testing doesn’t require any code skill.

5. Component maintainers update

About / Help page

@webcommsat: With the beta 1, we postponed our weekly catchup to this Friday 3 December 2021, 19:00 UTC. In addition, there will be a 10 minute drop-in, facilitated by @marybaum from 18:50 UTC for those coming to shadow, observers, or new people from marketing. We will look further at the designs from @critterverse and other items on the About page and its associated items, and the start of the social media collaborations. Please join us if you can and look at the initial design draft on the ticket.

If anyone has a particular aspect to highlight for Friday, please let @marybaum and @ abhanonstopnews (on Slack) know.

More on how you can help contribute to social media promotions for the 5.9 release on the marketing blog. Everyone is welcome to join the marketing meeting next week, Wednesday 8 December 2021, at 14:00 UTC, to start exploring the social media posts too.

6. Open Floor

Q. A question asked in Marketing today, if someone finds an error on beta 1, is there a cut off for when they can report it?
A: There is no cut-off. They can report it when/ if something is found.

No other items were raised.

#5-9, #dev-chat

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

Dev chat agenda for December 1, 2021

Announcements

The WordPress 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 has landed, after a lot of very hard work by a lot of very dedicated contributors. Please download and test! Also, in the beta period, work pivots to focus only on bugs that have shown up since feature freeze on November 8.

WordPress 5.8.2 is also live, and you should update. Minor releases usually fix bugs and 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. vulnerabilities.

Blogblog (versus network, site) posts of note

@annezazu has published this guide to testing the FSE features.

This Editor Chat Summary from @get_dave is a good place to find the latest on the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor.

@audrasjb has the latest issue of A Week in Core.

And remember that we’re on a revised release schedule.

Got other posts that should get the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team’s attention? Please add them in the comments.

Upcoming releases

The current release is version 5.9, and we are now in beta. There is much to discuss.

Component Maintainers

If you maintain a component and need help with beta fixes or other blockers as the 5.9 release moves forward, please plan to join the chat and update the group.

Open Floor

Add your topic to the comments, and enjoy priority for your topic at the beginning of Open Floor.

See you Wednesday at 20:00 UTC!

#agenda, #core, #dev-chat

Editor Chat Agenda: 1 December 2021

Facilitator and notetaker: @jorgefilipecosta

This is the agenda for the weekly editor chat scheduled for Wednesday, December 1 2021, 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/..

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

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

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:

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:

Templates

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

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:

@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

  • 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