Greetings! Here’s what happened in the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, September 16, 2020, 05:00 UTC and Wednesday, September 16, 2020, 20:00 UTC, following this agenda.
05:00 UTC core dev chat
@thewebprincess facilitated the meeting and took notes. Find the full Slack archive here.
20:00 UTC core dev chat
@thelmachido facilitated the meeting and @laurora took notes. The full Slack archive can be viewed here.
Both groups followed this agenda: https://make.wordpress.org/core/2020/09/15/dev-chat-agenda-september-16th-2020/
@pbiron shared that there will be an Upgrade/Install component 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. scrub today (September 17) at 18:00 UTC. Everyone is welcome to attend! More info can be found here: https://make.wordpress.org/core/2020/09/16/upgrade-install-component-bug-scrub-for-wordpress-5-6
@flixos90 would like more thoughts and feedback on a proposal to enhance image preview: https://make.wordpress.org/core/2020/09/15/enhancing-image-preview-core-proposal/. Please leave your comments on the post.
Due to the speed WP5.6 is moving at, and some unexpected items (oEmbed & PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.0), @chanthaboune has organized a meeting with the 5.6 release squad to discuss. This will take place today (September 17) at 20:00 UTC. @helen proposed streaming the meeting and the squad is still deciding whether to do this. In any case, notes will be taken and published.
A bug scrub was held before the 20:00 UTC dev chat: https://make.wordpress.org/core/2020/09/15/i18n-component-bug-scrub-for-wordpress-5-6/. @helen explained that updates were left on tickets reviewed from the Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. reports, and @justinahinon added that progress has been made on all i18n 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. 5.6 slated tickets.
Updates from Component Maintainers/Focus Leads
Will explore adding some UI User interface elements to manage email notifications on 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 and theme auto-updates.
@audrasjb highlighted the bug scrub taking place today (September 17) at 18:00 UTC.
@carike reported: “We have been receiving a lot of feedback, for which we are very grateful. Will update tickets over the next few days with more details on the proposed application design.”
@imath requested a second opinion on ticket Created for both bug reports and feature development on the bug tracker. #50521, and also shared that he’s been working with @dshanske on writing a kick-off post to launch a project to develop the WP Comment Types feature from a plugin. They would like guidance on how to make this post public on make.wordpress.org/core.
@clorith shared that they’re doing some multisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site work for this cycle and besides that general bug watching.
(Classic) Menus and Widgets
@audrasjb reviewed some tickets with a patch 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 put a few of them into milestone 5.6.
@johnbillion noted the continued progress on PHP 8 compatibility.
@karmatosed shared “A little note if any components/focuses want design help this release just pop a keyword on or hop into #design. There’s an awesome group of people ready to help this release so great to catch all those little tickets and things.”
@bduclos asked if there are any mockups of the new Twenty Twenty One theme available, and will the project be on Github GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/. @melchoyce will be sharing more details about this in a post, due to be published soon.
There was a lot of discussion regarding the announcement from Facebook & Instagram that they’ll be dropping unauthenticated oEmbed support; mainly around timing and how to communicate this update to WordPress users.
It was noted that the removal of those blocks in v9.0 of 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/ is complete – if need be it can be reverted.
@whyisjake volunteered to put a post together so that the conversation could be continued.
There was an update in response to privacy/data deletion request in issue #43437. It is not anticipated that there will much of a change to the current tools. Concluding with it is not foreseen that there will be any significant breaking type changes for the ticket.
A proposal was put forward to create a #sustainability Slack 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 for those interested in improving the sustainability of WP, through performance enhancements and more. @isabel_brison is putting together a blog (versus network, site) post to discuss further. @webcommsat shared this post: https://make.wordpress.org/marketing/2020/06/01/sustainability-working-group-update/ which details some of the work that has been done in this area so far.
@webcommsat highlighted that a week celebrating WordPress translation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. will take place from 28 September to 4 October 2020. If you have any ideas on how the translation process for WordPress releases could be promoted, please leave comments on this post: https://make.wordpress.org/polyglots/2020/09/09/lets-celebrate-international-translation-day-together/.
Next Dev Chat meetings
The next meetings will take place on Wednesday, September 23, 2020, 05:00 UTC and Wednesday, September 23, 2020, 20:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions.
#5-5-1, #5-5-2, #5-6, #dev-chat, #summary