Editor Chat Agenda 27 May, 2020

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

This is the agenda for the weekly coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor chat scheduled for Wednesday, 27 May, 2020, 10:00 AM EDT. This meeting is held in the #core-editor 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/. channel.

WordPress 5.5 Upcoming Release — Planning Roundup
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/ version 8.2 — RC 1 Available
Monthly Plan
Task Coordination
Open Floor

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, #editor-chat, #core-editor-agenda

Zebulan Stanphill 3:17 am on May 26, 2020

Finished some PRs and got them merged over the past week. Most notably:

Add RichText split-at-end/merge/remove behavior.
https://github.com/WordPress/gutenberg/pull/21764

Add usePrevious hook to @wordpress/compose package.
https://github.com/WordPress/gutenberg/pull/22540

As for PRs that are still WIP or awaiting reviews:

Heading 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. level control revamp PR has been improved and looks ready to merge.
https://github.com/WordPress/gutenberg/pull/20246

PR to replace instances of Lodash.includes with native JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. [].includes in the block-editor package is awaiting reviews.
https://github.com/WordPress/gutenberg/pull/21063

PR to refactor ReusableBlockEditPanel to use ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. is still waiting for reviews.
https://github.com/WordPress/gutenberg/pull/21181

I’ve been maintaining the Table of Contents block PR and making slight code quality improvements here and there. But it hasn’t really had any feedback to progress for around 20 days. I simply can’t progress without technical help/feedback. Would also appreciate some general feedback on potential naming changes, as well as 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) feedback to make sure the current markup makes sense.
https://github.com/WordPress/gutenberg/pull/21234

Great feedback/help has been provided to the Reusable Block edit component refactor/bugfix PR. It’s made some great progress, but there is still one noticeable behavior issue that I need help to resolve.
https://github.com/WordPress/gutenberg/pull/21427

Polish Custom HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. block PR is ready to go, assuming the stylistic changes are okay. Ideally, the block’s HTML view should look just like the Edit as HTML view on most blocks; yet the Edit as HTML view arguably doesn’t look as good as it should. Please provide design feedback.
https://github.com/WordPress/gutenberg/pull/21711

I also have a PR that was attempting to update the Quote block to use a light block wrapper, but I got completely stuck due to complications with the BlockQuotation component used to make the block edit component work on both web and native mobile. I need technical help to progress. It’s a difficult problem, but solving it will also solve how to convert other blocks to use light block wrappers.
https://github.com/WordPress/gutenberg/pull/22157

Another stuck PR is one to add color controls to the List block. It isn’t working on most default WordPress themes due to style conflicts. No idea how to get it working.
https://github.com/WordPress/gutenberg/pull/21387

Overall, several PRs have made significant progress thanks to your help/feedback. Others are still stuck where they were a week or two ago, but I’m sure there will be time for them once more pressing projects are tackled.

I’d like to express my thanks to everyone who has helped so far! Several PRs that I thought were ready turned out to have a few minor issues pointed out to me, and I’ve gained a good amount of experience through the maintenance of all these PRs and the feedback provided by various people. Again, thank you!
- Zebulan Stanphill 11:48 pm on May 26, 2020
  
  The Heading level control revamp PR just got merged! I’ve now begun work on a PR derived from the work in https://github.com/WordPress/gutenberg/pull/14889 to add a heading level checker to 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. to encourage more semantic heading level choices.
  
  https://github.com/WordPress/gutenberg/pull/22650
- Paal Joachim Romdahl 7:45 am on May 27, 2020
  
  Good going Zeb! Thanks for sharing the update!
Paal Joachim Romdahl 8:42 am on May 27, 2020

This is an important document for people to know about. As each of us have areas of focus that we can easier help out in. Listing our names in the document can help when someone creates a PR. As one will from the list understand who they can 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.” to get some help and/or a review.
https://github.com/WordPress/gutenberg/blob/master/.github/CODEOWNERS

Comments are closed.

Welcome!

Communication

Share this: