Editor chat summary: Wednesday, 29 June 2022

This post summarizes the weekly editor chat meeting on Wednesday, 29 June 2022, 14:00 UTC held in Slack.

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/ 13.6 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).

@jorgefilipecosta Released Gutenberg 13.6 RC today. The release could be downloaded at https://github.com/WordPress/gutenberg/releases/tag/v13.6.0-rc.1. The changelog could also be checked on the same link.

WordPress 6.0.X

Information related to future 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. releases of 6.0 can be checked on https://make.wordpress.org/core/2022/06/25/wordpress-6-0-x-release-team-and-6-0-1-schedule/.

On the editor side @zieladam is going to help with 6.0.1 for future releases there is an opening if someone is able to help.

WordPress 6.1

The planning post for WordPress 6.1 is available at https://make.wordpress.org/core/2022/06/23/wordpress-6-1-planning-roundup/. There are some positions opened on the release squad so if something interests feel free to volunteer in that post.

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. 1 & Feature Freeze is scheduled for September 20, 2022.

Key project updates

Building with patterns & Styles

Now we have the ability to use start patterns on a modal on other post types besides pages https://github.com/WordPress/gutenberg/pull/41791. A much-requested feature.

@jorgefilipecosta proposed PR to target descend 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. styles in a block using s shape equivalent o theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. on https://github.com/WordPress/gutenberg/pull/41922. It allows more styling flexibility when building a pattern.

Task coordination

@get_dave

@jorgefilipecosta

  • Previously:
    • Proposed a mechanism to allow the usage of the start post pattern modal on other post types besides pages.
    • Added an 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. to allow a pattern to be restricted to some post types
    • Proposed an API to allow blocks to style their descendent blocks.
    • Multiple 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, code enhancements, and reviews.
  • Future:
    • Implement the rendering of block-level presets.
    • Help the effort to expand the templates that can be created on the site editor.

@mamaduka

Is looking for technical feedback/review for my new PR to allow locking inner blocks from the container block – https://github.com/WordPress/gutenberg/pull/41876.

Open Floor

Toolbar regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.

@get_dave said that the toolbar has suffered a regression whereby it now obstructs blocks that are at the top of the viewport. The Nav block is badly affected by this. If anyone is available to work on this that would be great. I know @talldanwp has also promised to give it some attention.

@jorgefilipecosta asked if already know the PR that caused the regression. @get_dave said the popover component upgrade is the probable cause and added @talldanwp is investigating.

Weekly bug scrub

@NickDiego shared in the meeting that now we are now holding weekly Editor Bug Scrubs at 1400 UTC on Tuesdays here in #core-editor he and @mamaduka held the first one this week. Everyone is encouraged to participate and help on the weekly bug scrubs.

Request for RTL testing

@poena said:

There is a PR for RTL styles that could use more testing by someone who uses an RTL language as their default for the editor:

https://github.com/WordPress/gutenberg/pull/41762

So if you usually use RTL language your help is greatly appreciated.

#agenda, #core-editor, #editor, #summary

Making the Tech Editor Release Lead Role More Creative and Less Repetitive

Merging 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/ to WordPress on major releases is now more automated than ever.

@zieladam (me) and @gziolo were the tech editor release leads for WordPress 6.0. We’ve quickly noticed that ~30% of the role is about communication and decision making, while ~70% consists of repetitive weekly chores. We want to reverse these proportions.

Most repetitive work falls into one of the two categories:

  • Backporting PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes made in the Gutenberg 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 since the previous major WordPress release
  • Releasing weekly 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./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). versions

Backporting PHP changes made in the Gutenberg plugin since the previous major WordPress release

Finding and backporting all the PHP Pull Requests merged to Gutenberg but not to WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is a huge task.

For WordPress 6.0, it took us two days just to prepare the list. From there, it was two weeks of pinging, coordinating, reviewing, and merging code before we were done. Furthermore, not all the authors had the availability to help at that point in time.

This cannot be easily automated, but imagine the alternative: Gutenberg developers prepare PRs against WordPress core in parallel with merging their Gutenberg PRs. Any integration issues get surfaced right away, there are fewer merge conflicts, and the release leads don’t have to spend two weeks investigating the commit history and pinging code authors. The future availability of the developers isn’t a problem anymore either.

If that sounds appealing, come and speak up in the ongoing GitHub discussion!

Releasing weekly Beta/RC versions

The weekly release consists of four repetitive tasks:

  • Cherry-pick triaged code to a Gutenberg release branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".
  • Release Gutenberg @wordpress packages from that branch
  • Update the version of packages used in wordpress-develop
  • Manually stabilize any blocks to be included in the new release

@zieladam (me) and @gziolo added a degree of automation to all of the above.

Cherry-pick triaged code to a Gutenberg release branch

Bringing Gutenberg Pull Requests over to WordPress after Beta 1 requires cherry-picking the relevant commits.

Before, this involved manually resolving conflicts and letting the author know. A few times I got confused and spent more time on it than I hoped to.

Today, the new npm run cherry-pick script automates all of that (except resolving conflicts). Furthermore, it can be repurposed for the Gutenberg plugin releases.

Publish the updated @wordpress packages from the release branch

After cherry-picking the relevant changes to the release branch, the way to bring these changes to WordPress core is through npm packages.

Before, it took publishing permissions, a specific local setup, and remembering the correct command with the proper CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. parameters. With all that in place, you ran the built process, waited a longer while, and then published the packages.

Today, this entire process can now be triggered directly from GitHub UI after approval from any Gutenberg core team member.

Update the version of packages used in wordpress-develop

With fresh @wordpress packages published to the NPM registry, the next step is to update the dependencies in wordpress-develop.

Before, it involved a manual synchronization of the new Gutenberg dependencies with the package.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. file shipped in wordpress-develop. You had to add any new dependencies, update the versions of the existing ones, and delete ones that were no longer used.

Today, the new sync-gutenberg-packages console task automates this effort.

Manually stabilize any blocks to be included in the new release

Finally, a number of steps are required to enable the new stable blocks in WordPress core.

Before, you had to manually list the new blocks in a few .php and .js files and double- or triple-check whether all these lists are in sync. As there are other build steps at play, the resulting Pull Request is quite large. Even though @zieladam and @gziolo were careful, we still ended up making mistakes.

Today, the new sync-stable-blocks console task reduces the entire process to running a single command. All the relevant lists are generated automatically making the process easier and removing any chance for human error.

Next steps

Wiring the above automations to run sequentially would streamline the entire process to a single click of the button:

  • Take a list of Gutenberg PRs as an input
  • Create a Pull Request against wordpress-develop as an output (example)

With the caveat that merge conflicts would still have to be resolved manually.

I’d love to inspire the next release squad to explore this during the 6.1 release cycle.

By simplifying these two large areas, I believe we can truly make the Tech Editor Release LeadRelease Lead The community member ultimately responsible for the Release. role mostly about the decision, communication, and creative work without so many repetitive tasks.

Props to Héctor Prieto (@priethor) and Grzegorz Ziółkowski (@gziolo) for their help in putting this post together.

#6-0-1, #6-1, #core, #core-editor, #gutenberg

Editor Chat Agenda: 29th June 2022

Facilitator and notetaker: @jorgefilipecosta.

This is the agenda for the weekly editor chat scheduled for Wednesday, June 29, 2022, at 03:00 PM GMT+1. I

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

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

Editor chat summary: June 22, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, June 22. 2022, 03:00 PM GMT+1 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/.. Moderated by @fabiankaegy.

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

Gutenberg 13.5 got released by @annezazu. You can find the Changelog in the What’s new in Gutenberg 13.5? (22 June) post.

WordPress 6.0.1

WordPress 6.0.1 project board

Key project updates

The list of GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ tracking issues was updated to reflect the updated Roadmap for Gutenberg Phase 2 for WordPress 6.1 Matias Ventura published earlier this month.

Task coordination

Nothing was discussed during the meeting.

Open floor

@andrewserong

Shared an update on some of the work they’ve been doing to explore a potential path forward for refactoring how the Layout 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. support works.

@ramonopoly

Shared an update about the work on the Fluid Font Size feature.

@daveloodts

Asked a question regarding styles that get added for image alignment in the editor.

@mamaduka

Shared a Proposal for Weekly Editor Bug Scrubs

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Block editor styles: initiatives and goals

The CSSCSS Cascading Style Sheets. rendered by the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor needs improvement.

The challenges are many and they have been documented. There are, nevertheless, several recurring themes:

  • An overabundance of rendered inline style tags and duplicated CSS rules. For example, see #41434.
  • Confusing or meaningless classnames, or the lack of semantic and utility classes. See the proposals in #38719 and #38998
  • Difficulty extending and customizing styles for themes due to high specificity. Touched upon in this post, and demonstrated in issues such as #40159, #36135 and #37590.

The purpose of this post is to highlight ongoing initiatives targeted at addressing these issues, and to outline longer-term ambitions to output more readable, efficient and extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. frontend styles. 

Roadmap

Phase 1: block styles consolidation and refactoring the layout abstraction

Goals:

  • To audit and consolidate where the code generates block support CSS in the backend so that they are delivered from the same place (as opposed to multiple places). This covers CSS rules such as margin and padding, typography, colors and borders. 
  • Removing repetitive layout-specific styles and generating semantic class names for each layout. 

Phase 1 is currently underway. 

The focus in Phase 1 has been to lay a foundation that will make it easier to introduce iterative improvements. 

Rather than printing block styles on demand from multiple locations, the focus is to create a single, centralized agent responsible for generating them, and, in later phases, assume the responsibility of processing and rendering better frontend CSS.

Work on this has started and is progressing well. See Tracking: Add a Style Engine to manage rendering block styles #38167.

A pull request that reduces rule duplication and institutes semantic class names for the layout block support is ready for review. It also centralizes layout definitions, which will pave the way towards adding additional layouts in the future.

See: Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875

Phase 2: global styles consolidation and reducing style tags

Goals:

  • Connect global styles to the same mechanism with which we’re generating block styles.
  • Reduce the number of inline style tags we print to the page for block, layout and elements support.
  • For layouts, use a presets-like approach to generate semantic class names for attributes of layouts.

Building upon Phase 1, the outcome of this phase is to have a single styles “generator” capable of building CSS for both block and theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML./global styles.

In Phase 2, the objective is to explore how we can leverage this consolidated system of style generation by first grouping, then rendering a minimal set of style tags to the page. 

This includes, for example, moving block supports styles such as layout and elements to a single style 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.), then identifying other candidates for optimization.

There are already some very early, investigative PRs:

With regards to layout support, extending the group of semantic/utility classes to combine common attributes such as content justification and orientation, further reducing repetitive layout-specific styles.

Phase 3 and beyond

Proposed goals (in no particular order and not exclusive):

  • Continue with style consolidation, address edge cases or unique blocks that require special handling, such as the Gallery block.
  • Explore pre-render CSS rule processing with the intention of deduplicating other common and/or repetitive block styles.
  • Extend the scope of semantic class names and/or design token expression, and encapsulate rules into stable utility classes.
  • Establish and document standards by which to extend/override CSS.
  • Propose a way to control hierarchy and specificity, and make the style hierarchy cascade accessible and predictable. This might include preparing for cascade layers until they become more widely supported, and allowing for opt-in support 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/ via theme.json.
  • Allow for rendering styles in asynchronous contexts. See #35376

The intention is to publish GithubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ discussion threads for these topics to gather ideas and feedback.

How we’re going and how we’ll get there

The expectation is for the layout refactor and much of the styles consolidation work mentioned in Phase 1 to ship in WordPress 6.1

Phases 1 and 2 aim to ameliorate pain points, and also set things up for future enhancements in Phase 3++.

Style nirvana might well be out there, however the path comprises individual stepping stones, discovering how individual parts contribute to the whole, and balancing compatibility and stability with innovation.

If we can keep refining and narrowing the scope, shipping in stages, and laying out the foundations, I think we’ll be in a better position to manage the risks and challenges and greatly improve the condition of our rendered styles and frontend output. 

Thanks to all the folks who have shared their wisdom so far. ❤️ If you’d like to contribute, or have feedback or ideas on present or future initiatives, please leave a comment on one or all of the ongoing projects I’ve linked to in this post. 

Acknowledgements: This post was co-authored with @andrewserong and @isabel_brison, with the assistance of @apeatling and @matveb.

#core-css, #core-editor, #gutenberg

Editor chat summary: 15 June, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, June 15 2022, 03:00 PM GMT+1 in Slack. Moderated by @bph.

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/ 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 releases

Latest release Gutenberg 13.4

Gutenberg 13.5 RC 1 as released shortly after the meeting by @annezazu – Final release scheduled for Jun 22.

WordPress 6.0.1

WordPress 6.0.1 project board

Key project updates

The list of GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ tracking issues was updated to reflect the updated Roadmap for Gutenberg Phase 2 for WordPress 6.1  Matias Ventura published earlier this month.

Thank you for updates 
@siobhyb for the Mobile Team update
@getdave for the Navigation Block update

Task Coordination

@siobhyb

We’re currently making plans for Q3 on the mobile team, but it’s likely that we’ll have a focus on maintenance and fixing existing bugs.

@mamaduka

I’m mostly catching up on GitHub notifications after WCEU and my vacation. I’ll be focusing on PR reviews this week.

Open Floor

Announcements, questions, and discussions.

@hellofromtonya

Mentioned on the discussion on how to do faster, more frequent minor releases in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to ship fixes faster. Here a few links:

Next steps suggested by @hellofromtonya

  • Form the 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. squad > folks need to raise their hands (#6-0-release-leads channel)
  • list of pain points, bottlenecks, and ideas could be generated and then shared for discussion with the minor release squad

6.0 retrospective is still on its way. Deadline Jun 19th.

@johnstonphilip

Requested help to making sure duotone code is not present on the page unless required? (PR #38299) After the meeting, @skorasaurus chimed in

@alexstine

Needs technical feedback on this proof of concept PR for accessibility, even if it’s not a full code review “getting some input on if it is a good idea or how to make it a better idea would be great.” Stine wrote.
Related discussion: Improve keyboard navigation experience in all the block editors.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor Chat Agenda: June 22, 2022

Facilitator and notetaker: @fabiankaegy

This is the agenda for the weekly editor chat scheduled for Wednesday, June 22, 2022, 03:00 PM GMT+1. It follows the proposed new format with more emphasis on the Open Floor discussion.

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

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

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

Proposal: Editor Weekly Bug Scrubs

This post is a proposal to start weekly Editor Bug Scrubs in #core-editor the week of June 28th. The scrubs will have a singular focus on issues in the Gutenberg GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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. If you have feedback, please comment by June 24th, 2022.

Overview

New in the WordPress 6.0 release cycle, the role of Editor Triage Lead triages 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/ issues in the release and, to that end, runs weekly 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 in #core-editor.

As the release progressed, it became clear just how valuable these weekly meetings were in moving issues forward. And as the launch drew near, George Mamadashvili (@mamaduka) suggested continuing the scrubs a weekly, regardless of the release schedule.

Gutenberg right now has more than 4,200 open issues, and the number grows faster by the month.

And that number, especially out of context, makes a fairly convenient data point for observers to cite as evidence the project is not production-ready. Now, the same records that show the issues also show that dozens of contributors regularly and actively triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. these issues.

But the process for working through any set of issues on GitHub or tickets on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. is informal — that is the nature of 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.. Which also means, therefore, that the process utterly depends on the interests and skillsets of those contributors who show up and do the work.

The result is an ad-hoc process that has produced hundreds of stale issues. Many of those are no longer relevant, but they stay open because nobody formally closes them. And truly important issues are at a nontrivial risk of slipping through the cracks.

Weekly bug scrubs will not single-handedly solve these problems. But they will dedicate a solid hour every week when team members (including you, who are reading this now!) get together, review issues, and make concrete plans to resolve them.

And during release cycles, the structure will give Editor Triage Leads a ready structure and a team of contributors to get more done, and produce a better experience, with every new version of WordPress.

Proposal

  • What will happen? An Editor Weekly Bug Scrub meeting, in #core-editor 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/., every Tuesday at 1400 UTC.
  • When will they start? The week of June 28, 2022.
  • How will people know they’re happening? The scrubs will be on the Meetings Calendar.
  • What will they cover? Bug scrubs will follow the normal process in the Handbook — but address only Gutenberg issues on GitHub. 
  • Who will run these scrubs? Members of the Gutenberg Triage Team. Nick Diego (@ndiego) and George Mamadashvili (@mamaduka) will run the first several. Then other team members will get onboarded for future sessions. 
  • How will they work with the release cycle?
    • As soon as the release squad has a designated Editor Triage Lead, that person will lead the meetings and tailor triage efforts to he release in progress. 
    • At launch, meeting leadership will go back to the Gutenberg Triage Team. Ideally, Editor Triage Leads will have come from the Gutenberg Triage Team, so that transition should be seamless.

Next Steps

So what do you think?

Please share your comments by June 24th. If the community agrees Editor Bug Scrubs would be a good thing, the first scrub will be Tuesday, June 28, 2022, at 1400 UTC.

Props to George Mamadashvili (@mamaduka), Justin Tadlock (@greenshady), Héctor Prieto (@priethor), and Birgit Pauli-Haack (@bph) for their help in putting this proposal together.

(Ed. note: Also, did you know that anyone can lead a bug scrub, for any reason? That means you! And you can focus your scrub on any tickets you like, or any Gutenberg issues. (The difference: most of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. runs on Trac, which uses tickets and patches. The blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor runs on GitHub, which uses issues and pull requests. – @marybaum)

#bug-scrub, #editor, #gutenberg

Editor Chat Agenda: 15 June 2022

Facilitator and notetaker: @bph

This is the agenda for the weekly editor chat scheduled for Wednesday, June 15 2022, 04:00 PM GMT+1. 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.

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

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

Thank you for review to @priethor

#agenda, #core-editor, #core-editor-agenda, #meeting

Editor chat summary: 8 June, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, June 8 2022, 03:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

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/ 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 releases

Gutenberg 13.4 was released 8 June.

WordPress 6.0.1

WordPress 6.0.1 project board

Key project updates

Task Coordination

No tasks shared.

Open Floor

Announcements, questions and discussions.

@ndiego

Highlight:
I would love to get some additional eyes on this issue: Backport fixes for wp/v2/block-patterns/patterns and /wp/v2/pattern-directory/patterns endpoints to Gutenberg issue. The related PRs need to be backported to Gutenberg and I am not sure what that process looks like.

Once these are backported, I have a fix for When removing core pattern, allow theme.json pattern slugs to be listed in inserter.

@luehrsen

Question:
I wanted to ask for guidance around this issue: Explore options to add back semantic classnames to block wrappers. Where can we help, what can we do to move this forward? This affects our day to day business, so we are more than happy to help. Especially since 6.0 rolled out features that ignore semantic classnames. (Group Row/Stack)

@torounit

Question:
PR: Migrate list block test to Playwright.
The e2e test passes on GithubGitHub GitHub is a website that offers online implementation of git repositories that can 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/-Actions, but when I run it on my machine some tests fail. ( tests with names starting with should undo asterisk transform with backspace )
This problem does not occur when I run step by step. ( use debug mode. )Adding new Promise( ( resolve ) => setTimeout( resolve, 300 ) ); to the line after createNewPost succeeds, but it doesn’t seem like a good way.
Is there a better way?

Question:
Do we still need wp.blocks in our documentation? PR: Add supports to basic sample code.
@import metadata “. /block.json” I thought it would be easier to understand.

@skorasaurus

Highlight:
I triaged the issue WP 5.9 adds default Duotones before closing the body there are users who feel burned about the decision that was made (to introduce duotones) and load them by default. Several users are still unsure how to dequeue/remove them. This is representative of a broader pattern where Gutenberg is introducing new features or options without the means of disabling them and the need to communicate these decisions more clearly.

We had multiple questions/comments during the Open Floor which still need feedback.

To get more details go directly to the Open Floor discussions in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor 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/. channel.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary