Dev chat summary: May 19, 2021

@peterwilsoncc and @jeffpaul led the two chats–05:00 and 20:00 UTC—on this agenda.

Featured blogblog (versus network, site) posts

A Week in Core comes from @audrasjb and recognizes 90 contributors, of whom 18 were new last week.

What’s new in Gutenberg? Find out from @vdwijngaert.

An update on the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor from @itsjusteileen talks about that team’s monthly priorities:

  • Global Styles
  • Navigation
  • Widgets Screen
  • FSE
  • Mobile Projects

@francina reports on the Upgrade/Install meeting from Tuesday, May 18.

@desrosj took to the News blog to announce that Core is dropping support for IE11 in 5.8, what that means and how it will affect themes.

The 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) team has a proposal for updating TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. workflow keywords. They’d like another round of review, according to @joedolson’s post.

And finally, @mattchowning posted an apology for any consequences folks have suffered as a result of Gutenberg’s dual-licensing issues. In the 20:00 UTC meeting, @jeffpaul also blamed himself and other folx for the project’s overall approach to getting consent. Jeff recommends that if you’d like to discuss the situation further, please comment on the post respectfully and professionally.

Posts that need feedback

Jeff highlighted @andraganescu‘s post asking for help testing the Widgets editor and asked everyone involved with Core (ed. note: including you, dear reader) to 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. out some time to do that.

@drewwestcott and @daisyo shared some feedback on the instructions, and @webcommsat reported that Marketing is encouraging Meetups to promote the tests.

Next release: 5.8

Both facilitators issued a reminder: Feature Freeze is now five days away, on May 25, according to the full schedule.

In the 20:00 chat, @desrosj flagged that 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/ feature freeze is today, May 20, with RC1.

At that point, @jeffpaul pause[d] for what will feel like an uncomfortable amount of time to allow for calls for help…

@clorith pointed out that his component, Site Health, has a number of tickets marked ‘Good First Bug’ that could land in 5.8, if new contributors want to pick them up. Since he was mobile during the meeting, @desrosj compiled this list.

Other tickets mentioned:

#53212, from @pbiron, which @davidbaumwald said he’d review this week.

From @mte90: #44098, #15145, and #17025. @audrasjb said he owes @mte90 some feedback on those tickets, and @francina indicated she has an interest in the outcome.

Component maintainers

@jeffpaul moved the chat on to ask component maintainers to share plans and needs for help for 5.8.

@sergeybiryukov reported several items.

Plugins: Core finally supports the Update URI 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 headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes., so third-party plugins no longer risk getting overwritten by an update of a similarly named plugin from the WordPress.org Plugin Directory. See changeset [50921] and ticketticket Created for both bug reports and feature development on the bug tracker. #32101 for more details.

General: `wp-config-sample.php` has some new language that makes it clear that custom values should go in specific places, not just at the end of the file. Details are in #37199.

@desrosj brought in an update from @youknowriad on Core-editor.

@antpb reported on some meeting-time changes for Media.

@chanthaboune: Marketing is switching from pre-merge to post-merge, pre-release work—that means boosting the signal for testing features and 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., and building general awareness of FSE.

@audrasjb on Menus: Still planning to ship #21603 before feature freeze. On (Classic) Widgets: no major news.

@milana_cap on Docs: Starting collaboration with Docs team, especially with @bph for Block Editor user docs, and to get every handbook ready before release. She has also started populating the spreadsheet for tickets that need dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase..

@sabernhardt shared that the Toolbars component has two tickets in the milestone: #28569 and #26933.

Open Floor

@jeffpaul led off Open Floor with two 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. announcements:

1) WordCamp Northeast Ohio Region is this weekend.

2) WordCamp Europe tickets are going fast; register for your FREE ticket now. 

@clorith announced the Support team is looking for another deputy or two. Their workload has been growing over the years, and it’s more than what one rep can comfortably do these days. And, he pointed out, it’s a great opportunity to get involved without writing code. Details are here.

#5-8, #core, #dev-chat, #meetings, #summary

Core Editor Improvement: Contextual patterns for easier creation

We’ve all been there. Staring at a blank page sometimes with an idea of what you want to create and sometimes with a mind as blank as the page. To make the creation process easier and to leap into the pattern filled future, work is underway to suggest 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. patterns based on the block one is working with. Tied to this, when using the block inserter, block patterns will be suggested where possible. In the long run as this work continues and spreads to more blocks, it will be easier to create content and get inspired without leaving the editor. 

Exploring integrated patterns

For now with 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/ 10.6.2, you can see how this flow works with a few blocks including the Heading Block, Query Block, Social Icon Block, Buttons Block, and Paragraph Block. In particular, lots of work has been done around the Query Block to make it easier to create beautiful layouts in a few clicks with this powerful block. Here’s a quick visual showing this experience with the Quote Block: 

Video showing how the block patterns can be found in the transforms options

You can begin to explore these patterns in three ways:

  • Browse through them in the Patterns tab of the Block Inserter.
  • Select directly from the Quick Inserter. 
  • Navigate to them in the transform menu of individual blocks. 

Integrate your custom block patterns

On the flip side, if you’re creating your own custom block patterns, there’s a new experimental blockTypes property being worked on that will allow your patterns to show up in the transform menu. Here’s an example of how this works currently. This is still in the early stages though as it’s utilizing experimental components and might need changes down the road so stay tuned! If you do try this out and run into any bugs/feature requests, feel free to share them in the Gutenberg repo

Help with these efforts

Expect this work to continue expanding both in terms of integrating patterns in intuitive places and in terms of the number of unique patterns. To get a sense of where this work is headed in the future, check out this early PR. If you’re interested in helping in this area, make sure to join #core-editor, check out the current focuses, and attend the Core Editor weekly meeting Wednesday @ 14:00 UTC. Finally, if you’re wanting to dive into custom block patterns, check out the Learn WordPress course along with the documentation to get started. 

#core-editor, #core-editor-improvement, #gutenberg

CSS Chat Agenda: May 20, 2021

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, May 20, at 5:00 PM EDT. This meeting will be held in the #core-css 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 there’s any topic you’d like to discuss, please leave a comment below!

  • Housekeeping
  • Project Updates
    • Color Scheming (#49999)
      • Discuss next steps
    • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS deprecation path (#53070)
    • CSS Audit (#49582)
  • Open Floor + CSS Link Share

#agenda, #core-css

CSS Chat Summary: 13 May 2021

The meeting took place here on Slack. @notlaura facilitated and @danfarrow wrote up these notes.

Project updates

Color Scheming (#49999)

CSSCSS Cascading Style Sheets. Deprecation Path (#53070)

  • @tellthemachines is planning to write a Make post about the project to clarify details of the proposed methodology

CSS Audit (#49582)

  • The automated report generation PR needs 1 review – UPDATE: the PR has now been merged

Open floor / CSS link share

Thanks everyone!

#core-css, #summary

X-post: Why hosters should install the PHP-intl extension

X-post from +make.wordpress.org/hosting: Why hosters should install the PHP-intl extension

X-post: Follow-up Workflow Keyword Proposal

X-comment from +make.wordpress.org/accessibility: Comment on Follow-up Workflow Keyword Proposal

X-post: +make.wordpress.org/core/

X-post from +make.wordpress.org/accessibility: +make.wordpress.org/core/

Apologies on Gutenberg Dual-Licensing Process

Earlier this week two issues were opened in 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/ repo to help begin the process of obtaining consent from contributors to relicense their work under the GPLv2 and MPLv2 licenses.  I appreciate everyone’s quick responses on both of those issues, but understand that both raised some concerns that I would like to address here.  The first is a concern with the amount of notifications from the contributor agreement issue and the second is a concern with emails listed in the confirming commit authors issue.  Apologies to anyone negatively impacted by either of those issues as that was certainly not the intent.

There was consideration for alternate routes of gathering consent such as Google Forms, Google Sheets, a markdown file in the repo, and a standalone website but none offered the transparency and simplicity as a 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/ issue.  While prior Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. posts on the proposal and next steps for dual-licensing Gutenberg did mention the planned use of GitHub issues to gather consent from contributors, those posts could have been more descriptive in their plans.  In aiming for transparency and simplicity there were unintended side effects of adding noise into your daily lives with the GitHub notifications.  I apologize for this negative impact to you and any other unintended consequences.

There was also consideration for directly emailing or 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/. direct messaging to gain confirmation on potentially unknown commit authors, but these options were dismissed in favor of a GitHub issue to allow for transparency and simplicity in the process.  In sharing emails from the publicly available Gutenberg repo’s git log there were concerns that this opened those people up for spam and other unsolicited emails.  While those email addresses were already publicly available, I recognize that we made them more readily accessible and apologize for any negative impact this has on those individuals as a side effect of our attempt to transparently handle the process of confirming commit authors.

Again, it is worth repeating that I appreciate everyone’s quick responses on these issues and I apologize for anyone negatively impacted by them.  If you have any additional questions or concerns, please utilize the comments on this post and I will work to ensure they are addressed.

Props to @jeffpaul for drafting and reviewing this post.

Upgrade/Install component meeting notes from May 18th, 2021

On Tuesday May 18, the component held a meeting in the #core-auto-updates 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. You can read the conversation in Slack.

At this time, the component is tackling two main topics

  • Updaters
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of the component

Yesterday @afragen, @poena, @francina, and @pbiron worked/discussed the following tickets:

  • #14781 – The ticketticket Created for both bug reports and feature development on the bug tracker. was discussed also during the previous chat. It was decided to close it and follow the best practices laid out in the plugin handbook.
  • #20944 – The ticket was closed. The maintainers don’t see an elegant way to automate this action at this time. The solution is to re-activate the 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 from the CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. or via FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients..
  • #17301 – A method or instructions on how to test would be good. Added a note asking for testing info in the ticket.
  • #51823 and #51857 – The issue in the first ticket can not be reproduced or addressed without more details. @francina will investigate with @sergeybiryukov since the ticket mentions the Yoast plugin. As for the second ticket, @afragen pointed out that there were issues in the copying of the downloaded plugin or the plugin was incompletely downloaded and it’s hard to determine. The feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. Rollback Update Failure is an attempt to restore the previous existing plugin in the event of a failure. He created a Gist to force a failure to see how the feature plugin works. https://gist.github.com/afragen/80b68a6c8826ab37025b05d4519bb4bf – If you try it, please add your comments in the tickets.
  • #15134, #29408, and #36710 are all related to symlinks. @pbiron will evaluate those and see if he can close a couple of them in favor of keeping of single ticket open.

See you next week!

#core-auto-updates, #updater, #upgrade-install

Dev Chat Agenda for May 19, 2021

Here is the agenda for this week’s developer meetings to occur at the following times: May 19, 2021 at 5:00 UTC and May 19, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

Blog posts that need feedback

5.8 Schedule Review

  • Final Alpha Scrub focused on features and enhancements before Feature Freeze on May 24, 2021 at 20:00 UTC
  • Feature Freeze in 6 days on Tuesday, May 25th
  • 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 in 20 days on Tuesday, June 8th
  • RC 1 in 41 days on Tuesday, June 29th
  • 5.8 release in 62 days on Tuesday, July 20th

Components check-in and status updates

  • 5.8 plans and help needed
  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

Props @desrosj for peer review.

#5-8, #agenda, #dev-chat