This post summarizes the weekly editor chat meeting on Wednesday, 29 April 2020, 14:00 UTC held in Slack.
WordPress 5.4.1
@jorgefilipecosta said WordPress 5.4.1 was released on the last Friday and that the RC includes all the editor fixes expected on the final release A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. Concluding that unless we discover something critical until the release in some hours, he does not expect any additional task on the editor side. The editor fixes included in WordPress 5.4.1 can be checked at https://github.com/WordPress/gutenberg/pulls?q=is%3Apr+sort%3Aupdated-desc+label%3A%22Backport+to+WP+Core%22+is%3Aclosed.
@jorgefilipecosta gave public kudos to @whyisjake or handling the tasks needed for the release!
Gutenberg 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/ 8.0.0
@aduth shared the following update regarding Gutenberg 8.0.0:
The release 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). was released on Monday. There were a couple of bugs that were discovered between then and today and will be included as part of today’s release. Everything is looking okay on my end as far as releasing Gutenberg 8.0 today.
@youknowriad shared that the highlights of the release are:
- Patterns moved to the inserter and the inserter as a panel
- Add subscript and superscript formatting options
@jorgefilipecosta said that the last core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. releases included ten Gutenberg releases. Gutenberg 8.0.0 is the fifth Gutenberg release since WordPress 5.4 so more or less half of the things WordPress 5.5 editor is going to include are already out.
Monthly Plan & Weekly Priorities
Soon we are going to have the monthly plan for may. Regarding the April plan available at https://make.wordpress.org/core/2020/04/01/whats-next-in-gutenberg-april/, @mapk said he thinks everyone did really well and @youknowriad agreed and said we’re on a good pace these days and we’ll need to start thinking about the High-level priorities for May.
Task Coordination
Has been working on some follow-ups to the Patterns and Inserter work:
- Support search
- Rename APIs
- Make A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the core patterns translatable
He said there are still a lot more follow-ups there. H will continue there and will also keep an eye on the FSE work in general.
Has been focused on:
- Block 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. context: The first iteration landed last week. It still needs follow-up work to flesh out the PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 APIs.
- 8.0 release: Wrangling, also made changes to and helped land a new changelog generator tool which will be helpful to expedite the process for future releases.
Has been involved in PR reviews and issue discussions in
- Pasting, transforms
- Block content, versions
- Full-site (versus network, blog) editing and block-based themes
In the past week, his main focuses were:
Next, he is going to resume work on the block style system, global styles, etc.
Has been focused on:
- Cover Block: Continuing work on padding controls and alignment tools
Working on the gallery, looking at keeping the current gallery block, while building out a pattern(s) for the gallery, as a container with block images. Working on the data flow, design flow, and then build out from there. 5.5 will have both the current gallery block, and the pattern gallery(ies).
Has been AFK for a week. Attended some of his open work about the new navigation menus screen, refactored the author block, and re-added setting post author from it.
Is working on Iterations on the welcome guide and will soon start helping with FSE work, mainly Inserting existing saved template parts and Edit Site: Creating a new template from scratch.
Is focusing on:
Is following up on a few PRs:
-
Clearing the publish date with @earnjam
- Labels on buttons with @nicolad
- Looking at drag n drop and mover interactions a bit more.
During the last week, helped/reviewed the tasks needed for 5.4.1. I submitted many bug 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 and also some enhancements to the widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. screen. For the next week, he wants to continue some enhancements to the widget screen and to work on undo-redo and make sure it works as expected on the three screens: edit-post, edit-site, edit-widgets (it seems we have some issues on the last two). Lastly, he plans to continue interactions on some PR’s he has, namely CSS Cascading Style Sheets. vars for predefined colors, as that PR is impactful for global styles.
Plans to continued on block editor features and last week did the following tasks:
- worked on CSS support for build and start commands from wordpress/scripts
- landed a few smaller bug fixes
- helped @ajlende to land debugging support for unit and e2e tests
Her main focuses are navigation and design triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.. Said that we are getting in a good place with nav-menus.php thanks to so much amazing dev work. Shared that the navigation project board is a great place for dropping in for feedback there and testing as the release surfaces.
Open Floor
Code debugging
@john said:
I’m confused about how to debug custom gutenberg blocks when you need to see and play with the gutenberg source code. If the docs are unclear, and I need to poke around in the source code, I can’t because all the packages are run via build files. So if I was to run a “console.log” to see what happens in the getSaveElement filter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.… nothing happens.
Is there a proper way to access the entire codebase so I can see what’s happening inside functions that gutenberg provides plugin 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 developers? I’m not skilled enough to just READ the code. I need to actually be able to run console.logs inside the Gutenberg core while developing a plugin. But I can’t find a way to do that.
@youknowriad referred that maybe nothing happens because it’s not executed at all. And made some questions to better understand the problem.
@aduth said:
@john Instead of using the plugin from the plugin repository, you can clone the source code from GitHub 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/ to your wp-content/plugins. From there, you can treat it like you would when developing in Gutenberg itself, starting the build process with npm run dev or npm run build from within Gutenberg. You should see any changes to the source reflected in the plugin running on your site.
https://github.com/WordPress/gutenberg/blob/master/docs/contributors/getting-started.md
Asset Licences
In the agenda of the meeting @poena said:
If there has not been one, there needs to be a license review of all third party assets.
I was not able to find any information for the included images (for example, block patterns and FSE demo content) and icons (social media).
Licence must be considered when any such element is included in the plugin.
I am not familiar with how you review licensing for third party scripts, but I am not able to find a list of licenses and copyright anywhere.
@aduth said that there is a license check tool used for all third-party dependencies installed through NPM. And @youknoriad said he knows that all images used in patterns and block examples are public domain images and that each time we want to use a new one we create a meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket Created for both bug reports and feature development on the bug tracker. for it and check the license there.
@poena asked if it is correct to not even credit the public domain images?
@aduth and @youknowriad both said that although they are not lawyers they believe public domain does not require any attribution.
@poena followed up the question and asked about the icons.
@youknowriad said wordpress/icons are a mix of Dashicons and custom-built icons so he believes all of them are WP made. I know some might have been inspired by Material ones.
@poena said that when people take something from core/GB and place it elsewhere, We can’t just say that the images have the same license as core/plugin because core/plugin is GPL GNU General Public License. Also see copyright license. and some images may be public domain for example.
@nrqsnchz said that this was why we decided to go with text-only patterns for now. We couldn’t find a good library of images that was also compatible with WP’s license.
@aduth said It would be good if it could be communicated something consistent like “all images and content distributed through patterns are [a: public domain][b: distributed as GPL]”.
@youknowriad said if a plugin/theme is GPL, it can just reuse anything WP provides if not, you need to check per case. @poena followed up saying It’s not that simple and that we know that from twenty nineteen.
@poena concluded the topic by saying that she just wanted people to be mindful when they make their pull requests.
#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg, #meeting, #meeting-notes
