twstokes 3:29 pm on November 3, 2023
Tags:   

Mobile Team Update – November 3rd

WordPress iOSiOS The operating system used on iPhones and iPads. and Android version 23.6 is available for testing. Sign up here to join the 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. program on iOS or follow this link on your Android device, tap on “Become a beta tester”.

Highlights for the last two weeks:

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:

  • Fixed a bug where the Social Icons block wasn’t always visible
  • Fixed an issue where the title section of Synced Patterns wasn’t always visible
  • The option to convert the Classic block’s content to blocks is now available

#mobile

Josepha 4:22 pm on November 4, 2022  

Site Editor: a More User-Friendly Name

In July 2022, the WordPress community participated in a lively discussion around a more user-friendly name to give the suite of features and tools known as Full Site Editor. With community feedback in mind, it will simply be referred to as the “Site Editor,” going forward. Thank you to everyone who voiced their points of view on a topic that touches every part of 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.

Landing on Site Editor was the result of two key considerations. Firstly, Site Editor offers a clear and simple description to users with a range of technical skills. Secondly, there was substantial support for Site Editor, particularly from the Polyglot community, as the term that translates most effectively into hundreds of different languages. As we heard at WordCamp US 2022, better multilingual support is an important future direction for WordPress, so choosing easily translated terms is an important step. 

Site Editor also keeps the spirit of its original FSE codename as the powerful, full collection of features it encompasses. As a bonus, it also doesn’t cost us anything from an SEO or marketing standpoint, since it’s a simplification of the existing term. 🙂 

You’ll still see or hear instances of FSE around. There is no need to erase it from our story. Going forward, you’ll hear more people and 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/ announcements refer to the Site Editor. You’re invited to begin using the term Site Editor immediately and update areas within the documentation to reflect that change.

p.s. – Is this a rebranding? I wouldn’t say so, myself. FSE was an easy way to refer to a complex, new thing and didn’t make much sense as a branded term. This is just an update to the way we’re talking about that complex thing.

Props to the community members who posted here for voicing their thoughts on giving the Site Editor its new and user-friendly name and to @angelasjin @cbringmann and @jpantani for their editorial efforts!

Paco Marchante 10:22 pm on November 7, 2023
Tags:   

Plugin Review Team: 07 November 2023

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 Status Change Stats

  • Plugins requested : 100
  • Plugins rejected : 0
  • Plugins closed : 44
  • Plugins approved : 40

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 2430
    • (older than 7 days ago)** : 2278
    • (2023-10-23 – 2023-10-29) : 107
    • (new; not processed or replied to yet)* : 1048
    • (pending; replied to)* : 1382

Help Scout Queue Stats

  • Total Conversations: 468
  • New Conversations: 203
  • Customers: 417
  • Conversations per Day: 58
  • Busiest Day: Friday
  • Messages Received: 328
  • Replies Sent: 349
  • Emails Created: 101

#plugins

Emily Clarke 2:45 pm on October 31, 2023
Tags: ,   

Core Performance Team Update: October 2023

Tickets and contributions

The Performance Team works on performance-related tickets in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and holds a fortnightly Bug Scrub on Wednesdays; check https://make.wordpress.org/meetings/ for current time.

The focus in October was on tickets prioritized for the upcoming WordPress 6.4 release in which 68 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets were merged. Several follow up fixes were committed in the past few weeks to further polish performance enhancements in the 6.4 release. Early indications of benchmarking are showing positive improvements in performance, especially in server response time. The team focused on finalizing dev notes for the work:

The Performance Team is now starting to focus on upcoming tickets for WordPress 6.5, including the Performant Translations work mentioned below, and several items for improving template loading (see GitHub overview issue).

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 Checker

The Performance Team has continued work on the Plugin Checker https://github.com/WordPress/plugin-check, working closely with the Plugin Review team. 

Performant Translations Plugin

Further updates have been made to the Performant Translations plugin and a Trac ticket #59656 has been opened for merging Performant Translations in WordPress 6.5.

Team headlines and updates

In October, the Performance Team held a Hallway Hangout to discuss WordPress 6.3 performance impact in the field, diving into WordPress 6.4 performance improvements and looking ahead at what can be learned for WordPress 6.5. The recording of the video will be shared over the coming weeks.

Performance Lab Plugin

Performance Lab plugin updates are released monthly on the third Monday of the month.
October’s release 2.7.0 included enhancements to remove fetchpriority as the functionality is now available in WordPress Core, bumped the minimum required PHP version to 7.0 and minimum required WordPress version to 6.3 and the dominant color images standalone plugin was published. Work also continues on updating the new UI to manage standalone plugins and built-in modules.

#core-performance, #performance

Milana Cap 11:05 am on November 6, 2023
Tags:   

Documentation Team Update – November 6, 2023

The Documentation team has a new meeting schedule:

A new GitHub repo is created for end-user documentation and its translations to all locales. More info about this can be found here.

Documentation Issue Tracker stats.

Current state

By status:

By version:

By project:

Past 7 days

6 pull requests merged:

3 issues closed:

38 issues opened:

46 unresolved conversations

Current projects:

The Documentation team repositories:

#docs

Ankit K Gupta 7:32 am on October 30, 2023
Tags:   

Test Team Update: 30 October 2023

Test Ticket Queue 🎟

👉🏻 “(change: N)” represents changes from prior week (unless noted).

📊 Current totals (since 16 October 2023):

  • Need testing info: 17 (change: +0)
  • Need reproduce issue: 2040 (change: +9)
  • Need patch testing: 206 (change: +2)
  • Need unit tests: 113 (change: +1)
  • Need review (have patch and unit tests): 157 (change: -4)

🟢 New/Changed last week:

  • Need testing info: 1 (change: +0)
  • Need reproduce issue: 15 (change: +6)
  • Need patch testing: 3 (change: -15)
  • Need unit tests: 1 (change: +0)
  • Need review (have patch and unit tests): 6 (change: -10)

🟣 Closed last week:

  • Need testing info: 0 (change: +0)
  • Need reproduce issue: 3 (change: -3)
  • Need patch testing: 4 (change: -2)
  • Need unit tests: 0 (change: +0)
  • Need review (have patch and unit tests): 19 (change: -11)

To discuss queries used in this report, please comment below, or connect with the Test Team over in #core-test.

+make.wordpress.org/test/

#test

twstokes 4:05 pm on October 17, 2023
Tags:   

Mobile Team Update – October 17th

WordPress iOSiOS The operating system used on iPhones and iPads. and Android version 23.5 is available for testing. Sign up here to join the 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. program on iOS or follow this link on your Android device, tap on “Become a beta tester”.

Highlights for the last two weeks:

  • 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:
    • A formatted block can be split or exited by pressing Return three times
    • Fixed an issue where the Quote block’s left border could be invisible

#mobile

Milana Cap 9:44 am on October 23, 2023
Tags:   

Documentation Team Update – October 23, 2023

The Documentation team has a new meeting schedule:

A new GitHub repo is created for end-user documentation and its translations to all locales. More info about this can be found here.

Documentation Issue Tracker stats.

Current state

By status:

By version:

By project:

Past 7 days

2 pull requests open:

34 issues closed:

44 issues opened:

94 unresolved conversations

Current projects:

The Documentation team repositories:

#docs

Emily Clarke 4:27 pm on June 29, 2023
Tags: ,   

Core Performance Team Update: June 2023

Tickets and contributions

The Performance Team works on performance-related tickets in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and holds a fortnightly Bug Bash on Wednesdays; check https://make.wordpress.org/meetings/ for current time.

For the upcoming WordPress 6.3 release, the WordPress performance team has been focusing on closing several issues for the 6.3 release.

The Performance Team is happy to be able to report that the PR for #12009 was committed to WordPress core, closing a 13 year old ticket. This is a big milestone for the team, thank you to everyone who contributed to get this across the line. There is still a desire to extend support to inline scripts, so a new ticket has been opened (#58632) for that discussion, and several use-cases for the new 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. across WordPress core and 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/ are being discussed.

Additionally, the team is excited to share that we landed fetchpriority=”high” support #58235 in WordPress core. The commit [56037] includes notable refactoring to make the logic that was previously scoped to only lazy-loading more broadly available, as it is also required for fetchpriority. With that refactoring it also unblocks a fix to another issue that still needs to be addressed with lazy-loading: #58635

Both of these performance enhancements will launch as part of the upcoming WordPress 6.3 release.

For raw performance enhancements, 3 major highlights are:

  • Emoji loader script causes ~100ms long task #58472 (~20% LCP improvement, committed in [56074])
  • Performance issue in register_block_style_handle function #58528 (~30% server response time improvement for blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. themes, committed in [56044])
  • Improve performance of get_block_templates function #57756 (~15% server response time improvement for block themes, committed in [55687])

The Plugin Checker engineering has been completed for milestone 2 which now also includes additional checks. Progress can be seen in this GitHub repo, which eventually should be transferred to the WordPress organization. 

Team headlines and updates

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 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/. was a great success – thank you to those who joined! There were 2 performance tables this year; the first focused on the script loading strategy API testing the PR by modifying some plugins and core code to use it, and the second focused on profiling and benchmarking. 

Several new articles were added to the Performance Handbook this month:

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

Performance Lab plugin updates are released monthly on the third Monday of the month.

May’s release 2.4.0 includes further enhancements to creating stand-alone plugins and infrastructure, as well as some small bug fixes. 

The Performance Lab plugin has also reached 80k active installations this month!

#core-performance, #performance

Josepha 6:48 pm on March 16, 2021  

Proposal: A WordPress Project Contributor Handbook

There have been many times over the past six years where I reviewed new content going into a team’s handbook, and thought that it really should be in a big “WordPress Project Handbook”. It’s generally content around underlying philosophies or commitments to do (or not do) something, but ultimately shared expectations of how we, as contributors, work together, who we want to build our products for, and the WordPress interpretation of modern, 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. best practices.

As I’ve watched many working groups come together to create sections of this handbook, it occurred to me that speaking “on behalf of WordPress contributors” is never an easy task, and certainly not one that is made easier by trying to create a handbook by committee. That doesn’t make a handbook like this less vital, but it does make the responsibility much more heavy.

That level of responsibility is something that falls into my job description, so I will take on the responsibility for a first draft. I plan to include the following sections:

  • Community Code of Conduct
  • 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) Policy
  • Diversity and Inclusion Policy
  • Privacy Policy
  • Conflict of Interest Policy
  • Code of Ethics

This would be a handbook outside of individual team handbooks, and will grow to include other foundational content (i.e. the GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. primer, open source leadership resources, etc.).

Next Steps

  • I will coordinate a v1 of this handbook as a starting point.
  • I will share the v1 with former members of those working groups, so that we don’t lose that institutional knowledge.
  • A call for feedback will be posted so that refinements can be made.