The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this sitesite(versus network, blog) for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.?Create a ticket in our bug tracker.
This was a very quiet meeting, with only @psykro and @hrmervin attending. We continued along with the planned items in the requirements document.
The Objectives section seems complete, and no one has added any further comments on the document or the recap post, so we’re going to move forward and accept this as it stands
We reviewed the current status of the new Use Cases section. @psykro added a comments on the State item as well as comments around how we see notifications being sent to users based on their role.
Based on the fact that there were no other voices in the meeting, we ended the meeting early. As always we welcome feedback from the community in the current progress of finalizing the requirements document.
Below is a summary of the discussion from this week’s JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. chat (agenda, Slack transcript).
Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.
Create blockBlockBlock 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. package
New @wordpress/create-block package was merged in the past week: https://github.com/WordPress/gutenberg/pull/19773. The package is meant to help pluginPluginA 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 scaffold new blocks with a single command npm init @wordpress/block.
It is already available on NPM. It was published today as part of the next GutenbergGutenbergThe 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/ plugin releaseReleaseA 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. process that started on Monday.
Last week, Microsoft announced its new “Playwright” tool, which is very much like Puppeteer and created by many of its original contributors. The main draw here is that it supports multiple browsers, whereas we’ve always been limited to just Chrome using Puppeteer.
We discussed whether we should consider migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. from Puppeteer to Playwright but we decide to postpone the decision for some time. The reason for that is the uncertainty about how those two projects evolve. The fact that the Puppeteer team has just released a new version that supports the Firefox browser makes it even more interesting. We plan to revisit this topic in the future.
The chat marked week 2 of th 5.4 releaseReleaseA 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. cycle.
@francina announced that @davidb has posted this bug-scrub schedule, which also lists regular design and editor triages. Remember, you can get serious props by hosting a scrub of your own — and you can pick the tickets to suit your own interests!
She also confirmed the schedule and release squad.
BetaBetaA 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: 11 February 2020 (4 weeks from kickoff)
Release Candidaterelease candidateOne 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). 1: 03 March 2020 (3 weeks from beta 1)
General Release: 31 March 2020 (3 weeks from release candidate 1)
Answering the question from @francina, @karmatosed asked the group (plus you and me, dear reader) to comment on the post with our feedback. Priorities are open, as long as we keep in mind what we can finish by February 11 — Beta 1.
(Ed. note: If this is your first major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. cycle, and as a reminder for the rest of us, new features and enhancements must be largely complete by the time we release Beta 1. We call this a feature freeze.
Further betas and the release candidates are for bugbugA 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 patches. There’s also a string freeze at RC1.)
@karmatosed made one final point, asking if the working group could alternate meeting times to include the whole globe, and devchat attendees readily agreed.
Components Check-in
@ianbelanger asked for help testing and submitting patches for 19 bundled-theme tickets and 39 Twenty Twenty tickets, so at lease some of them can get into 5.4.
@johnbillion and @clorith reported steady progress on tooling and Sitesite(versus network, blog) Health, respectively. @xkon reported some small fixes and enhancements in privacy. See the transcript.
@jorgefilipecosta announced the release of Gutenberg 7.3, “featuring a very significant performance enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature..” (I think he means it’s faster. 😜)
He touted the navigation blockBlockBlock 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. as the big feature for 5.4 and pointed us all (you too, dear reader) to this board for tracking the status for that block.
GutenbergGutenbergThe 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/ 7.3
@gziolo announced that the Gutenberg 7.3 releaseReleaseA 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. was planned to happen later in the day and said, this release includes among others:
Multiple performance improvements.
A new blockBlockBlock 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. collections APIAPIAn 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.. The API is useful when a developer wants to group the blocks in its section in the inserter.
Further improvements to the Navigation block.
New experimental blocks for the full sitesite(versus network, blog) editing.
More details about this release are available on the release post.
Weekly Priorities
For this week, we keep the same priorities as last week:
Global styles also have a focus page on makemakeA 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)./design: https://make.wordpress.org/design/handbook/focuses/global-styles/
Worked on resizable editor PR https://github.com/WordPress/gutenberg/pull/19082.
All the tests are now updated, and it’s ready for further review. There’s a bit of discussion on how to isolate the editor-specific styles for manipulation in the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., any feedback appreciated at this point!
Has been working on the icons package. Referred Icons are all over the place in Gutenberg right now, and thinks at least we should gather them in a single package. Said technology-wise, we still need to explore different options to how best ship them for authors, but a tree-shakeable npm package seems like the best initial path forward without BC concerns. @youknowriad will continue working on a solution to this problem.
@youknowriad is also working on an Extensibility API Proposal ( will share more very soon) and keeps doing heavy triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. as time allows.
Is working on an attempt to have responsive backgrounds in blocks which have image backgrounds, and doing various tidying up PRs for the navigation block.
@nosolosw is focusing back on the work on Gutenberg. Revived a lingering PR to fix a focus issue in the gallery block https://github.com/WordPress/gutenberg/pull/14930. The PR needs a technical review!
Worked on some bugbugA 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 smaller enhancements.
Continued the work on PR’s I have open to address reviews.
For the next week:
Help to have a “Global Styles” mechanism in the core.
Continue the work on Angle Picker and Gradient type picker for the custom gradients.
Focus on triage issues. Reviewing PR’s required for 5.4 betaBetaA 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.
Renaming Inserter categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. names: https://github.com/WordPress/gutenberg/pull/19279.
Helping around improvements and consistency among various link components
Hoping to try to push user-metaMetaMeta 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.-based preferences persistence (sticky preferences) over the finish line. @aduth referred it would be a nice feature for WP 5.4.
Would like to visit some project management automation at some point.
Added further automation for CHANGELOG file updates in npm packages release
Wants to get a closer look at the Global Styles proposal and the new API that Riad mentioned.
Open floor
Template lock active at the post type level, and templateLock={ false } in InnerBlocks causes an invalidinvalidA 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. block warning
@chrisvanpatten brought up issue https://github.com/WordPress/gutenberg/issues/11681 and asked if there are any options to move the issue forward as the issue is causing a frustrating experience. The ticketticketCreated for both bug reports and feature development on the bug tracker. seems stalled without a clear path.
Currently, @chrisvanpatten relies on dispatch('core/block-editor').setTemplateValidity(true); as workaround to the problem.
@chopinbach volunteered to help address this problem, and @chrisvanpatten volunteered to team up. Thank you both!
FormTokenField: Make it possible to add children
@scruffian asked for feedback on https://github.com/WordPress/gutenberg/pull/19676.
@youknowriad said that while the change is minimal, it would be good to expand on the use-cases. @youknowriad referred that adding random children may not be the best path forward, and asked if there is another abstraction possible, or if the button is something that can be built-in.
@scruffian said @youknowriad ideas are valid, but his thought was that it would be more useful as it was proposed in the PR. @scruffian is open to achieving the result differently.
Server-side context API
@chopinbach asked for the latest updates on server-side context API @epiqueras is working on.
@epiqueras said the API is similar to ReactReactReact is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. context and that he needs a PR review.
@youknowriad and @mcsf referred that ideally, a block consumes from a “contextname”, not a “blockname” and different blocks can use the same context name to expose their context.
@epiqueras linked to a comment providing some reasons where the approach may have problems.
Based on feedback received at meetings and comments, we focused on making the Objectives section in the requirements document more concise.
We also added a Use Cases section, based on feedback from the previous meeting recap post.
Use Cases
This is the excerptExcerptAn excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. of the “Use Cases” section as compiled by @folletto and @psykro.
Section 2. Use Cases
1. Action required: the plugin wants the user to take a decision, i.e. “you got a comment” (action, notification)
2. Onboarding: the plugin wants to provide guidance on a specific feature, i.e. “try this feature” (action, on-page/notification)
3. Informative: the plugin wants to inform the user about something, i.e. “backup completed” (no action, notification)
4. State: the plugin changes its state, i.e. “settings saved” (no action, on-page)
5. Marketing: the plugins wants to advertise something or suggest an upgrade, i.e. “buy an upgrade!” (action, on-page)
Requesting Feedback
Should we address possible unintended uses (example: Notifications of subscribe/unsubscribe from sitesite(versus network, blog) which may include a profane username?) @folletto
For implementation, should we port notifications (such as marketing notes) only to the user who activated the pluginPluginA 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? @m1tk00
A note about how we hope to advance the project forward at a steady pace: by working together on the requirements document during meetings, and as time allows in between with comments and channel talks. Once we gather feedback on our goals and actionable steps in the best interest of a merge-able project, then we will progress with next sections of the document and work. @psykro@hrmervin
@francina is working on putting together a releaseReleaseA 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. squad. Some roles are already confirmed:
@matt is the release leadRelease LeadThe community member ultimately responsible for the Release.
@sergeybiryukov will be the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. tech focus lead
The whole team should be assembled by the end of the week. There is a fewer roles than in 5.3, because it’s a shorter release. The first BetaBetaA 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. release is in 3 weeks from now.
@davidbaumwald expects to release the bugbugA 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. scrubs schedule by the end of the week.
@karmatosed added that Core design triages (on Mondays) for a few weeks can also focus on 5.4 to boost things.
@audrasjb noted that depending on the number of accessibilityAccessibilityAccessibility (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) related tickets, the Accessibility Team can organize some extra accessibility focused bug scrubs. He will check the milestone to see if there is a need for more accessibility bug scrubs.
As @azaozz stated, hopefully component maintainers will take bigger and bigger part in “driving” 5.4, and releases in general.
@pbiron asked if there is a specific focus for 5.4. @francina answered that in general, 2020 is going to focus on one big goal: full sitesite(versus network, blog) editing with GutenbergGutenbergThe 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/. @dingo_d noted that it would need some coordination with the Theme Review Team.
@paragoninitiativeenterprises noted that #49200 needs feedback from anyone interested in WordPress security, or who develops plugins/themes.
@audrasjb is working on two tickets related to Themes and Plugins auto-updates: #49199 and #48850. This is one of the 9 projects for 2019-2020. The design team already provided some helpful feedback. These tickets are now waiting for technical review so they could hopefully land in the next couple of releases.
@marybaum noted her availability for copy review on 5.4 features.
@azaozz reported the Media team will release a feature plugin for lazy loading, so it can be tested well before adding to core. The pluginPluginA 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 should be available in a couple of days.
@francina mentioned that development on 5.4 should have started the day 5.4 was branched, back in October. In fact, many people wait for the kickoff to start working. With Beta release scheduled in 3 weeks, it’s not really the time to add not fully ready features to the scope. However, WordPress 5.5 agenda is already known, so there is no need to rush things.
@azaozz and @francina pointed out that as soon as a release’s code is moved to a branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"., trunktrunkA 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. is back in business for the next release.
@xkon noticed that the “Current Release” widgetWidgetA 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. on MakemakeA 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)./Core might be confusing for newcomers as it’s still indicating 5.3 as the current release in progress.
Calls from component maintainers
Media:@azaozz is looking at couple of small enhancements for the uploader changes from 5.3, specifically adding a link in the UIUIUser interface to the original image (if it was scaled), and looking at some of the edge cases when creating image sub-sizes, file size for large PNGs, etc.
Widgets & Menus:@audrasjb will coordinate with @welcher to identify priorities for an eventual specific bug scrub.
Build tools:@johnbillion is going to look at getting several of the Composer related tickets into 5.4 (like using Composer for external libraries and phpunit). @desrosj and @johnbillion to synchronize their work at some point as @desrosj is working on backporting the local Docker environment.
Comments:@imath committed to look at each ticketticketCreated for both bug reports and feature development on the bug tracker. involving comments in 5.4.
Open Floor
Some new contributors asked about how to start with core contribution. Worth noting the next New Contributor Meeting is scheduled for next Wednesday at 20:00 UTC in #coreSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. This is a great opportunity to ask for help or to learn how to contribute to WordPress Core.
We’re resuming our work on the WP Notify project with better focus on actionable ways to address the challenge of notifications in WordPress.
We started by answering more pointed questions as to what the solution must address, and whether a temporary alternative should be entertained at all.
Temporary Solution
@psykro suggested to post a separate tracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker., to improve the current admin_notices implementation, with sample code from @apedog
The benefit to this is that, as a team, we get something into coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. that improves users lives and we gain some real world experience of how the process could be improved by the final solution.
The negative is that it would mean this code is likely to be eventually replaced by our final, better solution. This very discussion, is the reason we want to present this concept to the community, for feedback on whether to a) expand admin_notices, or b) affirm the need for an entirely new replacement solution altogether, and what are the critical elements of that new approach
@schlessera is of the opinion, and rightly so, that any work done to improve the current admin_notices functionality is not worth the time. We should rather work on a solid, scalable and manageable solution for notification channels.
Permanent Solution (From The Onset)
A few of the very direct questions we must address for the replacement solution as suggested by @folleto are
What are we replacing? (if anything)
What kind of backward compatibility do we need?
What’s the minimal APIAPIAn 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. and UIUIUser interface we need to build for a v1?
As we answer these questions, we’re keeping in mind the end-user experience together with the API required. For example, a notifications menu will need a completely new way of handling notifications in WordPress API through use of the database and rendering those messages.
As @schlessera pointed out “The initial UI should satisfy the 80% need of letting Core/plugins/themes communicate platform state changes within the adminadmin(and super admin) dashboard in a scalable way where the user/user group keeps control.”
Meeting time
During the course of the meeting it became somewhat clear that the time of the meeting might be causing some problems for folks in different time zones. Conversation in the meeting became much more active after the first hour. Therefore we would like to know if the current meeting time is suitable, or if we should consider an alternative?
Next-Steps
Please comment with your thoughts below. You can also add comments your comments in the WP Notifications Project Google Doc under Section 1. “Objectives”
Here’s a summary of the #core-media chat from January 9, 2020. Weekly media meetings happen on Thursdays at 14:00 UTC; see the full transcript here, in the Make WordPress Slack.
Happy 2020! Because of the holidays, the group postponed chats until Thursday, January 9.
This morning, the group also discussed moving the regular time, so more people can join the chat – particularly people working on critical tickets in the 5.4 releaseReleaseA 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. cycle.
Here are three options. Vote for your favorite in the comments:
Move the current Thursday 14:00 UTC time to 15:00 UTC
Move the date to Tuesday at 21:00 UTC (this option works well for the three who came to today’s meeting.)
Multiple meetings, to account for both sides of the world. This option would likely require a push of the currently scheduled meeting to 15:00 or 16:00 UTC as well as an agreed time and date for the second meeting. @joemcgill suggested that multiple meetings not be forced to cover the same agenda items. Some items will overlap where it makes sense, but, for example, if one meeting has cleared the ticketticketCreated for both bug reports and feature development on the bug tracker. queue, it would be pointless for the next meeting to consist largely of a triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors..
New Media ticket triage
#48194 – Unregistered image sizes used for IMG tagtagA 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.) “srcset”
As @joemcgill pointed out: “The problem here seems to be that someone has deleted image files that are still referenced in the database in attachment metadata. Regenerating image sizes ( wp media regenerate ) would fix this problem, but should we only use registered sizes in `srcset` attributes if there are other sizes available?”
#48321 – Hotswapping featured imageFeatured imageA featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. with gallery images
It seems the ask is for (after creating gallery) the option to click on one of the gallery items and set as featured image of the associated post. It was agreed by attendees that this may not be best fit in the gallery blockBlockBlock 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.UIUIUser interface and perhaps would be better fit as an option within the media modal when creating galleries, images, etc.
The group changed the ticket to ask for reporter feedback.
@karmatosed made another point. The “Uploaded to this post” filterFilterFilters 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., in the Set Featured Image modal, does give the reporter part of what they’re asking for.
#48325 – Additional filter in media-template.php. Let developers hide attachment page link.
@joemcgill pointed us to the code that creates the attachment link: https://github.com/WordPress/WordPress/blob/master/wp-includes/media-template.php#L511 and said, “At minimum, I think that template should check that data.link is actually a URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org before displaying [it]. [Developers] could filter the data that is used by this template.”
WordPress 5.4 Media Focuses
While it didn’t come up in the meeting, notes are a great place for all of us to develop ideas for Media focuses in 5.4.
If you have any media-related focuses you’d like to work on in the 5.4 cycle, and that you’re ready to work on, please leave a comment.
That helps the Media maintainers gather and prioritize the work. Plus, it would be great if you’d come to next week’s chat so we can all discuss your idea!
The following is a summary of the weekly media component meeting that occurred on Thursday, December 19, 2019. 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.
Due to the holidays, we are postponing weekly meetings until Thursday, January 9.
Additionally, we are planning to adjust the meeting time in the new year to allow for better attendance from people working on priority tickets during the 5.4 cycle. @joemcgill will be reaching out to component maintainers to gather preferred times and will post an updated schedule before January 9.
WordPress 5.4 Media Focuses
As planning for WordPress version 5.4 is beginning, @francina has reached out to component maintainers to see if there are any major plans for this releaseReleaseA 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.. Here are the items currently being discussed:
#44427: Introduce lazy-loading APIAPIAn 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. for media and other elements – @flixos90 is leading this effort and will be looking for feedback.
@azaozz plans on working on more meaningful error messages when uploads fail (possibly in cooperation with Sitesite(versus network, blog) Health).
@azaozz also plans to look into deprecating some of the “notoriously misused” image related functions, like constrain_size_for_editor().
Several other regular contributors are still working out how much time they’ll have to contribute in the new year and what their focuses will be.
If anyone has any additional media-related focuses they plan to work on during the 5.4 cycle, please leave a comment below so we can gather and prioritize work in the new year.
All the discussions can be found in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. channel on SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.here.
Announcements and highlighted posts
@audrasjb gave an update about 5.3.1 version that was released on December 13. Right after, a couple of high severityseverityThe seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. issues were raised on Core TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. The releaseReleaseA 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. team then planned and held two bugbugA 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. scrubs and released a provisional schedule for 5.3.2.
Update: WordPress 5.3.2 went live later yesterday after the devchat.
@francina gave a quick update of WordPress 5.4, which is ETA is still March 31 as initially planned. She is currently collecting feedback from component maintainers and the release could eventually be shortened if there are no big features planned to ship into the version.
Components Check-in
@johnbillion precised that component maintainership doesn’t mean having to fix all the bugs, and that it’s more a shepherding role. So, anyone interested in maintaining a component or just wanting to know more is welcome to pingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” a committercommitterA 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. or release leadRelease LeadThe community member ultimately responsible for the Release..
@imath called for attention on #33717 from the Comments component to which he proposed a patchpatchA 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..
@francina then manifested her desire to see the Comments components as one of the focus for 5.4, since it has been abandoned for a while.
An interesting discussion about components and components maintainers then took place. @francina asked about how the Core team can help with the recruitment of maintainers.
@karmatosed suggested a few steps that would basically consist in
Clarifying what component maintainers do.
Being ok with people going in and out of that role, almost encouraging it to spread good people around.
Looking at what is a focus for this coming year.
@garrett-eclipse suggested we do on MakemakeA 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)./Core on seeking maintainers. He also proposed we can see who the regular contributors are in the component and reach out to them specifically.
@mikerbg said that a good step would be to identify individuals that are willing and able to provide some assistance to the marketing team to publicize recruitment opportunities and needs.
@jeremyfelt reminded this discussion from a chat in May, that it might worth looking at.
The full transcript of the discussions about components and components maintainers can be found here.
