Tag Archives: summary

Carolina Nymark 9:56 am on September 13, 2024
Tags: , , summary,   

Default Theme Chat Summary, September 11, 2024

This post summarizes the latest Default Theme meeting (agenda, slack transcript).

Status update

We’ve made significant progress with patterns and templates this past week.
The work on Twenty Twenty-Five is happening in the GitHub repository.

  • 36 open issues.
  • 19 open pull requests.

In the Figma file you can see what is completed by looking for a green circle. Designs in progress have a yellow circle, and anything that is blocked or not planned at this time, is labeled with a red circle.

Priorities

  • Finish the work for all the remaining block patterns.
  • Work on the style variations. There’s an open issue to address these.
  • Work on items that are set to [Priority] High.

Once we finish adding the remaining 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. patterns and templates, we’ll start adding issues and instructions on how to proceed with 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. (making strings translatable, etc.), indentation, and polishing the patterns/templates.

Open floor

@erichmond brought up that it is difficult to pick issues to work on, and that even if a contributor is assigned to an issue, there may be duplicate pull requests submitted.

The intention is to follow the assignment to the person who has shown interest in the issue first. A recommendation would be to see if there are pull requests open before starting to work on a given issue.

@luminuu Asked if it would be a good idea to test the theme during the WCUS contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. on Tuesday the 17th of September, and if anyone would be available online during the start of the contributor day.

It is difficult to predict what kind of issues that may be open in the repository on the 17th and if they are suitable to work on during a contributor day. A new label in the repository can help contributor day attendees to select issues to work on.

Thanks to @beafialho & @juanfra for reviewing the summary.

#bundled-theme, #core-themes, #summary, #twenty-twenty-five

Joe McGill 12:40 am on September 13, 2024
Tags: , , , summary   

Summary, Dev Chat, September 11, 2024

Start of the meeting in 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/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

WordPress 6.2.2 was released this week.

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

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 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 scheduled for Tuesday, October 1. The Road Map post can be found here.

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

Following the recent WordPress 6.6.2 release, the next maintenance release (if needed) will be WordPress 6.6.3. There were not updates shared in the meeting.

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: 19.2

The next Gutenberg release will be 19.2, scheduled for September 11 (this release occurred after the meeting).

Discussion

@peterwilsoncc requested that we discuss 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. Bindings UIUI User interface feature, TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. #61945.

To summarize his concern:

My main concern here is that the approach is to hide the UI from users with low permissions. I don’t feel that this is a great approach to handling a UI that is considered too technical, as I don’t think there is anything to suggest that an administrator will understand what an author does not.

So I’m of the view the interface ought to be improved and made less technical before it’s shipped in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

@noisysocks suggested waiting on an update from Mario Santos, who is working on the feature, but added:

I’d be fine with just updating this to use caps. The interface doesn’t strike me as being too technical. Can put it in the Advanced tab if we’re worried…

…The short of it is that I’m okay with fixing the cap issue (add a new cap, don’t check against a role) and shipping in 6.7 or leaving it in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party for more testing. Up to the team working on it. We have until beta 1 to decide.

@joemcgill highlighted two additional Slack updates this week:

Open Floor

@mikachan provided an update on #61708 on the agenda:

I’ve addressed the feedback by adding a deprecation notice to the pattern rather than removing it. I’d appreciate any thoughts on if this feels like a better approach.

@peterwilsoncc agreed to review.

@joemcgill pointed out #62004. @jrf recently asked all committers to review in full here. Julia shared the following updates during the meeting:

Ticket #53010 is basically the first step: splitting up the huge test classes to smaller classes which each only test one thing, i.e. one global function, one method in a class etc.

This includes making sure that the new test files comply with the PHPUnit naming conventions.

There are a number of patches attached to the ticket which can be used to see how to do this (mind: not all have been reviewed yet for the latest info).

I also think it would be great if we could get a decision on yes/no namespacing the test classes. I believe we should and that now is the time.

And followed up with

The other thing which would really really help, is to make sure that any new tests go in “clean”. As in: comply with the requirements for newer PHPUnit versions. The task is large enough as it is without having to clean up after new commits.

#6-7, #core, #dev-chat, #summary

Birgit Pauli-Haack 8:14 am on September 11, 2024
Tags: , , , summary   

Summary of the Developer Blog editorial meeting on 5 September 2024

Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Start of the meeting in Slack.

Attendees: @greenshady @webcommsat @oglekler @ndiego @zeelthakkar @jagirbahesh @bcworkz (async) and @bph (facilitator).

Last meeting notes: Developer Blog editorial meeting summary 1 August 2024

In this article

Contributor updates

  • Congrats to @ajlendelende and @aljullu to receiving their Documentation Contributor badges for their contributions to the Developer Blog.  
  • Call for contributors to take on What’s new for Developers roundup post for November? @greenshady @ndiego or I (@bph) will be right with you to guide you through the research as well as the writing part. If you want to take it on, come to the #core-dev-blog channel or DM either one of us.

Newly published posts since last meeting

Since the last meeting, we published the following articles

Huge Thank You to the writer and reviewers! 

Project status

The project board for Developer Blog content is 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/.

Issues closed

In review

In progress

On the to-do-list, assigned to writers

Topics approved, in need of a writer

If you are interested in taking on a topic from this list or know someone who would be a good person to write about them, comment on the Issue or 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.” @bph in Slack either in the #core-dev-blog channel or in a DM.

New topics approved

The topic idea Modifying text with the HTML API in WordPress 6.7 needs to simmer some more to see if there will be more elaborate examples coming in the next major WordPress version. Justin will bring it back to the October meeting should the topic deemed mature enough for a blog post.

Open floor

@greenshady inquired about the possibility of translating the content of the Developer blog into other languages. Currently, there isn’t a formal proposal for a process and tools. It’s worth exploring, though. It was stated that it’s complicated for Rosetta sites, and it might not be easy to translate. It would be better if the translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. can be put right into the adminadmin (and super admin). If there is someone who translated an article, we could publish it on the Dev Blog under “other languages” and once we have a critical mass, we can create categories for Spanish, German etc. The bigger issue than the technological implementation is the recruiting and onboarding of translators to be contributors.

@bph is to reach out to the training team, to learn about their process, as they are a few steps ahead in working with translators.

@greenshady will open an issue, where we can follow up on discussion and progress.

Next meeting: October 3rd, 2024, at 13:00 UTC in the #core-dev-blog channel

Props to @greenshady for the review of the post.

#meeting, #meta, #summary

Emily Clarke 4:01 pm on September 10, 2024
Tags: , , , , summary   

Performance Chat Summary: 10 September 2024

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

Announcements

  • Welcome to our new members of #core-performance
  • 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. US is coming up Sep 17-20 in Portland, Oregon – we will have a performance table at Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. with Adam
  • WordPress 6.7 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 October 1
  • Performance Lab next release scheduled for Sep 23

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

WordPress Performance Trac Tickets

Performance Lab Plugin (and other Performance Plugins)

Active Priority Projects

Investigate INP Improvements

  • No updates this week

Improving the calculation of image size attributes

  • @joemcgill we’re still working through some details on the approach for incorporating layout info for ancestor blocks and hope to have an update later this week.

Enable Client Side Modern Image Generation

  • @swissspidy Nothing new really from my side since last week. A couple of smaller PRs got merged into GB, and I’m ironing out some build tooling issues. Apart from that, focusing on my WCUS talk

Enhance Onboarding Experience of Performance Lab Plugin

  • @flixos90 The only news on enhancing the onboarding experience is that we’re going to ask attendees at the Google booth at WCUS to give Performance Lab a spin. We hope that from there we get a diverse list of people, especially including ones that have not used the plugin before. That should help us get some idea on what people consider pain points in the onboarding process.

Open Floor

  • @swissspidy Performance chat sometimes clashes with release parties (like today). Should we consider moving the meeting on those occasions? e.g. by +1 hour or so. Or not a big deal?
    • @joemcgill I’m unsure how many of the release parties for this 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. will happen at the usual time, given the timezone makeup of the team. I think @peterwilsoncc was planning on publishing a schedule for betas/RCs soon. Perhaps something to consider after that?
  • Suggestion to cancel next week’s meeting due to WordCamp US

Our next chat will be held on Tuesday, September 24, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Beatriz Fialho 3:57 pm on September 5, 2024
Tags: , , summary,   

Default Theme Chat Summary, September 4, 2024

This post summarizes the latest Default Theme meeting (agenda).

Status update

The work on Twenty Twenty-Five is happening in the GitHub repository. At the time of the meeting, there were 54 open issues and 19 open pull requests.

There were about 45 patterns designed in total. 31 patterns were built/merged or had open in-progress PRs. 14 patterns were not yet built.

There were 34 templates designed in total, 22 templates are built (the default personal blogblog (versus network, site) and alternative ones for personal, photo and news blogs). Due to time constraints, the “blogging with sidebar” alternative likely won’t get built.

There’s an open issue to create the “combined” global style variations. 1 of the 8 variations has been created, 4 others are assigned.

It is possible to see what’s 🟢 built/ 🟡 not built/ 🔴 may not be built in the Figma file.

Some important information regarding the project timing was shared: the theme needs to be more or less complete before October 1, 2024, after that it is 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 only. And text strings need to be final before October 22, 2024.

Priorities

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. patterns are the highest priority now, and need to be completed as soon as possible to be used to create the other layouts such as landing pages and homepages. There are “High priority” labels and they will also dictate what’s becoming a priority along the project.

Call notes

According to the agenda, a short, informal call happened to take a look at what’s built and what’s not, and determine if some of the original designs need to be left out. Those present were @beafialho, @poena, @juanfra, @luminuu and @oncecoupled.

The call focused on the progress and challenges of the development of Twenty Twenty-Five.

Key points:

  • The completion of personal default templates and alternatives, with some patterns still pending-
  • Four patterns are blocked due to the lack of image support for categories in search templates and the new accordion block’s delay, leading to the possibility to leave out three “categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.” patterns
  • The team discussed the feasibility of adding patterns directly from the patterns 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. and the need for consistent naming and ordering of section styles
  • The team also considered the impact of 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. US contributions and the need for thorough testing and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) checks

Action items:

  • Follow up on the new accordion block PR and status
  • Evaluate building search result patterns or leaving them out
  • Consider adding a “page” category for patterns
  • Eventually 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.” accessibility reviewers for testing

Thanks to @juanfra for reviewing the summary.

#bundled-theme, #core-themes, #summary, #twenty-twenty-five

Sarah Norris 2:11 am on September 5, 2024
Tags: , , , summary   

Summary, Dev Chat, September 4, 2024

Start of the meeting in 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/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

There were no announcements this week.

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

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 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 scheduled for Tuesday, October 1. The Road Map post was recently published.

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

The next maintenance release will be WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the 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: 19.2

The next Gutenberg release will be 19.2, scheduled for September 11.

Discussion

When discussing WordPress 6.7, we highlighted that @joen has listed some items that could use some help here, and @noisysocks reminded us that it’s always worth checking the Editor tasks board, especially items in the “Todo” and “Needs review” columns.

@peterwilsoncc asked for some additional eyes on this PR.

@noisysocks confirmed that the last Gutenberg 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). before the feature freeze is September 18, and these are the biggest items to keep an eye on:

Open Floor

@ironprogrammer asked: Has there ever been a pre-Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. online hangout where people could get this help beforehand? And maybe more importantly, would it do any good toward getting folks prepared before they arrive? – @joemcgill mentioned the documentation in the handbook and offered to reach out to the WCUS organizers to see if there is a need for more support with the onboarding process this year.

Props to @joemcgill for proofreading.

#6-7, #core, #dev-chat, #summary

Emily Clarke 4:05 pm on September 3, 2024
Tags: , , , , summary   

Performance Chat Summary: 3 September 2024

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

Announcements

  • Welcome to our new members of #core-performance
  • Last week we reached over 1,000 members of our channel
  • 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. US is coming up Sep 17-20 in Portland, Oregon – we will have a performance table at Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. with Adam
  • WordPress 6.7 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 October 1

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
  • 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)
    • Next milestone
    • Clarification on September release date due to clash with WordCamp US
  • Active priority projects

WordPress Performance Trac Tickets

Performance Lab Plugin (and other Performance Plugins)

  • Discussed the next Performance Lab release moving a week later to Sep 23 due to WordCamp US
  • @flixos90 While not related to WordPress/performance, I spent some time last week documenting the processes for how the Plugin Checker works, see https://github.com/WordPress/plugin-check/issues/597 and https://docs.google.com/document/d/1wDGZBwWB2WAxfbHE3lygIzQFK8IssCa5apOyaBolukQ/edit. Since the logic is quite complex to follow with the different possible scenarios, this is probably valuable to have as a reference, so please have a look if you’re interested, should help any contributor to PCP
    • Eventually, after ironing out remaining questions and functional quirks, we could add a version of that to the docs folder of the repository

Active Priority Projects

Investigate INP Improvements

  • No updates this week

Improving the calculation of image size attributes

Enable Client Side Modern Image Generation

  • @swissspidy Working on 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/ PRs for media, but currently focusing on my WCUS talk

Enhance Onboarding Experience of Performance Lab Plugin

  • @flixos90 last week we informally chatted a bit more about asking some attendees at the WCUS booth to test using the PL plugin, to see how they experience the onboarding, where they may be confused or have questions. So that’s definitely something we’re going to incorporate in the Google booth section for performance – primarily for attendees that may not be familiar with the plugin yet, or at least haven’t used it before

Open Floor

  • Discussion around this Slack thread for persistent object cache
    • @westonruter I suppose the test for object caching should only be prominent if a site does not have page caching. A site may not use page caching due to it being highly dynamic or acquiring users to be logged in. For such a site, object caching would perhaps be the next best thing instead of page caching.
    • @joemcgill There are so many “it depends” scenarios when it comes to what caching strategy is best. For example, if you’re running a site like a store that needs to serve dynamic data and can’t use a full page cache, an object cache will reduce the load on the DB, which should speed up requests. However, if you run a site that can make use of a full page cache, that will usually be better because it avoids any need for the server to load data from the DB and render the page at all. For many sites, full page cache is probably a more meaningful strategy. Setting up an object cache is more complex and usually is not something folks will set up themselves—instead, relying on whatever their host has set up.
    • @joemcgill It’s possible that the Site Health message could be improved so most site owners aren’t confused by the nuances of all these options and focus only on the things that most people can actually affect, e.g., setting up a full-page caching solution. Hosts can also modify CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s default site health checks to give better guidance on their hardware. Possibly something to chat about with the #hosting team
    • @paaljoachim asked What can he do from the sideline? Should I mention this discussion in the hosting channel? Something else? Should I leave it up to you in this channel to followup on this?
    • @thelovekesh As the number of plugins in the PL mono-repo grows, CI times are increasing accordingly. To address this, we should update our workflows to:
      • 1. Run tests only for the plugin whose files have been updated.
      • 2. Apply the same approach for linting and static analysis.
    • This issue also impacts local development, particularly with PHPStan. While linting is fast with each commit(pre-commit hook), static analysis still runs across the entire codebase.
      • @westonruter Good idea, although there are risks for doing this when there are plugin dependencies. Like if someone changes code in Optimization Detective which Image Prioritizer depends on, then this might slip under the radar. We could specifically account for plugin dependencies

Our next chat will be held on Tuesday, September 10, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary

Juan Aldasoro 12:17 pm on August 30, 2024
Tags: , , summary,   

Default Theme Chat Summary, August 28, 2024

This post summarizes the latest Default Theme meeting (agenda, slack transcript).

Status update

Most presets are now part of the theme, and work is being done on the different templates and patterns. The repository now has priority labels to indicate the urgency of specific issues and pull requests.

Over 20 contributors have participated so far, and over 60 open issues are in the 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/ repository. Many are related to 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. patterns, and the ones with the “Need Dev” label are ready to be worked on.
https://github.com/WordPress/twentytwentyfive/issues

A decision was made not to use domains or brands in graphic elements or patterns. More about that discussion and decision here. There were also conversations on how to improve the process of getting the images from the Figma file to add them to the theme, which resulted in hosting the images in a public directory.

Priorities

With the different presets already in the theme, contributors are ready to start working on the different theme styles. Next, the alternative templates for photo blogblog (versus network, site), complex blog and personal blog.

At the same time, work needs to be completed on block patterns to be used in the creation of other layouts, such as landing pages.

Open floor

@joen mentioned that there’s a good list of Gutenberg-related issues to the theme development, created by @poena, and that he’d be willing to help expedite those.

@beafialho asked how to proceed with implementing templates, when parts are still being discussed or there are independent issues to work on. The conclusion was that as long as there’s communication on why there are things that are not being fully implemented according to the design, and there are links to the other issues we can move forward to expedite things.

@beafialho also asked about creating GitHub issues vs. opening PRs directly when she finds issues with the implementation. The idea is that if the issues found are quick to fix, a PR could be the best way to expedite things. If the issues found are related to bigger changes, then creating GitHub issues would be the best way to proceed. As it can open up the game for contributors to work on those, and it’ll keep track of the progress and what happened.

Thanks to @poena for reviewing the summary.

#bundled-theme, #core-themes, #summary, #twenty-twenty-five

Joe McGill 1:44 am on August 29, 2024
Tags: , , , summary   

Performance Chat Summary: 27 August 2024

The full chat log is available beginning here on Slack.

Upcoming WordPress 6.7 release

We reviewed the 6.7 milestone for performance focus tickets.

  • #61103 (marked as an early ticketticket Created for both bug reports and feature development on the bug tracker.) – @flixos90 had just reviewed, and @pbiron will update the PR.
  • #61847 – @mukesh27 is working on a PR for this.
  • @adamsilverstein shared that he had a couple of small AVIF fixes that he’s planning to move to the milestone

 Next Performance Lab release

The current milestones can be found at https://github.com/WordPress/performance/milestones, and the release date is Sept 16. @joemcgill questioned whether this date will conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with WCUS that week.

  • @adamsilverstein is working on a PR for the Modern Images 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 to include converting upload PNGs in addition to JPEGs that I hope will be ready for the next release.
  • @thelovekesh is working on Web Worker Offloading(WWO) plugin to make it ready for WPOrg. Ongoing tasks:

Priority Projects

Refer to the overview issues in our GH Project board.

Open floor

Conversation about priority projects bled over into open floor. No other items were discussed.

Our next chat will be held on Tuesday at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #performance, #performance-chat, #summary

Joe McGill 1:26 am on August 29, 2024
Tags: , , , summary   

Summary, Dev Chat, August 28, 2024

Start of the meeting in 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/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

There were no announcements this week.

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

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 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 scheduled for Tuesday, October 1.

The bug scrub schedule was published prior to the meeting.

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

The next maintenance release will be WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the 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: 19.1

The next Gutenberg release at the time of the meeting was 19.1, which was released on August 28.

Discussion

The first topic was, “which releases can be done during normal working hours for our CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech leads?”

@joemcgill referenced this comment on the agenda post and asked @peterwilsoncc to clarify the what was being considered.

I saw a comment in the 6.7 channel that release parties are also apparently going to happen in APAC times? I’d like to know if this was discussed in public somewhere. I know moving Dev Chat was discussed, but I (as 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). for 6.7) wasn’t included in the discussion about moving the release parties, neither before or after I accepted the role.

To summarize @peterwilsoncc response:

  • Beta release parties can happen during APAC sunlight
  • RCs will need to happen at around the usual time (~16:00 UTC) to allow for increased attendance
  • For the betas, @peterwilsoncc can drive MC and @kirasong and @noisysocks could do release commits
  • During RC, MC and commits will need to be people off the release squad

@joemcgill:

I’ll note that the time you’re suggesting for betas is well out of timezone for David who is the release coordinator. According to the handbook the first responsibility of the release coordinator is to “Run various release processes in Slack (beta, 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)., release)” but whatever you all work out seems fine.

@peterwilsoncc agreed to coordinate with the release squad about release timing will publish a post announcing the timing of release parties.

Next, @kirasong shared a list of issues that had been highlighted in #6-7-release-leads as things that folks can get involved with.

@noisysocks reminded that the Iteration/Tracking Issues column in the Editor tasks board is the best source of truth re. current initiatives.

Open Floor

We discussed the following issues:

#6-7, #core, #dev-chat, #summary