Agenda, Dev Chat, Wednesday May 22, 2024

The next WordPress Developers Chat will take place on  Wednesday May 22, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.

Announcements

The scheduled date for WordPress 6.6 Beta 1 is June 4, which is less than 2 weeks away. From this point on, core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. will focus on testing and fixing bugs discovered during 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. testing. Begin writing 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, and 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. and the About page (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/. archive, ZIP download).

@ellatrix recently announced that the last 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/ release to go into WP 6.6 will have an 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). next Friday, May 31.

Forthcoming releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.6

We are currently in the WordPress 6.6 release cycle. See the Roadmap Post for details about what is planned for this release.

Next maintenance release: 6.5.4

@jorbin requested that we discuss the potential of doing a 6.5.4 release to accommodate #61269.

Next Gutenberg release: 18.4

Gutenberg 18.4 is scheduled for release on May 22 and includes these issues.

Discussions

With the Beta 1 deadline quickly approaching, we’ll use the discussion time to check in on priority items for this release. Review the list of Editor Updates section of this agenda for a list of updates of several key features related to this release.

Highlighted posts

Editor updates

Props to @mikachan for putting together a list of editor related updates.

Get involved

Updates

Tickets for assistance

Tickets for 6.6 will be prioritized.

Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting if there are any questions or you will be async.

@vcanales mentioned the following issues in the WordPress 6.6 Editor Tasks board that are up for grabs for developers:

@dmsnell requested that we highlight the following issues:

  • #61009 allows storing the proposed “Bits” syntax, making it possible for experimentation inside Gutenberg.
  • #61052 allows storing custom data attributes containing dashes, which is what the Interactivity 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. relies on.

Open floor

Items for this can be shared in the comments.

Props to @jeffpaul for reviewing.

#agenda, #core, #dev-chat

Performance Chat Agenda: 21 May 2024

Here is the agenda for this week’s performance team meeting scheduled for May 21, 2024 at 15:00 UTC.

  • Announcements
    • Welcome to our new members of #core-performance
    • Performance lab 3.1.0 released yesterday
    • Request for feedback on ideas to improve the Performance Team site. See this issue for discussion
    • Confirmation of the 3.2.0 release date moving to June 3 due to 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 travel
  • Priority items
    • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
      • Current release (6.6)
      • Future release
    • Performance Lab 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 (and other performance plugins) including:
      • Auto-Sizes for Lazy-Loaded Images
      • Embed Optimizer
      • Fetchpriority
      • Image Placeholders
      • Modern Image Formats
      • Optimization Detective
      • Performant Translations
      • Speculative Loading
    • Active priority projects
      • Improve template loading
      • INP research opportunities
      • Improving the calculation of image size attributes
      • Optimized autoloaded options
  • Open floor
    • Frequency of a Performance Lab plugin focused 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

If you have any topics you’d like to add to this agenda, please add them in the comments below.


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

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

Agenda, Dev Chat, Wednesday May 15, 2024

The next WordPress Developers Chat will take place on  Wednesday May 15, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.

Announcements

A reminder that the WordPress 6.6 roadmap has been published. Please also read and leave feedback on the Server to client data sharing for Script Modules proposal. Feel free to leave feedback either during Dev Chat or on the proposal post.

Forthcoming releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.6

We are currently in the WordPress 6.6 release cycle.

Next 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/ release: 18.4

Gutenberg 18.4 is scheduled for release on May 22 and includes these issues.

Discussions

This week, we will continue to discuss the Roadmap for the WordPress 6.6 release cycle, in case anyone has any questions or would like to chat about any of the proposed features, including:

If we have time, we can also discuss the canonical 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. plugins proposal. There is an initial issue and discussion here, and a follow-up Gutenberg PR is currently in progress.

Feel free to suggest additional topics in the comments.

Highlighted posts

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Updates

Props to @annezazu for putting together these updates.

Get involved:

Updates:

    Tickets for assistance

    Tickets for 6.6 will be prioritized.

    Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting if there are any questions or you will be async.

    Open floor

    Items for this can be shared in the comments.

    Props to @joemcgill for reviewing.

    #agenda, #core, #dev-chat

    Performance Chat Agenda: 14 May 2024

    Here is the agenda for this week’s performance team meeting scheduled for May 14, 2024 at 15:00 UTC.

    • Announcements
      • Welcome to our new members of #core-performance
      • Performance lab 3.1.0 release scheduled for May 20
    • Priority items
      • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
        • Current release (6.6)
        • Future release
      • Performance Lab 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 (and other performance plugins)
      • Active priority projects
        • Improve template loading
        • INP research opportunities
        • Improving the calculation of image size attributes
        • Optimized autoloaded options
    • Open floor

    If you have any topics you’d like to add to this agenda, please add them in the comments below.


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

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

    Agenda, Dev Chat, Wednesday May 8, 2024

    The next WordPress Developers Chat will take place on  Wednesday May 8, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

    The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

    Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.

    Announcements

    The WordPress 6.6 roadmap has been published.

    WordPress 6.5.3 was released on Tuesday, May 7. This minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. features 12 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. fixes in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 9 bug fixes for 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. You can review a summary of the maintenance updates in this release by reading the Release Candidate announcement.

    Forthcoming releases

    Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.6

    We are currently in the WordPress 6.6 release cycle.

    Next maintenance release: 6.5.4

    Now that 6.5.3 is released, let’s discuss planning for the next maintenance release.

    Next 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/ release: 18.3

    Gutenberg 18.3 is scheduled for May 8 and will include these issues.

    Discussions

    Following up with some updates from previous week’s discussion:

    • New 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/. channels#core-interactivity-api was created to help folks working there better organize and collaborate.
    • Gutenberg commits: as a way to bring additional visibility to changes committed in the Gutenberg repo, we’ve started an experiment to show commits to the 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. branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". (PR merges) in the #core channel.

    This week, we will have time for open discussion about the Roadmap for the WordPress 6.6 release cycle.

    Feel free to suggest additional topics in the comments.

    Highlighted posts

    Core Editor Updates

    Props to @annezazu for helping put together these updates.

    Tickets for assistance

    Tickets for 6.6 will be prioritized.

    Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.

    Open floor

    Items for this can be shared in the comments.

    Props to @annezazu for reviewing.

    #agenda, #core, #dev-chat

    Performance Chat Agenda: 7 May 2024

    Here is the agenda for this week’s performance team meeting scheduled for May 7, 2024 at 15:00 UTC.

    • Announcements
    • Priority items
      • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
        • Current release (6.6)
        • Future release
      • Performance Lab 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 (and other performance plugins)
      • Active priority projects
        • Improve template loading
        • INP research opportunities
        • Improving the calculation of image size attributes
        • Optimized autoloaded options
    • Open floor

    If you have any topics you’d like to add to this agenda, please add them in the comments below.


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

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

    Agenda, Dev Chat, Wednesday May 1, 2024

    The next WordPress Developers Chat will take place on  Wednesday May 1, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

    The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

    Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.

    Announcements

    The WordPress 6.5 retrospective survey is now closed. Thank you to everyone who responded! Expect a follow-up post with collected, anonymized results once @priethor, @marybaum, and @akshayar have finished processing all of the feedback.

    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/ 18.2 was released on April 24. Read about what’s new in this release.

    Phase 3: the remaining phase 3 related overview issues were created for folks to join Phase 3: Block LibraryPhase 3: WorkflowsPhase 3: Revisions, and Phase 3: Collaboration index.

    Forthcoming releases

    Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.6

    We are currently in the WordPress 6.6 release cycle.

    Next maintenance release: 6.5.3

    There are currently there are currently 3 open trac tickets and 1 Gutenberg ticket left to resolve. A Release Candidaterelease 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). is planned for May 2, with a tentative release date planned for May 7. There is more information about this release in this post, including the 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 schedule and how you can get involved.

    Next Gutenberg release: 18.3

    Gutenberg 18.3 is scheduled for May 8 and will include these issues.

    Discussions

    Last week, we started discussing several topics raised in a recent discussion in the #core-editor channel how we can improve how contributors follow along with editor updates and improve communication within the project. There were several potential actions discussed, including:

    • Create more high-level tracking issues that are not tied to a major release.
    • Create 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/. channels for high-level features, such as navigation (#feature-website-navigation) and the grid 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. (#feature-grid).
    • Create teams 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/ for high-level features to create an easy point-of-contact and discussion space for these features.

    This week, we’ll dedicate our discussion time to summarizing any action items that still need to be followed up on from that discussion.

    Feel free to suggest additional topics in the comments.

    Highlighted posts

    CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Updates

    Props to @annezazu for helping put together these updates.

    Tickets for assistance

    Tickets for 6.6 will be prioritized.

    Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.

    Open floor

    Items for this can be shared in the comments.

    Props to @annezazu and @mikachan for reviewing.

    #agenda, #core, #dev-chat

    Performance Chat Agenda: 30 April 2024

    Here is the agenda for this week’s performance team meeting scheduled for Apr 30, 2024 at 15:00 UTC.

    • Announcements
    • Priority items
      • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
        • Current release (6.6)
        • Future release
      • Performance Lab 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 (and other performance plugins)
      • Active priority projects
        • Improve template loading
        • INP research opportunities
        • Improving the calculation of image size attributes
        • Optimized autoloaded options
    • Open floor

    If you have any topics you’d like to add to this agenda, please add them in the comments below.


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

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

    Agenda, Dev Chat, Wednesday April 24, 2024

    The next WordPress Developers Chat will take place on  Wednesday April 24, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

    The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

    Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.

    Announcements

    An update for the 6.6 release squad has been posted, please note that the release squad is looking for one or two CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads to focus on triaging TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and a Documentation Lead with previous experience for the role.

    Also, a reminder that the WordPress 6.5 retrospective post has been published, please fill in the survey if you would like to leave feedback or suggestions for improvements to the release process. The form and comments will be open until April 26th, 2024

    There was also a recent discussion in the #core-editor channel around several topics linked to how we can improve how contributors follow along with editor updates and improve communication within the project. There were several potential actions discussed, including:

    • Create more high-level tracking issues that are not tied to a major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope..
    • Create 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/. channels for high-level features, such as navigation (#feature-website-navigation) and the grid 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. (#feature-grid).
    • Create teams 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/ for high-level features to create an easy point-of-contact and discussion space for these features.

    Forthcoming releases

    Next major release: 6.6

    We are currently in the WordPress 6.6 release cycle.

    Next maintenance release: 6.5.3

    There are currently 15 open tickets in the 6.5.3 release milestone. There is more information about this release in this post, including the 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 schedule and how you can get involved.

    Next 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/ release: 18.2

    Gutenberg 18.2 is scheduled for April 24 and will include these issues.

    Discussions

    We are planning on discussing the following topics:

    Feel free to suggest additional topics in the comments.

    Highlighted posts

    Core Editor Updates

    Props to @annezazu for putting together these updates.

    Tickets for assistance

    Tickets for 6.6 will be prioritized.

    Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.

    Open floor

    Items for this can be shared in the comments.

    Props to @joemcgill for reviewing.

    #agenda, #core, #dev-chat

    Performance Chat Agenda: 23 April 2024

    Here is the agenda for this week’s performance team meeting scheduled for Apr 23, 2024 at 15:00 UTC.

    • Announcements
    • Priority items
      • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
        • Current release (6.6)
        • Future release
      • Performance Lab 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 (and other performance plugins)
        • Final decision regarding streamlining PL plugin and other standalone plugins #1061
      • Active priority projects
        • Improve template loading
        • INP research opportunities
        • Improving the calculation of image size attributes
        • Optimized autoloaded options
    • Open floor

    If you have any topics you’d like to add to this agenda, please add them in the comments below.


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

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