DevChat meeting Summary – May 5, 2021

Agenda for the two meetings. Thanks to @peterwilsoncc and @jeffpaul for leading the 05:00 and 20:00 UTC devchats respectively.

Link to 05:00 UTC devchat meeting archive in Slack // Link to 20:00 UTC devchat meeting archive in Slack

Announcements and news

These posts need your feedback:

  • @ryokuhi published a proposal on Make/Accessibility about a new Trac workflow keyword that 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 would like to consider.  If you feel particularly opinionated or passionate about this, please comment on the post.
  • @jeffpaul and @desrosj published a request to Component Maintainers, Feature plugin authors, and the Gutenberg team to share plans / help needed for 5.8 (primary focus will be FSE).  Please comment on the post to help ensure we’re tracking the right work for the release.
    • @youknowriad noted that required Gutenberg changes in Core are made as filters/extensions points and brought to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as part of 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/ merge that happens regularly
    • @mkaz shared the WordPress 5.8 Must Haves project board on GitHub as outline of Gutenberg work for 5.8

5.8 Review

  • Schedule confirmed including 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. scrub schedule
  • @youknowriad shared that trunk is already on Gutenberg 10.4, @gziolo is working on updating it to 10.5 and the big changes (Global styles infrastructure in themes.json and FSE blocks) are coming in 10.6
  • Feature freeze on Tuesday May 25th (19 days from now) defined as “During the following two weeks, there will be no commits for new enhancements or feature requests. Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. will focus on defect work (aka outstanding bugs)
  • 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 on Tuesday June 8 (33 days)
  • RC 1 on Tuesday June 29 (54 days)
  • Release on Tuesday July 20 (75 days)
  • Current list of tickets that are on the 5.8 milestone, list of good-first-bugs tickets

Component maintainers and committers update

  • @sergeybiryukov shared Plugins update that Parameter names in 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 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. functions now use consistent terminology when referring to actions, filters, and callback functions via #50531
  • @sergeybiryukov shared Themes update that #49487 removes the “Featured” tab on Add Themes screen to match an earlier change in the Theme Directory
  • @webcommsat shared About/Help update that ticketticket Created for both bug reports and feature development on the bug tracker. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. continues with @marybaum
  • @audrasjb shared Menus update that #21603 is being reviewed
  • @audrasjb shared Upgrade/Install update that the last meeting recap includes a project for the next few releases

Open Floor

Props to @audrasjb, @webcommsat and @marybaum for reviewing this post.

#5-8, #accessibility, #dev-chat, #docs, #fse, #full-site-editing, #github, #learnwp, #summaries, #summary, #updater

Media Meeting Recap – May 6, 2021

The following is a summary of the weekly Media component meeting that occurred on Thursday, May 6, 2021 at 14:00 UTC. Weekly media meetings are held every Thursday at 14:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @antpb, @mista-flo, @chaion07, @adamsilverstein, @paaljoachim, @hellofromtonya, @sergeybiryukov, @desrosj

Media 5.8 tickets

This meeting’s discussion focused around WebP and 5.8 Media features.

#35725: Add WebP support – WebP support has been merged! Please test on all configurations possible to ensure there are no edge case issues. Big props to @adamsilverstein and all who helped make this happen! Adam mentioned that a post is in progress that will provide an overview to the new WebP supports.

#52876 Add capability to set default format for image sub-sizes. – This ticketticket Created for both bug reports and feature development on the bug tracker. is in progress and adds a new filterFilter 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. where people can set a default image type such as WebP. @adamsilverstein has asked for some testing assistance to ensure everything works as intended. Testing instructions can be found here.

#50105: Remove infinite scrolling behavior from the Media grid – It was agreed during the meeting that for the button that moves focus to the first newly loaded media item, “Jump to first loaded item” is a great way to make this not focus on images or any other specific media type and still be clear. @hellofromtonya mentioned in the meeting on the pending count issue, “I think it would be a better experience for users if we could solve it before 5.8 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.. That said, it would be good to get the 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. committed and then work on that specific issue as a follow-up.” It was agreed by multiple participants in the meeting that landing this sooner and iterating is ideal.

#37255: Update attachment functions to accept a post object in addition to ID@hellofromtonya mentioned keeping this ticket focused on resolving the issues that were identified and moving any broader scope to a separate issue to avoid this being punted to a future release again.

Props @antpb for proofreading and final review.

#core, #media, #summary

Editor chat summary: 5th May 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-05-05 14:00 UTC in Slack. Moderated by @get_dave.

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

  • At the time of the meeting the latest release was 10.5.4.
  • @get_dave noted 10.6 RC is due today (May 5th) with the stable release on May 12th.
  • Riad asked for volunteers to release the RC for 10.6 – this was completed post-meeting by @vdwijngaert.

WordPress 5.8

  • Feature freeze for Gutenberg for WordPress 5.8 is May 19th (10.7 RC).
  • The release schedule for WP 5.8 is available.
  • Riad noted that to follow the progress, we have these two things:
    • A project to see all the different mandatory tasks for this release.
    • A merge issue to track the progress of the integration of the Gutenberg updates into trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. before feature freeze date.
  • Riad asked for folks to review and help with the experimental APIs in this Issue.
  • @gziolo is already working on bringing Gutenberg 10.5 into WordPress trunk.
  • @youknowriad is the Editor Tech lead for 5.8.

Full Site Editing Next Steps

  • Reminder about Hector Prieto’s Full Site Editing Go/No Go: Next steps post which summarizes scope for Gutenberg in WordPress 5.8.
  • To summarise, the scope is roughly:
    • 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. theme building
    • Theme blocks (eg: Query, Navigation, Site Logo…etc) 
    • Template editing within the post editor
    • Widgets Editor & Block Widgets in 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. 
    • Persistent List view in the post editor
    • Duotone design tool 
    • Gallery block refactor
  • Riad said we’re already in a good state as everything is developed but we may still have to do some calls about whether to keep everything or reconsider some parts of it.

What’s new in Gutenberg

@ajitbohra posted What’s New In Gutenberg for the end of April.

Highlight’s included:

  • New block patterns and pattern transformations
  • “Template Editing Mode” – enables editing templates without leaving the Post Editor.
  • File Block now supports embedding PDFs in most major browser
  • Block widgets in the Customizer now have media upload and richtext formats.
  • Fix autoscrolling when selecting partially “off screen” blocks.

Key Project updates

Updates were requested for the key projects.

Global Styles

@nosolosw provided an update async via a Github Issue. I have omitted it here for brevity.

@youknowriad also provided us with a summary update:

  • the new 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. format merged
  • we’re making theme.json stable (no more experimental-theme.json ) in 10.6.

Block based WidgetWidget 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. Editor and Customizer.

@andraganescu provided the update.

  • The widgets editor has gone through an amazing round of polish.
  • Grouped up only late last week, this week all the major testing blockers have had their fixes merged in time for the new Gutenberg release.
  • The aim is to have a call for testing as soon as possible to collect feedback on the state and progress of the project.

Navigation Block

@joen provided an async update:

@mkaz also provided:

  • Responsive hamburger menu aiming for GB 10.7 PR-30047 eyes welcome
  • Dynamic Home URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is the last must-have for 5.8 in progress and looking good  PR-30926
  • Refining placeholder and design

Navigation Editor screen

@get_dave provided an update:

  • The Nav editor continues to see steady progress.
  • We now have all entity (post, page, 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.)…etc) block variations serialising to/parsing from their respective nav_menu_items. So when you add a Post link it stays synced to that Post.
  • We also have lots of work going on regarding notifying users about unsaved changes.
  • Both nav block and editor features have also seen background improvements to stability and test coverage.

Full Site Editing

The meeting agreed this was mostly covered by the above items.

@paaljoachim did ask if someone could provide an async update on the Page templates.

Feel free to leave an update in the comments if you have one.

Mobile Team

Task Coordination

@annezazu:

@aristath:

  • Last week was Greek/Orthodox Easter so it was a half working week here:
  • Continued working on PR to autogenerate anchors for headings – #30825. Could use a review after today’s updates.
  • Font-sizes can now use non-px values – #31314
  • WIP – Worked on splitting the theme.css file to conditionally load parts for rendered blocks only – #31239 (same as what we previously did for the style.css file).
  • This week & next week I plan to continue working on 5.8 tickets, converting the quote block to nested blocks, and improving the sustainability of block themes. Hopefully I won’t need to continue working on the autogenerate-anchors PR ’cause it will be merged.

@mamaduka:

  • Primarily focused on the new Navigation Editor.
  • I pushed another update for the “Most used terms” feature and based on the latest feedback. I think it’s in a good place to merge into the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • There’s also a new PR Site/Template editor welcome guide if anyone wants to test and provide feedback.

@paaljoachim:

@get_dave:

@ntsekouras:

@vdwijngaert:

  • Working on an accessible (and reusable) way of describing a path (eg: go to Settings > Reading) to follow, came up in 31122
  • Resuming work on the first step of duplicating post/page title to the top toolbar (issue: 27093, PR: 31288 )
  • Tweaking the ImageResizeControl behavior, now it returns NaN when empty or invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. 31355
  • Gave a go at fixing block conversion for <!–more–> tag in the middle of a paragraph 31374, could use a review.

@desrosj

@jorgefilipecosta:

  • Helping the merge of the theme.json shape changes (with reviews suggestions etc).
  • I also made some PR reviews not related to global styles.
  • I added some PR’s removing unused code 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.’s and stabilising other API’s.
  • Changed the way the global styles cpt is associated to a theme to use a taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. like the other FSE post types do.
  • Finishing a refactoring to the link color to use an elements + the same mechanism as duotone/layout instead of css variables.
  • I will work on moving theme.json to core and the code changes required to be core first code.
  • I plan on fixing some old issues/tasks where I have been pinged and have some insights.
  • And if time allows I plan on starting the work on dashboard that shows the performance metrics on each commit merged to trunk.

Open Floor

Note for task coordination purposes: Automattic will be on remote virutal meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. next week.

@annezazu noted for task coordination purposes that much of Automattic that focuses on the editor space is going to be on a remote, virtual  meetup next week (12th & 13th). It might mean less of us coming to the core editor chat or slightly less responsiveness during those days but it’ll probably depend on the person.

Please reconnect your 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/ and WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ accounts.

  • @desrosj flagged issue with some GitHub and WordPress.org connections where tokens expired for some users.
  • If you have previously connected your GitHub account to your WordPress.org account, please head over and verify the connection is still active!
  • If you have never connected your accounts, please do! This is a huge help for the release squads when they compile the list of props for a given release.
  • We always want everyone to receive proper recognition for their contributions, and this is a huge help with matching contributions to Gutenberg on GitHub to a .org profile. 
  • More info on connecting your Github profile to your WordPress.org account.

Opt out Plugin to be used to disable the block based Widgets editor.

@paaljoachim wanted to highlight this issue: Add a plugin to disable the block based Widgets editor.

As a plugin has been added if/when a user wants to go back to using the Classic Widget screen. I am hesitant. As it should be easier to jump between old <-> new.

@andraganescu responded:

“Easier” is complex. Adding buttons to switch in and out may sound easier, but using the same system that has been used for years via plugins can be easier as well. Opening that issue, I did think about the option to add an “opt out” button. But that would mean adding an opt in button as well. And that would mean adding a user setting. And, if not a user setting then a way to store the opt in state. This, as the welcome screen in the Guteneberg editor has shown us, is not a reliable way.

@andraganescu indicated there would be a “Welcome screen” on first use of the new Widget editor with clear information about how to install the Plugin to easily opt out.

@andraganescu also confirmed there will be multiple touch points:

  • Post install page.
  • Welcome screen.
  • Make post with more information.

Wrap up

Due to the meeting taking longer than usual @get_dave wrapped up by encouraging any further open floor questions to be left async as a comments (below).

Thanks to everyone who attended.

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

DevChat meeting Summary – April 21, 2021

@peterwilsoncc and @audrasjb led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Release announcements

WordPress 5.7.1

WordPress 5.7.1 was released on Wednesday April 14, 2021. This security and maintenance release features 26 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 in addition to two security fixes.

There are only 6 tickets in the next milestone (5.7.2), and as for now there is no urgent thing to address.

WordPress 5.8

Some blogblog (versus network, site) posts were published on Make/Core:

@annezazu shared that 2 weeks are left to go on a Query Quest and give feedback. Worth noting there is also an Italian version of the testing process (props to @piermario). If you have issues with the call for testing or questions about setting up a test site, please feel free to ask @annezazu in the #fse-outreach-experiment channel on 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/..

@chanthaboune shared that the next step for WP 5.8 is to get a release team together.

While she’s finally not available to lead the release squad, @francina will be available to help wrangling contributors and mentoring. She will also publish a call for release team members on Make/Core.

Make/Core News

Blog posts that need feedback: FLoC concerns

One blogpost was discussed during most of the meeting time:

@carike posted the proposal, and an active discussion started with more than 100 commenters. For those interested, there is a summary of the discussion on WP Tavern. Worth also noting that @helen, lead developer of the project, published a top comment about the proposal.

@peterwilsoncc previously shared a comment from the Security team in the initial post: based on the information presented, this should not be considered a security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have. at this time.

Worth noting that 3 people from Google Chrome DevRel team attended the meeting: @michaelkleber as Chrome Tech Lead for the ads-related APIs, @r0wan and @samdutton as Chrome DevRel.

Below you’ll find some direct quotes from this open floor discussion:

@michaelkleber shared that the FLoC initiative is just at the beginning of what Chrome calls an Origin Trial — that’s the way we introduce new proposed APIs to get feedback from developers.

@joyously asked whether FLoC simply is a cookie of another flavor or not.
@r0wan answered there is a key difference with a cookie is that it’s a 1:1 token the server sets on the client. With the FLoC id, it’s a 1:many grouping that does not enable that same direct link back to an individual across different sites. It’s also not a value that the server gets to set for the client.
@michaelkleber added that the key contrast with third-party cookies is that a FLoC cohort can’t be used to know information specifically about you. Instead it allows some kind of probabilistic information about a large group of people that you’re temporarily part of (each FLoC cohort has thousands of people in it).

@carike shared with a detailed use case and asked for the safeguards that are in place to prevent this.

@helen’s asked what is the utility is of disabling FLoC on the content provider front vs. on the consumer front.
@michaelkleber answered that in the final end state, they expect the way FLoC will work is that the only pages that will be relevant to calculating your cohort are the pages that call the FLoC 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..  So pages will “opt in” by using some new JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. function call. The HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. 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. being discussed here was introduced as a way that pages could include random 3rd-party JS without worrying that it would invoke that API without them expecting it. So the HTTP header is saying “There is a new API that exists in the web, and I want to be sure my page cannot use it”.

@michaelkleber: FLoC doesn’t involve saving any new information, it’s just calculated based on the recent browsing history — and not the full URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org even, just the domain name.

@helen: So on its own by default, a WordPress-served page of content is not going to be used to calculate. However, if you were to, say, embed something that includes a piece of JS, that JS could then call the API and it would include the entire page?
@r0wan answered: so a default WordPress page with no use of the FLoC JS API and no ad-tagged resources in it will not be used as part of the FLoC calculations. If that site includes a third-party that uses FLoC then that would include the top-level page.

@michaelkleber: There is a bunch of on-device clustering that goes into making sure that your FLoC is shared with thousands of other people. If you want to read more about the technical details of clustering, here’s the page that describes it all.

@macmanx: So, is there’s no point in a site blocking FLoC if that site is not using FLoC-enabled resources? If a site were not using AdSense, it’s most likely not even going to be included in FLoC? And, on the other hand, if that site were already running AdSense, it probably benefits from FLoC and would not want 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.?

@samdutton nodded: During the current FLoC origin trial, a page visit will only be included in the browser’s FLoC computation for one of two reasons:

@macmanx: So, FLoC only triggers when resources that benefit (or are assumed to benefit) from FLoC are present. If I have that right, then WordPress blocking FLoC software-wide would be similar to blocking Google Fonts software-wide. It would have an effect but would actually be more of a negative impact to the site itself.

@michaelkleber: We’re running the Origin Trial so that we can get feedback, and what we hear from people (including you, now) is the kind of feedback that affects the end decision.
So it seems to me that this group is generally in favor of our best-guess plan (only look at pages that actually invoke the FLoC API), for which thank you. But I’m sure we’ll hear other opinions as well.

@mkaz: I think debating the merits of FLoC is a bit beyond the point, it may or may not be evil, probably no more or less than say AdSense. Where we wouldn’t introduce something to WordPress that would explicitly block a site from implementing AdSense, right?
@carike: The proposal just changes it from opt-out to opt-in. It does not prohibit someone from opting in.
@westonruter: If the page has to opt-in to FLoC by using an API then what’s the point of also requiring the site to opt-in to allowing FLoC as well? Going back to the Google Fonts example, if WordPress blocked Google Fonts from being used except if an opt-in is used, then if a theme enqueued a Google Font stylesheet then they’d also have to add the code to opt-in to not blocking Google Fonts. That doesn’t make sense to me. It’s like requiring a double opt-in?
@mkaz: It doesn’t seem like the area of the WordPress software to automatically opt people out of something in their browser.

@helen: So, a user/consumer disabling FLoC in their browser would mean they are not dropped into a bucket that’s used to determine ads/whatever that they see around the web (or… wherever). A WordPress site by default will not be used as a part of determining a given user’s bucket.
@macmanx: It seems to me, based on all this discussion, the best place for anti-FLoC measures are in the browser under control of the viewer, not in the site. If a site is triggering FLoC in the first place, it likely intends to benefit from FLoC in some way.

@carike shared a quote from the Chromium repository: “Any request made within an ad iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. is considered an ad resource request.”
@michaelkleber: The point is that Chrome’s Ad Tagging is trying to figure out exactly which resources are ads — very important if you want to, for example, unload ads that use too many bytes.  So the rule is “anything loaded inside an ad counts as part of the ad”. But for FLoC, we’re asking a much coarser question: “Does this page have any ad stuff on it at all?”  So details about which specific items are part of that ad are irrelevant.

@jorbin: In my personal opinion, WordPress is best off making a decision of no action at this time (not that we are making a decision in the meeting). FLoC as of right now is in such a small trial that we as a project should continue to monitor it and try to encourage that the final implementation is one that is going to align with us a project, but as of now it doesn’t present any danger to individuals on the web and in fact has the potential to benefit many publishers.

At the end of the chat, @jorbin shared a reminder about the Post & Comment Guidelines on Make/Core blogs to everyone that has posting abilities on make/core that we do have a page with expectations for posting there and that 1) All posts should be peer reviewed (it currently states by a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component., but I personally would say project leaders who are not committer would fall into that bucket) and 2) That the peer reviewer should be recognized in the post.

The Google Chrome DevRel Team members shared that everyone is welcome to get in touch them via the chromiumDev Twitter account or the FLoC repository on GitHub.

After the devchat, @helen opened a ticketticket Created for both bug reports and feature development on the bug tracker. to summarize the discussion and to discuss the next steps: #53069: Consider implications of FLoC and any actions to be taken on the provider (WordPress) front. Everyone is welcome to contribute to the discussion in this Trac ticket.

Thanks @chanthaboune for the quick review.

#5-7-1, #5-8, #dev-chat, #summaries, #summary

DevChat meeting Summary – April 14, 2021

@markparnell and @audrasjb led the weekly meetings of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Upcoming WordPress releases

WordPress 5.7.1

Since no issue was raised after the release candidate, WordPress 5.7.1 was released a few hours after the devchat. It contains 26 bugfixes and 2 security fixes.

WordPress 5.8

Some blogblog (versus network, site) posts were published on Make/Core:

While it happened after the meeting, it’s important to note that the Full Site Editing Go/No Go decision was published on April 14, 2021.

@annezazu mentioned the latest call for testing for the FSE Outreach Program. This week, it’s about the Query Block.

Announcements and news

Please note that these posts are still waiting for feeback:

Component maintainers updates

General (@sergeybiryukov): Sergey has started chipping away at some long-standing coding standards issues in core, see ticketticket Created for both bug reports and feature development on the bug tracker. #52627 for more details.

Build/Test Tools, Date/Time, Internationalization, Permalinks (@sergeybiryukov): No major news this week.

Site Health (@clorith): No major news this week.

Menus, Widgets and Upgrade/Install (@audrasjb): No major new this week.

@audrasjb mentioned there are still many Core components looking for new maintainers:

  • Cache 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.
  • Database
  • Help/About (@marybaum)
  • Quick/Bulk Edit
  • Feeds
  • Filesystem API
  • Import
  • Mail
  • Plugins
  • Post, Post types
  • Login and registration

@marybaum volunteered to maintain the Help/About component. This request was accepted by the Core team.

Open floor

@webcommsat shared that lots of people have been asking about WCEU dates (7-10 June 2021). The community team is looking at how they promote contributing this year too. More soon.

Ticket #53014 was mentioned in both 5:00 UTC and 20:00 UTC devchats. It’s in milestone 5.8. It wasn’t fixed in previous releases as it still needs a 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. and proper testing. 

#5-7-1, #5-8, #dev-chat, #summaries, #summary

Dev Chat meeting Summary – April 7, 2021

This is the weekly meetings summary of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team. The facilitator for this week’s chats was @peterwilsoncc at 05:00 UTC and @francina at 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements & News

Upcoming releases

WordPress 5.7.1

In line with the trial for consistent minor release leads for each major branch, all the 5.7.x point releases will be led by @peterwilsoncc, with @audrasjb as deputy.

Here is the expected 5.7.1 release schedule:

  • Release Candidaterelease 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).: Wednesday 7 April, 2021 around 23:00 UTC (released)
  • Final release: Wednesday 14 April, 2021 around 23:00 UTC

@audrasjb announced (and hosted) a new 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. scrub right after the devchat.

Note: At the time this meeting recap is published, WP 5.7.1 Release Candidate 1 is now available for testing.

WordPress 5.8

@francina shared some blogposts worth reading, where a new, experimental, release cycle is proposed, and the early bug scrubs schedule is now available.

Core related blogblog (versus network, site) posts

@annezazu shared that the current FSE call for testing is now open for feedback until April 12th rather than April 8th. Hopefully, this gives people an extra weekend to chime in and share their experience.

@chanthaboune pointed out that the first go/no go date for FSE in WP5.8 is next Tuesday.

@nalininonstopnewsuk shared that it is possible share FSE Call for Testing on social and FSE Call for Testing on LinkedIn.

@francina shared this blog post from the Marketing Team: Thoughts on Marketing, FSE, and What’s Next. It’s relevant to the current release, so please read and leave your feedback.

Component maintainers updates

Build/Test Tools (@sergeybiryukov): Work has continued on backporting recent build and test tool improvements to the older branches still receiving security updates. See ticketticket Created for both bug reports and feature development on the bug tracker. #52653 for more details. A post is also upcoming on make/core.

Date/Time, General, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks (@sergeybiryukov): No major news this week.

Menus, Widgets, Upgrade/Install (@audrasjb): No major news this week.

Site Health (@clorith): The only ticket in milestone 5.7.1 was committed in time.

@francina also pointed out the ticket she opened in Meta Trac concerning Component maintainers updates. In the past month she also reached out to the majority of the components and removed inactive maintainers. Right now there are quite a lot of components without maintainers.

The attendees discussed about maintainers recruitment. If anyone is interested to help to maintain a component, @audrasjb pointed out that he would be happy to mentor/explain what he is doing on the few components he maintains. @francina proposed an online meeting/Q&A, like the casual online gatherings hosted by the community team.

Open floor

@paaljoachim asked what is the definition of what can and not not be included in a 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..

@jeffpaul quoted the Core team handbook: “A minor release is intended for bugfixes and enhancements that do not add new deployedDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. files and are at the discretion of the release leadRelease Lead The community member ultimately responsible for the Release. with suggestions/input from component maintainers and committers.”

@sergeybiryukov added that generally, minor releases are addressing regressions introduced in the latest release and some follow-up changes to new features, with occasional fixes for bugs from other recent releases, and occasional enhancements that the release leads feel are necessary.

#5-7-1, #5-8, #core-auto-updates, #dev-chat, #summaries, #summary

Editor chat summary: 31 March, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, March 31, 2021, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

WordPress 5.7.1

WordPress 5.7.1 maintenance release.
The following release schedule is being proposed:
Release Candidaterelease 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).: Wednesday 7 April, 2021 around 23:00 UTC.
Final release: Wednesday 14 April, 2021 around 23:00 UTC.

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

What’s new in Gutenberg 10.3.

5.8 Pre-planning

5.8 schedule

Monthly Priorities

March monthly priorities. Along with Key Project updates.

Global Style

Update from @nosolosw

Navigation Editor

Update from @grzegorz

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

Update from @mkaz

Mobile

Update from @hypest

Full Site Editing

Update from @annezazu

Task Coordination

@annezazu

  • Mainly focused on FSE Outreach program (daily fse testing, reporting issues, writing up summaries, writing tests, amplifying!) and a few CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement post ideas in the pipeline.

@aristath

  • Focus FSE and getting things ready for our MVP for inclusion in core.
  • Past week focused on implementations for hybrid themes, and also adding skip-links to FSE themes.
  • Focus on reviewing PRs.

@ntsekouras

@mamaduka

@poena

  • Reviews.
  • Testing Full Site Editing.
  • Reporting issues and creating pull requests toward the FSE MVP.

Open Floor

Discussing the Full Site Editing MVP.
To summarize the discussion that happened during the meeting and after, here are the top takeways:

  • There is confusion of what MVP for Full Site Editing consists of.
  • As has been previously shared, the MVP should make it possible to build a version of the Twenty Twenty-One theme, using only blocks, without any coding knowledge.
  • Widgets & Navigation work are not included in FSE but they are seen as complementary projects to help with adoption.
  • At the moment we have two targets: the full site editing MVP & what would be introduced in 5.8.

A link to the full discussion on Slack.

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

Dev Chat meeting Summary – March 31, 2021

This is the weekly meetings summary of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team. The facilitator for this week’s chats was @markparnell at 05:00 UTC and @francina at 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements & News

Upcoming releases

WordPress 5.7.1

In line with the trial for consistent minor release leads for each major branch, all the 5.7.x point releases will be led by @peterwilsoncc, with @audrasjb as deputy.

Here is the expected 5.7.1 release schedule:

  • Release Candidaterelease 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).: Wednesday 7 April, 2021 around 23:00 UTC
  • Final release: Wednesday 14 April, 2021 around 23:00 UTC

There are 33 tickets in the milestone:

  • 10 are already closed as fixed
  • 3 are fixed and reopened for proper backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch.

@audrasjb announced a new 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. scrub right after the devchat, and will run another one on Tuesday April 6, 2021 at 20:00 UTC.

Note: At the time this meeting recap is published, there are now 31 tickets in the milestone. 12 are fixed, 4 are reopened. The ticketticket Created for both bug reports and feature development on the bug tracker. with the higher priority was fixed (#52822).

Please note that this WordPress 5.7 board is the one to watch for 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/ updates that will need to land in this release.

WordPress 5.8

@francina shared some blogposts worth reading, where a new, experimental, release cycle is proposed, and the early bug scrubs schedule is now available.

Core related blogblog (versus network, site) posts

Some thoughts were shared about the last item (Add a testing template to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.). People are invited to comment in the blog post.

@francina suggested to follow make.wordpress.org/updates as this blog has updates from Make teams + project leadership.

Component maintainers updates

Build/Test Tools (@sergeybiryukov): Work has continued on backporting recent build and test tool improvements to the older branches still receiving security updates. See ticket #52653 for more details.

Date/Time (@sergeybiryukov): No major news this week.

General (@sergeybiryukov): No major news this week.

Internationalization (@sergeybiryukov): No major news this week.

Permalinks (@sergeybiryukov): No major news this week.

Menus (@audrasjb): JB did some Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. last week.

Widgets (@audrasjb): no major news this week.

Upgrade/Install (@audrasjb / @afragen): The team is still looking for feedback concerning the feature plugin. @francina asked if it would be useful to organize a test scrub. I would be a nice idea, and @afragen answered there’s a simple way to force the rollback for testing. The Upgrade/Install team will discuss this during the next #core-auto-updates weekly meeting on Tuesday April 6, 2021 at 18:00 UTC.

Toolbar (@sabernhardt): no triage planned this week, but @sabernhardt will probably will have another session in a few weeks.

Open floor

@chanthaboune noted that there are listening hours next week with her and Matt.

@annezazu dropped in a call out to help with the latest call for testing for the Full Site Editing Outreach Experiment: FSE Program Testing 4 – Building a restaurant themed header.

@chanthaboune shared that the recent Slack outage caused some additional things to break, so if folks see things that usually work but aren’t now, please feel free to let her know.

#5-7-1, #5-8, #dev-chat, #summaries, #summary

Dev Chat meeting Summary – March 24, 2021

This is the weekly meetings summary of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team. The facilitator for this week’s chats was @peterwilsoncc at 05:00 UTC and @audrasjb at 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements & News

There is also a couple items on the Make/Core blogblog (versus network, site) that require feedback:

Upcoming WordPress Releases

WordPress 5.7.1

In line with the trial for consistent minor release leads for each major branch, all the 5.7.x point releases will be led by @peterwilsoncc, with @audrasjb as deputy.

Here is the expected 5.7.1 release schedule:

  • Release Candidaterelease 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).: Wednesday 7 April, 2021 around 23:00 UTC
  • Final release: Wednesday 14 April, 2021 around 23:00 UTC

For now, there are 26 tickets in the milestone.
11 of them are closed as fixed, or reopened for backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. operations.

@audrasjb plan to run a 5.7.1 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. scrub on Thursday March 25, 2021 at 22:00 UTC. Everyone is welcome to attend.

Please note that this WordPress 5.7 board is the one to watch for 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/ updates that will need to land in this release.

WordPress 5.8

@chanthaboune shared some news about WordPress 5.8: @francina started to compile the planning round up and will publish it soon. @lukecarbis, @boniu91 and @hellofromtonya also compiled an early 5.8 bug scrub schedule, and published it right after the devchat.

Component maintainers updates

General (@sergeybiryukov): Work has continued on further fixing jQuery deprecations in WordPress core. See ticketticket Created for both bug reports and feature development on the bug tracker. #51812 for more details.

I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. (@sergeybiryukov): The list of translations for selecting a timezone in General Settings was updated to add two new timezones and remove some older duplicates. See ticket #52861 for more details.

Build/Test Tools (@sergeybiryukov): no major news this week.

Date/Time (@sergeybiryukov): no major news this week.

Permalinks (@sergeybiryukov): no major news this week.

Themes (@williampatton): the component has had quite a lot of eyes recently but extra help would be appreciated.

Site Health (@clorith): the component has one ticket for 5.7.1, it’s got a proposed solution and feedback. Everyone is welcome to contribute.

Upgrade/Install (@audrasjb): no major news this week.

Menus / Widgets: @audrasjb started to silently scrub both of their awaiting review tickets, in order to prepare 5.8 effort.

Toolbar (@sabernhardt): there is a Toolbar component triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. scheduled on Thursday March 25, 2021 at 15:00 UTC. Also, the Core team nominated @sabernhardt as Toolbar component maintainer and he accepted.

Open floor

@isabel_brison requested some feedback on an overview ticket for adding end-to-end tests to WordPress Core.
The ticket contains suggestions for how to test most of the pages in the WordPress dashboard but requested some feedback on how to, or whether to, test certain pages.

@francina provided a document produced by her colleagues at Yoast recently. These are now available on the ticket.​

@clorith started a discussion on more frequently merging updates from 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 in to Core. Highlighting that this would make testing future releases of WordPress features easier without keeping track of which features will remain in the plugin for the time being. There was general support for the idea.​ @chanthaboune is offered her help to move this forward.

@estelaris requested assistance for the Docs team in reviewing end user documentation. Particularly some of the more technical details. Anyone wishing to offer assistance can get in touch via the #docs channel 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/. or by messaging @estelaris directly.​

@peterwilsoncc requested some highlighted the workflow report for the 5.7.1 release due in April. For contributors wishing to write code and see it released quickly, Peter recommend they review tickets on the “needs 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.” section of the report. Contributors wishing to test or review suggested code can review tickets on the “has patch/needs testing” section of the report.

@webcommsat requested people share two items with the marketing team via shared documents:

Thanks @peterwilsoncc for his help to compile the meetings notes.

#5-7-1, #5-8, #dev-chat, #summaries, #summary

Dev chat summary: March 17, 2021

@francina led the chat on this agenda.

Announcements

The big news: WordPress 5.7 “Esperanza” landed March 9, and the group took a well-deserved bow.

Moving on, Francesca highlighted these posts:

@jeffpaul noted Trial run: Consistent minor release squad leaders for each major branch. Francesca added that the post is both a highlight and a call for volunteers.

@annezazu put out a last call for FSE Program Testing Call #3: Create a fun & custom 404 page. If you’d like to catch up on the previous two FSE tests, Anne and Francesca said you can find previous calls under this tag. If you’d like to do your own testing, the FSE Handbook has a page with instructions. Capping off the FSE discussion was Marketing Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @webcommsat, who said you can also share this LinkedIn promotion.

@francina then turned to posts that need feedback. This Proposal: A WordPress Project Contributor Handbook drew spirited emoji support from the group. Francesca also reminded the group to sign up for the Updates blog to keep up with a variety of team updates, as well as posts from @chanthaboune about cross-team efforts and the latest news from leadership.

Components check-in and status updates

@sergeybiryukov started with jQuery news: the version in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. has updated to 3.6.0, which is mostly 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 and improvements. Two callouts:

Aside from the change to no longer ensure XHTML-compliant tags for you, we do not expect other compatibility issues when upgrading from a jQuery 3.0+ version.

See ticketticket Created for both bug reports and feature development on the bug tracker. #52707 for more details.

 jQuery hoverIntent library has updated from version 1.8.3 to 1.10.1. The changes all appear to be minor.

See ticket #52686 for more details.

@adamsilverstein checked in with Media news: he’s working on landing support for WebP images in 5.8 and would like testing and feedback on ticket #35725.

Up next, @audrasjb said he has nothing new for Menus and WidgetWidget 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., but he’s quietly scrubbing bugs and watching tickets. On Upgrade/Install, he highlighted this feature plugin proposal post.

@sabernhardt wrapped up the Component updates with his announcement of a Toolbar triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors./bug scrub for the following day, March 18, at 16:00 UTC.

Open floor

IE11 support

@adamsilverstein asked: Given that the Project has decided to drop support for IE 11, have we discussed a specific release to make that change in?

The discussion that followed outlined a general process—notify, then act—but pointed out the group still needs to make a specific plan for IE11. Adam noted that IE11 is the only major browser that doesn’t support WebP images.

@desrosj said there might already be a notification in place. @adamsilverstein found a ticket, #48743, to that effect. Further discussion also made it clear that the team needs to do more to announce the change, including stronger language in relevant tickets (@desrosj and @audrasjb), a News blogblog (versus network, site) post (h/t: @jorbin) and relevant Handbook updates (h/t @jeffpaul)

“Try FSE?”

@sergeybiryukov observed:

It seems that most of WP users (outside of the contributing teams) are still largely unaware that full-site editing is coming later this year.

Perhaps that’s intentional, but once we have something stable to test, have we considered adding a dashboard widget to one of the upcoming minor releases, to invite more users to test FSE before final release, like we did 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/ in #41316 for WP 4.9.8?

See the full discussion that followed, with a variety of people sharing a variety of views on the subject.

#5-7-1, #5-8, #core, #dev-chat, #meetings, #summaries, #summary