Tag Archives: meeting

Tonya Mork 8:03 pm on January 16, 2024
Tags: , , , , , meeting,   

Dev Chat Summary, January 10, 2024

The WordPress Developers Chat meeting took place on  10 January 2024 at 20:00 UTC  in core on Make WordPress Slack.

Key info

Please read the DevChat Agenda for a curated list of announcements, highlighted posts, Core Editor updates, major and minor release updates, and more.

Chat Summary

Nominations for 2024 Core Team Reps:

@desrosj reminded Gutenberg and Core development contributors to update their local Node.js/npm as:

.. the versions of Node.js and npm required for WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development are now 20.x and 10.x.

In order to continue contributing to WordPress through wordpress-develop or WordPress/Gutenberg, you’ll need to upgrade the version of Node.js installed on your machine to one that’s greater than or equal to 20.10.0 (currently the most recent generally available version 20.x version). This should also update npm to the correct, expected version appropriately (10.2.3 or higher is required).

Release Updates

Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.4.3

@jorbin shared an update:

  • Timeline coming before next devchat.
  • No pressing issues – okay to wait “a few weeks for the next minor.”
  • Reminder to “milestone any tickets” needing addressing.

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

  • Release squad: call to join the squad ended Jan 12th.
  • Current: in Alpha.
  • Next milestone: 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 is Feb 13th.

Tickets / Issues that need assistance

  • #60227 @jonsurrell asked for feedback to use an external library for testing the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. 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..
  • #60025 @jorbin requested help (it’s in the 6.4.3 milestone) and noted:

Joe did a great job of summerizing and shared some paths forward that I think could be good to explore

Open Floor

Discussion of changing DevChat

@jorbin opened the discussion for changing DevChat, i.e. to get to the important things to chat about (rather than half or more of the meeting dropping links):

As we are now 43 minutes into the meeting and it’s been almost all link sharing thus far, I wonder if perhaps 2024 should be the year we explore some alternatives for this meeting? I’m not sure that a link dump is doing it

The discussion summary:

socializing to folks leading/working on feature projects or specific items targeted in a current major release that devchat is a good place to come and share blocks/problems/areas for feedback they have.  Chatting through those things synchronously can help find alternate paths forward for those things that are of importance to the project.

advance those conversations towards an acceptance or finding iterative ways to improve those proposals.

When to start? Experiment starts next meeting.

Call for Volunteers to review the open proposals on Make/Core and create a list of unresolved ones to discuss during the DevChat meeting.

Font Library – avoid merge roadblocks

@joemcgill asked for Font Library update and plan to avoid the roadblocks experienced during 6.4. See the discussion in the Slack thread which includes Core merge criteria.

Next Meeting

The next meeting will be on 17 January 2024 at 20:00 UTC . This DevChat will experiment with a new approach

Are you interested in helping draft DevChat summaries? Volunteer at the next meeting!

Props @webcommsat for peer review.

#6-4, #6-5, #core, #core-editor, #dev-chat, #meeting, #summary

Emily Clarke 12:43 pm on January 16, 2024
Tags: , meeting, ,   

Performance Chat Agenda: 16 January 2024

Here is the agenda for this week’s performance team meeting scheduled for Jan 16, 2024 at 16:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.

  • Announcements
    • Welcome to our new members of #core-performance
    • 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 release today for version 2.8.0
  • Priority projects
  • Open floor

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

Emily Clarke 11:18 am on January 9, 2024
Tags: , meeting, ,   

Performance Chat Agenda: 9 January 2024

Here is the agenda for this week’s performance team meeting scheduled for Jan 9, 2024 at 16:00 UTC. 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

Emily Clarke 10:40 am on January 2, 2024
Tags: , meeting, ,   

Performance Chat Agenda: 2 January 2024

Here is the agenda for this week’s performance team meeting scheduled for Jan 2, 2024 at 16:00 UTC. 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

Emily Clarke 10:25 am on December 19, 2023
Tags: , meeting, ,   

Performance Chat Agenda: 19 December 2023

Here is the agenda for this week’s performance team meeting scheduled for Dec 19, 2023 at 16:00 UTC. 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

Brian Alexander 10:17 pm on December 13, 2023
Tags: , , , meeting,   

Dev Chat Summary, December 6, 2023

The WordPress Developers Chat meeting took place on  6 December 2023 at 20:00 UTC  in core on Make WordPress Slack (or #core in Matrix).

Key info

Announcements

  • WordPress 6.4.2 Maintenance & Security Release: 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. addresses a handful of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. bugs, as well as a preventive security update. Props to the minor release squad for getting this shipped!

Highlighted Posts

Editor Updates

@annezazu has graciously shared this week’s #core-editor update, found here: https://make.wordpress.org/core/2023/12/05/dev-chat-agenda-december-6-2023/#comment-45924

Release Updates

Next minor release: 6.4.3

@jorbin indicated that work is underway to put a squad together for this release.

👉🏻 Volunteers interested in helping on the 6.4.3 minor release should drop a note in #6-4-release-leads.

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

Some helpful links:

Are you able to help with future 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. scrubs? Bug scrubs post. Next scrub: December 19, 2023 at 19:00 UTC in the #core Slack channel.

Component Maintainer Updates

Disable autoload for large options

@flixos90 requested a second opinion and general feedback on the approach envisioned in https://core.trac.wordpress.org/ticket/42441. In order to differentiate between whether an autoload value for an option was set as a default or explicitly chosen, it is proposed to add new possible values for that database column. For additional context, comment:20 may be helpful, and a PR implementation already exists.

While personally supportive of the effort, Felix added that such a change will require a dev notedev 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 plugins specifically focused on autoloading may need to cater for the change. It was clarified that only plugins that enhance autoloading specifically should be affected. @azaozz agreed that this approach was sound, and should be fully backwards compatible. Additional discussion moved to the Trac ticket.

Open Floor

Core version displayed on Updates page

From the agenda comments, @shenyanzhi wished to draw attention to https://core.trac.wordpress.org/ticket/40241. It was suggested to raise the ticketticket Created for both bug reports and feature development on the bug tracker. over in #core-upgrade-install for additional feedback, and for contributors to leave a comment on the ticket or dev chat post comments.

Disable the WordPress-Docs ruleset in Gutenberg

Also from the agenda comments, @antonvlasenko asked for feedback on a proposal (GB 56487) to [temporarily] disable the WordPress-Docs ruleset from Gutenberg. Core doesn’t use these rules, so this change would simplify the backporting process from Core, improving parity between the repos. Feedback on the issue or accompanying PR is greatly appreciated.

Next Meeting

The next meeting will be on 13 December 2023 at 20:00 UTC .

Are you interested in helping draft Dev Chat summaries? Volunteer at the next meeting!

Props @hellofromtonya for peer review, and @webcommsat for essential meeting preparation work.

#6-4, #6-5, #dev-chat, #meeting, #summary

Emily Clarke 12:06 pm on December 12, 2023
Tags: , meeting, ,   

Performance Chat Agenda: 12 December 2023

Here is the agenda for this week’s performance team meeting scheduled for Dec 12, 2023 at 16:00 UTC. 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

Emily Clarke 10:47 am on December 5, 2023
Tags: , meeting, ,   

Performance Chat Agenda: 5 December 2023

Here is the agenda for this week’s performance team meeting scheduled for Dec 5, 2023 at 16:00 UTC. 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

marybaum 10:03 pm on November 28, 2023
Tags: , meeting,   

Dev chat summary, November 22, 2023

Here’s what happened in the dev chat from November 22, with @marybaum facilitating, on this agenda. If you would like more detail, check out the chat transcript.

Announcements

What’s new in Gutenberg 17.1

Highlighted posts

Exploration to support Modules and Import Maps – this post shares the collaborative effort to explore native support for modern 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/. modules and import maps within the WordPress ecosystem to enhance the developer experience. Head over to the post if you’d like to get involved.

New section: coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor updates

@annezazu was in the house to kick off an experiment: instead of a separate editor chat, the editor team will have its own section for updates in the Core devchat.

In the meeting, the discussion started with a cut-and-paste of her comment on the agenda; then folks could question and comment on the items they were interested in. The result was a clear view of the huge job the editor team has been doing—and continues to polish.

Tickets

The group skipped over the standard upcoming-releases section to bring up two tickets whose stakeholders particularly wanted to get eyeballs on.

#59758 went first and got a commitment to test its 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. from the attendee who showed up at the meeting specifically to advocate for it.

The other, #59866, got attention in 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 that happened just before this summary appeared on the Make blogblog (versus network, site).

Thanks to the folks who helped move both those tickets in the right direction!

#dev-chat, #meeting, #summary

Emily Clarke 12:04 pm on November 28, 2023
Tags: , meeting, ,   

Performance Chat Agenda: 28 November 2023

Here is the agenda for this week’s performance team meeting scheduled for Nov 28, 2023 at 16:00 UTC. 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