Components Maintainers and Gutenberg

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.

In this week’s DevChat, @jeffpaul asked:

One thing I’ve become curious about is how some components should potentially be looking to support current/future phases of 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/? Thinking here about CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., Widgets, Menus, and the like. Is there anyone on the Gutenberg team that’s working with those components to see how those maintainers/contributor teams could help advance Gutenberg development from their unique perspective from a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. component team?

Some discussion ensued, but it’s an important topic that’s worth discussing in an asynchronous forum where people from all timezones can participate.

So: How do we ensure that there is good collaboration between Component Maintainers and the Gutenberg project?

tellthemachines 4:29 am on February 21, 2020

This is an important question! I have some thoughts:

1. It’s hard to map components to 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/ because Gutenberg isn’t clearly divided into components. It might have started out as roughly under the editor component, but it has expanded to be much more than that.

It would be helpful, to start with, if we could have as clear as possible a mapping of components to their relevant parts of Gutenberg. In some cases, we can map components to specific packages, say Build/Test Tools to `wordpress/scripts` and `wordpress/e2e-tests`, but for others there’s no direct correspondence to packages. For some perhaps we can still find some relevant grouping of labels on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.

2. Pace of development in Gutenberg is fast, so it’s hard to stay on top of things.

It could be useful for Gutenberg devs to publish periodic overviews of what’s being done and what’s important to keep track of for each component (where relevant, of course). Following on from point 1., if we roughly divide Gutenberg into “components”, perhaps we can assign maintainers to each of them, whose responsibility it would be to create these documents.

3. We already have a list of points of contact for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. components, so another benefit of official maintainers on the Gutenberg side would be having a handy list of people that core component maintainers (and others!) 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.” if they want to get more involved with the Gutenberg side of their component.

4. When there is lots happening for a given component across core and Gutenberg, it also might be good to set up a couple of component-specific meetings for knowledge exchange.

5. Eventually, the aim would be for core and Gutenberg components to merge. These ideas should work as steps in that direction, not as a further divide between both codebases.
Andrea Fercia 7:58 am on February 21, 2020

> the aim would be for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/ components to merge.

Yup, I’d tend to think removing the de facto separation between core and the Gutenberg project would be a good first step.
David Herrera 6:13 am on February 24, 2020

I’m a maintainer of the Customize component, but I’m speaking for only myself here.

It would be great for the 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/ team to help focus attention on the most important issues related to the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. by dropping links to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ issues or pull requests into #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-customize now and then.

Now that I know about the Customization label on GitHub, I’ll try my best to keep pace with that as well. Or, I don’t mind being tagged directly in GitHub — I’m @dlh01. But it’s already part of my routine to keep an eye on #core-customize, so Gutenberg links put there will quickly appear on my radar.

As @tellthemachines said, Gutenberg is so incredibly active (which is great!) that it can feel like all the time I have to dedicate to core would just go into reading all the discussions I’ve missed. Anything at all that the Gutenberg team can do to act as a funnel would be of great aid.

Comments are closed.

Welcome!

Communication

Share this: