Core Team Reps for 2023: Submit Your Votes

Two weeks ago we opened up nominations for new CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team Reps to replace @marybaum and me. Nominations have closed, so now it’s time for voting!

You can find the poll below. Since we’re aiming to elect two reps, you can vote for up to two people.

What Are Team Reps?

In the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project, each team has on average one or two representatives, abbreviated as reps. Some teams have more than two, but for the sake of sanity sticking with two for now keeps things simpler. And for the historians out there, the role goes way back to 2012.

Historically with the Core team, the team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. duration was around a year, though some reps stuck around longer if there was a particularly good fit.

Anyone who serves as a “team rep” is responsible for communicating on behalf of the Core team to the other contributor groups via weekly updates, as well as occasional cross-team chats. Reps are also consulted on 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/., to help find someone on the Core team who will be at an event who can help lead a Core table.  Full details on the Team Rep role is on the Team Update site.

It is not called “team lead” for a reason.  It’s an administrative role. While people elected as team reps will generally come from the pool of folks that people think of as experienced leaders, the team rep role is designed to change hands regularly.

This role has a time commitment attached to it. Not a huge amount, but it’s at least one or two hours a week.

Here are the main tasks:

Then… let’s get ourselves two new reps!

Where Can I Vote?

You can vote for up to two people at the same time, but once you have submitted your vote you won’t be able to vote again.

If you have any questions, please feel free to ask in the comments. @marybaum and I will be happy to reply. Thanks!

This poll will remain open until Friday, December 16, 2020 at 23:59 UTC, after which team reps will be chosen based on the votes received.

Co-authored by @audrasjb and @marybaum.

#team-reps

Dev Chat summary: Wednesday, November 30, 2022

Here’s a summary of the weekly WordPress developers’ chat for November 30.

1) Welcome

IF you’re new to dev chat, you can find out more about this weekly meeting in the handbook.

Meeting facilitators: @marybaum and @webcommsat.

Agenda followed; thanks to @marybaum for preparing it.

Start of the meeting in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of 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/..

Summary from the November 23, 2022 dev chat.

2) Announcements

Slack link.

  • WordPress 3.7 – 4.0 have landed their final versions. Props to everyone who volunteered and to @peterwilsoncc for leading.
  • 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/ 14.7 is expected to land 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). today.
  • Nominations for 2023 Core Team Representatives close this Friday.

3) Blogblog (versus network, site) posts of note

Slack link.

4) Upcoming releases

Slack link.

a) The 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. is 6.2

December is a great time to work on the things you would most like to see land in 6.2.

b) The 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. is 6.1.2.

No updates from the release teams at this time.

5) Components and tickets

Slack link.

a) Components

Build/Test Tools, Date/Time, General, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks: no major news this week – @sergeybiryukov.

Site Health: nothing new to report – @clorith

Quick/ Bulk Edit Component

  • #54378 @webcommsat: This ticketticket Created for both bug reports and feature development on the bug tracker. could be an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. if anyone wanted to work on it. This has been raised in scrubs previously.
  • #55549 This ticket has been closed for now after testing.
  • #56137 Raising this ticket as it has come up a couple of times in meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. groups – request to be able to add excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. in Quick Edit.

b) Tickets

  • No other tickets were raised.

6) Open Floor

Slack link.

a) WordPress 6.1 issue #45713

@bernhard-reiter: WordPress 6.1 has an issue with .is-layout-flex. The issue is complicated, and some testers are having trouble reproducing it. Full details are in the chat as it happened.

Props to: @marybaum and @webcommsat for running dev chat, @dpotter05 for the summary, and to @webcommsat and @marybaum for review.

#6-1, #6-2, #dev-chat, #summary

Devchat agenda, November 30, 2022

1. Welcome

The WordPress Developers’ chat happens every Wednesday in the #core channel of 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/. at 20:00 UTC. If you’re keeping track, here’s last week’s summary.

2. Announcements

The final versions of WordPress 3.7 – 4.0 have landed with a notice on each that they are no longer supported. Please encourage your users to upgrade to WordPress 6.1.1, running PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 or later.

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/ 14.7 RC1 will land while devchat is happening. More info to come!

Nominations for the 2023 Core team reps will close Friday.

3. Blogblog (versus network, site) posts of note

From @estelaris, the Docs team is looking for feedback on a second iteration of DevHub’s new look.

From @audrasjb comes the latest A Week in Core.

@azaozz proposes a change to multiline commenting standards.

4. Upcoming releases

The next major is 6.2; the next minor is 6.1.2.

December is a great time to work on the things you would most like to see land in 6.2—before the release cycle ramps up in the new year.

5. Components and tickets

If you’ve got the tickets, the devchat group has the time.

6. Open floor

Add your item to the comments!

#agenda, #dev-chat

Now Available: WordPress 3.7-4.0 Final Releases

WordPress 3.7.41, 3.8.41, 3.9.40 and 4.0.38 are now available!

These releases feature an update to the upgrade notification to indicate these versions of WordPress are no longer receiving security updates. WordPress 4.1 and later will continue to receive such updates.

The next major version of release of WordPress will be version 6.2 planned for next year.

On sites running WordPress 3.7-4.0 with automatic updates enabled, the upgrade process will begin automatically.

These releases should not be used on new production websites. The latest version of WordPress is available from the downloads page.

Thank you to these WordPress contributors

These releases were led by Josepha Haden Chomphosy and Peter Wilson with Dion Hulse running mission control.

These WordPress releases would not have been possible without the contributions of JB Audras, Colin Stewart, Česlav Przywara, Robin, Jonathan Desrosiers, Linkon Miyan, Mukesh Panchal, Sumit Bagthariya, Matt Mullenweg, Josepha Haden Chomphosy, Peter Wilson, Dion Hulse and the WordPress security team.

As there was no update to the currently stable version of WordPress, version 6.1, these releases were announced here rather than on wordpress.org/news. It was announced on 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/ these version of WordPress would cease receiving security updates earlier this year.

Thanks to @costdev for proofreading this post.

#releases

Performance Chat Summary: 29 November 2022

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

Focus area updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Measurement

N/A

GitHub project

  • No updates

Feedback requested

JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSS Cascading Style Sheets.

@aristath @sergiomdgomes

GitHub project

  • No updates

Feedback requested

Database

@olliejones

GitHub project

  • @mxbclang: What are the next steps on Revisit indexes for DB performance #132?
    • @olliejones: Current voting winner points to doing something dbms-version-specific to the schema, eventually in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., think we can do this 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 if we’re willing to accept a mu-plugin drop-in module. Disadvantage here is complexity.
    • @flixos90: This is tricky – we have a voting winner, but also some strong opinions from different sides including a WP lead developer.
    • @mxbclang: Seems like the best next step here would be to close out the vote as planned but hold on next steps pending further discussion in the issue, then regroup on this in a future chat
    • All agreed; vote will close and @mxbclang will add a comment about next steps
  • @olliejones: SQLite Object Cache is coming along nicely; will create a new module proposal issue once it’s closer to complete
  • @olliejones: For future discussion: Do we need some sort of formal set of filters, etc. to support the big competent hosting providers in this back-end area?

Feedback requested

Infrastructure

@flixos90

GitHub project

  • @flixos90: Been working on iterating on the Server-Timing API PR. Still in draft because unit tests need to be added, but ready for review. Would love feedback and opinions on the 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. implementation. The most important recent change is that it is now initialized early through a drop-in, so it can capture measurements that happen before WP plugins are loaded.

Feedback requested

Open floor

  • @olliejones: There’s a sustainability team forming – see #sustainability Slack channel
  • @nickchomey: Been working on implementing a real PWA for a site under development. Plugin options are limited right now but @westonruter‘s plugin is the right approach. Is this something that the performance team can move forward?
    • @flixos90: Not sure what the current state of the plugin is; original idea was for it to be a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.
    • @nickchomey: Proposing a real coordinated effort be made to improve it to the point that it could be merged into core
    • @flixos90: It could definitely be feature plugin material, but as always it requires resources. If a small group is up for tackling, we would be supportive and help here possible.
    • @westonruter: The plugin is stable and essentially in maintenance mode. Not clear if there is the 80% user benefit to justify core merge just yet. See discussion between @nickchomey and @westonruter in GH issue: https://github.com/GoogleChromeLabs/pwa-wp/issues/884.
    • @flixos90: Key aspect of proposing this for core would be to come with an actual usage of PWA capabilities that immediately benefits core users
    • @westonruter: Benefit that all users could get now is offline browsing on the front-end, but there’s a separate concern of what happens when a large portion of the web is registering service workers
    • @pbearne: Aren’t we going to need something like this for real-time multi-editing in 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/?
    • @olliejones: Maybe the Twenty Twenty Four theme could be made PWA-friendly?

Our next chat will be held on Tuesday, December 6, 2022 at 16:00 UTC in the #core-performance channel in Slack.

#core-js, #core-media, #performance, #performance-chat, #summary, #hosting-community

#meta

A Week in Core – November 28, 2022

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 21 and November 28, 2022.

  • 26 commits
  • 32 contributors
  • 76 tickets created
  • 0 tickets reopened
  • 66 tickets closed

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

Bundled Themes

  • Twenty Eleven: Remove useless title attributes – #57199, #24766, #24203
  • Twenty Nineteen: Remove the incorrect “flexible-headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.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.)#46213
  • Twenty Nineteen: Remove useless title attributes – #57199, #24766, #24203
  • Twenty Ten: Fixes brace indentation in loop-attachment template – #57210, #56791
  • Twenty Twenty-One: Add a comment for the closing h2 tag in author info template – #56476
  • Twenty Twenty-Three: In page template, make post titles links – #57175

Coding Standards

  • Correct the deprecation version for _filter_query_attachment_filenames()#56791
  • Fix brace indentation in wp-align/includes/noop.php#57209, #56792
  • Remove extra slashes when concatenating ABSPATH with a path – #57074, #57071
  • Use HOUR_IN_SECONDS where appropriate – #56791
  • Various brace indentation corrections – #57210, #56791

Comments

  • Make moderated or disallowed key check case-insensitive for non-Latin words – #57207

Docs

  • Add missing parameter descriptions in wp-admin/includes/template.php#57208, #56792
  • Correct the type for _WP_Dependency::$src property – #57206
  • Improve various globals documentation, as per documentation standards – #57069, #56792
  • Improve various globals documentation, as per documentation standards – #57069, #56792
  • Improve various globals documentation, as per documentation standards – #57069, #56792
  • Revise comments using “we” in WordPress root directory files – #57052
  • Use third-person singular verbs 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. Supports related function descriptions, as per docblocks standards – #56792
  • Various docblockdocblock (phpdoc, xref, inline docs) fixes in Block Supports related functions – #56792

Plugins

  • Improve “No 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 found” message alignement in Plugins screen – #57194, #55721, #55272

Site Editor

  • Show correct theme per template or template part – #55437

Tests

  • Add a public visibility to wp_filesize() tests – #57171
  • Add unit tests for attachment’s file size being included in metadata – #57171
  • Clean up test file in wpmu_delete_blog() tests – #56793
  • Correct references to set_up() and tear_down() in various DocBlocks – #56793
  • Move wp_filesize() tests to their own file – #57171

Props

Thanks to the 34 people who contributed to WordPress Core on Trac last week: @sergeybiryukov (6), @mukesh27 (5), @audrasjb (5), @costdev (4), @sabernhardt (3), @upadalavipul (3), @krupalpanchal (2), @spacedmonkey (2), @pbearne (2), @poena (2), @laurelfulford (1), @jigar-bhanushali (1), @ironprogrammer (1), @bonjour52 (1), @jorbin (1), @johnwatkins0 (1), @adamsilverstein (1), @ptahdunbar (1), @WoutPitje (1), @mitogh (1), @sruthi90 (1), @anantajitjg (1), @aparnajl (1), @emanuelx (1), @TobiasBg (1), @swissspidy (1), @mehulkaklotar (1), @alberuni-azad (1), @jrf (1), @riccardodicurti (1), @mahekkalola (1), @haritpanchal (1), @scruffian (1), and @petaryoast (1).

Congrats and welcome to our 5 new contributors of the week: @bonjour52, @sruthi90, @aparnajl, @emanuelx, @mahekkalola ♥️

Core committers: @audrasjb (13), @sergeybiryukov (12), and @bernhard-reiter (1).

#6-2, #core, #week-in-core

Editor Chat Agenda: November 30, 2022

Facilitator and notetaker: @fabiankaegy

This is the agenda for the weekly editor chat scheduled for Wednesday, November 30th 2022 at 15:00 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/.

General Announcements and Links.

Gutenberg 14.6.1 was released on Nov. 25
Gutenberg Plugin 14.7 RC1 is to be released on Nov. 30, 22

Key project updates

Task Coordination.

Open Floor – extended edition.

If you cannot attend the meeting, you are encouraged to share anything relevant to the discussion:

  • If you have an update for the main site editing projects, please feel free to share it 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: 29 November 2022

Here is the agenda for this week’s performance team meeting scheduled for November 29, 2022, at 16:00 UTC.


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

Proposal: Amend the Inline Documentation Standards for multi-line comments

This is a small proposal to amend the standards for multi-line comments. The current standards seem to require that multi-line comments have to be done like this:

/*
 * This is a comment that is long enough to warrant being stretched over
 * the span of multiple lines. You'll notice this follows basically
 * the same format as the PHPDoc wrapping and comment block style.
 */

There is also a warning that they must not begin with /** as that is the DocBlockdocblock (phpdoc, xref, inline docs) syntax, and may result in parsing errors.

The proposal is to remove this requirement and to encourage multi-line comments to be done with slashes, same as single-line comments.

// This is a comment that is long enough to warrant being stretched over
// the span of multiple lines. You'll notice this follows basically
// the same format as the single-line comment style.

Reasons:

  • Reduce possibility of typos and eventual parsing errors. This is not just from typing, seems many modern IDEs can auto-complete or auto-correct /* to /** which may lead to more typos.
  • The de-facto 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/. coding standard Prettier, and the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher’s PSR-12 do not enforce specific comment styles.
  • In addition to encouraging typos, the current standard is visually very close to the DocBlock standard which may lead to a moment of confusion when reading the code (uh, is this an incomplete DocBlock that doesn’t have @since and @param?).

#proposal

Dev Chat summary: Wednesday, November 23, 2022

The weekly WordPress developers chat meeting was held in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of 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/. at 20:00 UTC.

Agenda followed.

Start of the meeting in the core channel of the Make WordPress Slack.

Summary from November 16, 2022 dev chat.

1) Announcements

Slack link.

  • What’s new in Gutenberg 14.6 has been published.
  • Support will end for WordPress 3.7 – 4.0 on December 1, 2022. The last release party for these versions will be on November 30, 2022. More in the post.
  • The WordPress developer blogblog (versus network, site) is in public 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.. Contributors needed. For more information please contact @bph or join the #core-dev-blog channel in the Make WordPress slack. Update post.
  • The call for nominations for 2023 Core Team Representatives is open until December 2, 2022. Self-nominations are welcomed.
  • DevHub is getting a new look. Feedback from developers needed, particularly on the way documentation has been split and the way 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. changed inside the articles in the code reference. Please comment in Figma or on this post from the documentation team.

2) Blog posts of note

Slack link.

3) Upcoming releases

Slack link.

The next major is 6.2; the next minor is 6.1.2. Look for updates next week.

4) Components and tickets

Slack link.

a) Components

No major news this week for these components:

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

Help needed with onboarding new maintainers. If you’re a maintainer with tips you can share and/or are willing to let someone shadow you, please contact @marybaum

b) Tickets

@helen highlighted ticketticket Created for both bug reports and feature development on the bug tracker. #57187 for people who had particular experience in containers.

5) Open Floor

Slack link.

No issues were discussed.

Props to to @marybaum and @webcommsat for facilitating; to @DavidPotter for the summary, and to @webcommsat and @audrasjb for reviewing; and to @estelaris, @audrasjb, @azaozz, and @sergeybiryukov for participating.

#6-2, #dev-chat, #summary