Dev Chat Summary: December 9 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, December 9, 2020, 05:00 UTC and Wednesday, December 9, 2020, 20:00 UTC.

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

@francina & @johnbillion facilitated the meeting and @laurora took notes. The full Slack archive can be viewed here.

Announcements

WordPress 5.6 aka “Simone” was released yesterday (8 December 2020). The release squad was entirely made of people identifying as women and non-binary folx. You can read more about the release in this blog post. At the time of the meeting, @helen shared that it’s already exceeded 3 million downloads.

The annual State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. will be taking place Thursday 17 December at 1600 UTC. If you’d like to submit a question, the deadline is Friday 11 December! This post has more information.

Updates from Component Maintainers/Focus Leads

Build/Test Tools:

@desrosj is continuing to work on the 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/ Action workflows and backporting the local Docker environment to the remaining older branches.

@desrosj has been working one repo at a time to convert the Travis configurations to workflows. If you maintain any repositories under the WordPress GitHub organization and want to help with the transition, feel free to DM him.

Open Floor

@afragen requested some extra eyes on #51976. If you’re able to help out, please add your comments to the ticketticket Created for both bug reports and feature development on the bug tracker.. And also added that if you’re after a larger challenge to take a look at #51928, noting that 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. might need to be moved to #51857.

Next Dev Chat meetings

The next meetings will take place on Wednesday, December 16, 2020, 05:00 UTC and Wednesday, December 16, 2020, 20:00 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions.

#5-6, #5-7, #dev-chat, #summaries, #summary

Dev Chat Summary – 2 December 2020

The meeting was facilitated by @peterwilsoncc and @thewebprincess while @mikeschroder and @johnbillion took notes. Full meeting transcript on Slack. Both groups followed this pre-prepared agenda.

Announcements

Highlighted Posts

  • A Week in Core – November 23, 2020
  • What’s next in Gutenberg? The monthly report is out
  • Discussion: Update the updater
  • Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are continue to be updated ready for final release, here’s the latest dev-notes.
  • Release cycle discussion post – we need your feedback!
  • WP Notify project review

Component maintainers and focus leads

@peterwilsoncc reminded everyone that these components are in need of maintainers:

If you’re wondering what being a maintainer involves, @markparnell linked this guide from @francina.

Open Floor

@noisysocks requested review on #51612, which aims to make the  render_block_data, pre_render_block and render_block_context filters run on nested blocks. The PR with the latest approach can be found here.

The 2000 UTC group discussed #51913 and #51918 which led into a general discussion about the level of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support in 5.6 and how to communicate it. @marybaum asked for clarity to ensure all the marketing messaging is accurate.

The current consensus is that coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is “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.-compatible”, which means 5.6 works on its own with PHP 8, but that any given site may not work due to the plugins and themes in use and that more defensive programming is needed in core.

Next Dev Chat Meeting

The next meetings will take place on December 9, 2020 at 0500UTC and December 9, 2020 at 2000UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

Apologies

Apologies from @johnbillion for the late posting of this summary. The post sat in draft until today when I was reminded of it.

Onwards!

#5-6, #5-7, #core, #dev-chat, #summaries, #summary

Dev Chat Summary – 25 November 2020

The meeting was facilitated by @thewebprincess while @thelmachido took notes. Full meeting transcript on slack. Both groups followed the pre-prepared agenda

Highlighted Posts

  1.  A week in Core. Take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between November 16 and November 23, 2020
  2. On November 24 the Field Guide was updated with new  Dev notes
  3. WP release cycle. If you work for a company whose product is influenced by WordPress releases, you are encouraged to join the discussion about aligning the WP release cycle with industry standards
  4. 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 and themes developers releases depend on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., so it’s important that extenders reply.
  5. With the 5.6 release scheduled for December 8th, let’s start planning for 5.7. What’s on your wish-list for version 5.7
  6. The marketing team are starting working on ‘the Month in WordPress in their weekly meeting, please reach out if you have any contributions to share.
  7. Last but not least, the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. is now published. Folks are reminded to continue testing PHP 8

Component maintainers and focus leads

 PHP 8 Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. @sergeybiryukov advised that PHP 8.0 release is scheduled for November 26. The dev note does a great job summarizing the changes and challenges PHP 8.0 brings for WordPress core and plugin or theme authors, so give it a read. There are a few components without a maintainer, and some that could use more maintainer support, a challenge was raised to people to consider contributing in this way, it’s not as hard as you might be thinking! See the discussion here and pick a component to dive into.

Open Floor


The Marketing Team is working on a social media pack on version 5.6, if anyone would like to support this, please let @lmurillom or @abhanonstopnewsuk know. Follow the conversation on slack 

Questions and answers for version 5.6
Where uploaded yesterday on 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/. @abhanonstopnewsuk – “ l would like to thank everyone who has already helped with this from the release squad, core and marketing, and a big shout out to @vimes1984 and  @meher who have led these questions and answers work with me over the last month.”

There are a number of tickets coming in since 5.6 RC1. @hellofromtonya will be scheduling a pre-RC2 Scrub Scheduled: Nov 30th @ 1900 UTC and will drop tickets into #core channel over the next few days to escalate.

The theme/theme directory teams have two requests for feedback on the make blogblog (versus network, site)https://make.wordpress.org/themes/2020/11/18/theme-previews-in-the-time-of-blocks/ and https://make.wordpress.org/themes/2020/11/19/feedback-requested-resolution-process-for-issues-found-in-live-themes/  please review and add your thoughts.

Mike asked for more testing assistance with https://github.com/WordPress/phpunit-test-runner/issues/121 in the hopes we can get this across the line. Finally, Paal posted a note that he’s going to be focusing on improving the structure of the handbooks, watch this space to see how that develops

Next Dev Chat Meeting

The next meetings will take place on Wednesday, December 2, 2020, 07:00 AM GMT+2 and Wednesday, December 2, 2020, 10:00 PM GMT+2 in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#5-6, #5-7, #dev-chat, #summaries, #summary

Dev Chat Summary: November 18 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, November 18, 2020, 05:00 UTC and Wednesday, November 4, 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/11/04/dev-chat-agenda-october-4th-november-2020/

Announcements

RC1 of 5.6 has been released! The team would love you to help by testing the 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)., and/or by offering any translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. skills. More information can be found in the Release Candidate post.

@helen shared that the theme previewer site [wp-themes.com] is now showing starter content for the demos for Twenty Twenty One, Twenty Twenty, and Twenty Seventeen, thanks to some help from @dinhtungdu and @dd32. Helen noted that it is not yet available for themes at large; the reasons for which she’ll be sharing in a post that’ll be published soon.

Highlighted Posts

A Week in Core – November 16, 2020

Site Health Check changes in 5.6

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are starting to show up ready for final release, here’s the latest dev-notes 5.6

Updates from Component Maintainers/Focus Leads

General:
@sergeybiryukov shared that PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 release is scheduled for November 26. For WordPress 5.6, the current plan is to declare it as “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. compatible with PHP 8”. A post on make/core is coming soon, but you can see the reasoning behind this in the following 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/. conversations:
https://wordpress.slack.com/archives/C02RQBWTW/p1605646136362600
https://wordpress.slack.com/archives/C02RQBWTW/p1605646630372100

@desrosj added that the dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for this is almost complete, and will be added tomorrow [November 19].

Open Floor

@isabel_brison flagged that there are still a number of outstanding issues in relation to the editor. If you think you might be able to help out in clearing these, please take a look at the to-do column on the Gutenberg project board on GitHub.

@webcommsat shared that the Marketing Team is working on questions and answers for 5.6 for the HelpHub and working with the Training Team. The team will add the latest version to the Marketing Team GitHub at the end of this week, for those who are interested in helping with this.

@desrosj apologized for the delay in publishing the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. – this will be published by the end of the week.

@francina has started recapping the comments to the post about aligning the WP release cycle to industry standards. Right now there are very few voices, and despite the deadline for feedback stated has now passed, she would still love to hear from more people. Please review the post and share your feedback.

@whyisjake asked when the planning for the 5.7 release cycle (team etc) is going to start. @francina suspects @chanthaboune has a plan, but stressed that it would be great to see 5.6 squad members back again, and encourages anyone who has any questions about being part of the release squad to reach out to her or @audrasjb. Francesca will be adding a list of release squad roles and more information on how you can get involved in the handbook soon.

Next Dev Chat meetings

The next meetings will take place on Wednesday, November 25, 2020, 05:00 UTC and Wednesday, November 25, 2020, 20:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions.

#5-6, #dev-chat, #summaries, #summary

Dev Chat Summary: November 11 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on November 11, 2020 at 0500 UTC and November 11, 2020 at 2000 UTC, following this agenda.

05:00 UTC core dev chat

@peterwilsoncc facilitated the meeting and @mikeschroder took notes. Find the full Slack archive here.

20:00 UTC core dev chat

@laurora facilitated the meeting and @thewebprincess took notes. The full Slack archive can be viewed here.

Announcements

The WP 5.6 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. 4 has been delayed and will now be released around November 12, 2020 at 2000 UTC.

Highlighted Posts

And recent posts on the Make/Core blogblog (versus network, site) to highlight are:

Updates from Component Maintainers/Focus Leads

General: PHP8 is scheduled for November 26th, please see the PHP 8 call for testing to ensure we are ready before RC 1 scheduled for launch on November 17th. @desrosj is working on the dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase..

Site Health: Most remaining patches complete for 5.6. Dev notes remaining.

Open Floor

@mikeschroder asked for help with getting PHP8 working with the automated hosting tests, as it’d be great to have hosts running the core tests with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 before 5.6 is released. Logs from that discussion found here.

@joostdevalk sparked a lively discussion with the following statement “If we enable auto-updates for core, we should default to it for all plugins too.” It is worth reviewing the conversation.

Finally, @helen put the call out for people to leave their thoughts/comments regarding Dark Mode in Twenty Twenty-One on the recent post.

Next Dev Chat meetings

The next meetings will take place on November 18, 2020 at 0500 UTC and November 18, 2020 at 2000 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions.

Props to @thewebprincess helping to compile these notes, @hellofromtonya for proofing, and @davidbaumwald for final review.

#5-6, #dev-chat, #summaries, #summary

Dev Chat Summary: November 04 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, November 4, 2020, 05:00 UTC and Wednesday, November 4, 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/11/04/dev-chat-agenda-october-4th-november-2020/

Announcements

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. 3 of 5.6 has been released!

WordPress 5.5.2 & 5.5.3 were also released. You can read up on the technical details in this post.

Highlighted Posts

Introducing auto-updates interface for Core major versions in WordPress 5.6

What’s next in Gutenberg? (November)

Updates from Component Maintainers/Focus Leads

General:
@sergeybiryukov reminded us that PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 release is scheduled for November 26. We have two weeks until November 17 (scheduled date for WordPress 5.6 RC1) to discover and fix any remaining issues. Please see the PHP 8 call for testing: https://make.wordpress.org/core/2020/10/06/call-for-testing-php-8-0/. We need more testing on PHP 8, expanding test coverage, and creating tickets for any issues found.

Build/Test Tools:
@sergeybiryukov shared the following updates:

  • The test matrix on Travis was trimmed for older branches to remove the jobs that are no longer necessary. See #51705 for more details.
  • Multisitemultisite 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 test failures on 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/ Actions were fixed, see #51670 for more details.

Open Floor

@ahmedchaion asked if there were any plans to have a New Contributor Meeting suited to APAC timezones. The group agreed that there’s:
1. No reason  we can’t have one if there are available contributors to run it
2. And that the regular APAC Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session fulfills that gap to some extent.
@thewebprincess asked if there were any core requirements for someone willing to run a new contributor meeting and if there was any documentation available. @sergeybiryukov followed up by stating there is no documentation currently available for this, but the following links might be helpful:

The group had a lively (and lengthy) discussion on the auto-updates UIUI User interface. The full transcript of the discussion can be viewed here.

@nalini highlighted the latest Month in WordPress post. And also shared the write-ups from the WordPress translation celebrations, adding that the Marketing and Polyglots teams are now working on questions and answers to encourage translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization., including about releases.

Next Dev Chat meetings

The next meetings will take place on Wednesday, November 11, 2020, 05:00 UTC and Wednesday, November 11, 2020, 20:00 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions.

#5-5-2, #5-5-3, #5-6, #dev-chat, #summaries, #summary

Dev Chat Summary – 21 October 2020

This post summarizes this week’s meetings happening on Wednesday, October 21, 2020, 07:00 AM GMT+2 and Wednesday, October 21, 2020, 10:00 PM GMT+2 on the agenda.

0500 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat

0500 Full meeting transcript 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/.: https://wordpress.slack.com/archives/C02RQBWTW/p1599022834165200

@peterwilsoncc facilitated the meeting and took notes.

2000 core devchat

The meeting was facilitated by @laurora while @thelmachido took notes. Full meeting transcript on slack

Both groups followed this agenda.

First item: celebrating the first beta release of WordPress 5.6 on October 20! Please download the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. version, experiment with it on a test installation (not a live site!) and share any bugs you find or issues that come up.

Announcements

@annezazu announced the Widgets Screen won’t land in 5.6. A Make Core post is coming soon that will discuss where the feature is and what the next steps will be. And though the feature isn’t ready for the current release, it is still on the roadmap, and the team points out they still need feedback on the current work. You can give them that feedback, or share any other thoughts, here or on GitHub.

Highlighted Posts

Introducing Github actions for automated testing.

Please check it out! Your contributions are welcome.

Component Updates

PHP 8 call for testing

@sergeybiryukov highlighted the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher call for testing.

Build/Test Tools

Again, 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/ Actions are now running automated tests. See this post and this ticket for more.

@whyisjake is looking at a 5.5.2 release on Tuesday, October 27 or Thursday. October 29. He hopes to run a scrub tomorrow and then put the release docs together over the weekend.

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)

With the Beta 1 released, the team plans to switch gears to accessibility: namely, to review and package the Accessibility Statement feature as a 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. @jonnyvaughan and Alice Williams, who have begun coding the feature, would love some feedback and testing. Interested? Check out this GitHub repo.

Media

@mikeschroder asked for testing on #42663, which landed on October 20. He’s especially interested in your help if you write plugins that use stream wrappers.

He has two priorities:

  1. Make sure existing stream implementations still work.
  2. How hard is it to integrate those implementations with this new one?

Look for a dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. from Mike as we get closer to final release. slack

Open Floor

@garrett-eclipse opened #51584 to ask if anyone else had hit the problem. After some discussion, the group concluded it is reproducible but doesn’t appear to be a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in WP 5.6 slack

@garrett-eclipse shared that he’s been wondering if WP notices should be active or passive. He has been leaning towards the convention that Google has and was wondering if he can add that to the handbook? @pbiron mentioned that US English spelling is mentioned in the handbook. Follow the conversation here slack.

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 28, 2020, 07:00 AM GMT+2 and Wednesday, October 28, 2020, 10:00 PM GMT+2 in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#5-6, #dev-chat, #summaries, #summary

Dev Chat Summary 14th October 2020

Hello Friends! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat on Wednesday, October 15th, 2020, 05:00 UTC and Wednesday, October 15th , 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 @thewebprincess took notes. The full Slack archive can be viewed here.

Both groups followed this agenda: https://make.wordpress.org/core/2020/10/13/dev-chat-agenda-october-14th/

Announcements

  • APAC based core 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., @peterwilsoncc has taken up a role that will allow him to contribute to core 4 days a week 🎉
  • A group is gathering around issues that can be moved to a minor release to clear the path for 5.6 and address issues like removing the embed blocks for FB an Instagram due to their withdrawal of support. If you can help, here’s where to dig in https://core.trac.wordpress.org/tickets/minor @whyisjake will be organizing the release, so reach out if you want to get involved.

No Highlighted Blogblog (versus network, site) posts this week

Updates from Component Maintainers/Focus Leads

Open Floor

  • @mikeschroder observed some failing tests for some hosts and the 0500 UTC crew dug in to find the cause in a package update – resolution to add an issue to the board to be included for the next 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/ release.
  • @isabel_brison threw out that if anyone was keen to work on or review editor-related stuff, the 5.6 project board has a few things to pick up in To do and Needs Review columns :smile:
  • The state of PHP8 support in core generated a fair amount of discussion. Rather than summarize here, please review the archive of the conversation in Slack for all the detail. Major takeaways are the dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are in progress in relation to communication around the significant number of breaking changes – Helen called for a deliberate effort towards outreach of this change which has extensive discussion to follow. Furthermore @omarreiss suggests declaring WP incompatible with PHP8 with a useful perspective from @jrf in response. Lots to dig in there, and there will be marketing and outreach efforts to ensure widespread awareness.
  • @justinahinon opened a discussion with a suggestion regarding pairing existing contributors with new ones to build connection and support newbies.
  • @helen asked for a rundown on significant issues to complete before 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 is released,
    • Major Core auto-updates opt-in UIUI User interface
    • Twenty Twenty-One
    • Widgets as Blocks
    • JQuery 3.5x
    • Issues on this list

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 15 2020, 05:00 UTC and Wednesday, October 14, 2020, 20:00 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions.

Thanks to @francina for proofreading this post.

#5-6, #summaries, #summary

Dev Chat Summary 8th October 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, October 7th, 2020, 05:00 UTC and Wednesday, October 7th , 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
@laurora facilitated the meeting and @thewebprincess took notes. The full Slack archive can be viewed here .

Both groups followed this agenda: https://make.wordpress.org/core/2020/10/06/dev-chat-agenda-weds-7th-october-2020/

Announcements

No announcements today!

Highlighted Posts

  • https://make.wordpress.org/core/2020/10/01/whats-next-in-gutenberg-october/ No action needed, but posted for awareness as there are notes for 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. or 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 devs and in invite for those interested in contributing.
  • Requests for comments on Starter Content https://make.wordpress.org/core/2020/10/06/revisiting-starter-content-on-org-and-beyond/ – which is a request for comment.
  • Progress update on https://make.wordpress.org/core/2020/10/06/update-wordpress-5-6-release-progress/. No action required though a request for a graphic depiction of what the Full Site Editing simple, routine user flows was discussed. This will help give people a sense of how it’s likely to work when it does come into core as it’s currently hard to visualise something we’ve not seen before.

Updates from Component Maintainers/Focus Leads

  • Build/Test Tools, General: Continued work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support:
    • The PHP 8 Docker image has been updated to use the same PHP extensions for PHP 8 that we have on PHP 7.x
    • A new NPM task has been added to use the Composer-installed version of PHPUnit
    • * There is an ongoing effort to fix some function argument type issues reported by PHPStan (a static analyzer): #51423.
    • * Next steps: More testing on PHP 8, expanding test coverage, and creating tickets for any issues found. A call for testing was published earlier this week: https://make.wordpress.org/core/2020/10/06/call-for-testing-php-8-0/
      Question was asked: Does PHP8 support need more people involved? A: Follow the issues here PHP8 Tag in trac
  • 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., Date/Time, Permalinks: No major news this week.
  • Site Health has had some attention in the past week to go over 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.-refreshes and tickets
  • External Libraries: jQuery update has some progress too #r49101 has updated jQuery and jQuery UIUI User interface. Please test!
  • Upgrade/Install: our main ticketticket Created for both bug reports and feature development on the bug tracker. ( 50907 ) is still in progress.

Open Floor

  • The Marcomms team noted that they’re inviting feedback in relation to the About Page for 5.6 in thisGoogle form feedback is are also welcome via tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. but this form will help make it more accessible to the wider community who might not be familiar with trac and its processes.
  • It was observed that the titles for the dev chat entries in the calendar weren’t updated with the UTC specific timings so @peterwilsoncc updated them to Core Development Weekly Chat (0500 UTC) and Core Development Weekly Chat (2000 UTC)
  • #40351 (Term post re-counts scale poorly, are common and difficult to avoid) – WordPress Trac which is slated for 5.6 has a patch, but the question was asked whether there’s enough time to test properly before adding to the release, after discussion, the plan is for further testing this week, if nothing breaks it will be added to the release.
  • Discussion then went on to explore options for dummy content for testing andthe contingent posted numerous options according to individual preferences to answer the inquirer.
  • #50658 was highlighted for review: ‘has patch. Tested. Has screenshots. Missed wp5.5 deadline and tagged for 5.6. Action: pings sent to the component maintainers for review
  • Ticket https://meta.trac.wordpress.org/ticket/5463 was highlighted for feedback in relation expediting updating process for component and focus teams. Please comment on that ticket if you have feedback.
  • https://core.trac.wordpress.org/ticket/50907 needs more eyes on it and feedback added to the ticket.
  • The Yoast team have put together a short term team to focus on Twenty Twenty-One development, they’ve created a project board which you can follow here to track progress of issues
  • Reminder: next test scrub on Friday October 9th 13:30 UTC
  • Requests for testing: of https://make.wordpress.org/core/2020/09/30/call-for-testing-the-widgets-screen-in-gutenberg-9-1/ and

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 7, 2020, 05:00 UTC and Wednesday, October 7, 2020, 20:00 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions.

Props to @francina for the proofread.

#5-6, #summaries, #summary

Dev Chat Summary: September 30 2020

Hello! Here’s what happened in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev chat on Wednesday, September 30, 2020, 05:00 UTC and Wednesday, September 30, 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/29/dev-chat-agenda-september-30th-2020/

Announcements

@annezazu shared that the navigation screen is being put on pause to focus on Widgets screen as a stronger candidate for 5.6 – there has since been a post added to the core blogblog (versus network, site), which you can read in more detail here the post includes a call out for testers. If you’re available to help you can get details here.

@francina announced that weekly Test Scrubs will be starting this Friday, October 2nd at 13:30 UTC: https://make.wordpress.org/core/2020/09/29/test-scrub-for-wordpress-5-6/

Highlighted Posts

Proposal: A font enqueue API for WP core – Please add any thoughts or comments on the post.

Updates from Component Maintainers/Focus Leads

Build/Test Tools:
@sergeybiryukov shared that work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support has continued. All known unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. issues have been addressed, and the tests are now passing on PHP 8. #50913 includes most of the progress on this, some work was also done in other related tickets: https://core.trac.wordpress.org/query?keywords=~php8

Next steps for PHP 8 support:

  • Docker image needs to be updated to use the same PHP extensions for PHP 8 that we have on PHP 7.x: gdmbstring, etc. There is a PR by @desrosj waiting for review: https://github.com/WordPress/wpdev-docker-images/pull/36. If anyone is able to help with that, please do.
  • There is an ongoing effort to fix some function argument type issues reported by PHPStan (a static analyzer): #51423.
  • More testing on PHP 8, expanding test coverage, and creating tickets for any issues found. @andraganescu and @desrosj are working on a call for testing to be published later.

MarComms:
@yvettesonnefeld shared that they have posted the ticket for the About page, with a brief attached. Please add any features that should be highlighted on the About page and release post via a comment on the ticketticket Created for both bug reports and feature development on the bug tracker..

A Google form is being created for those who are struggling to master TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

Upgrade/Install:
@audrasjb shared that most of the work is currently focused on Core major versions Auto-updates: #50907

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):
@sarahricker shared that @jonnyvaughan and Alice Williams are well underway on the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. being developed for #50673. A summary of where they’re at can be found here.

Open Floor

Regarding the Application Passwords Merge Proposal discussed last week, @timothyblynjacobs stated “I think we’ve added the necessary functionality to address the concerns shared in the comments (via filters).”

@janthiel highlighted a small change proposal regarding the quote calculation caching in multisites. The ticket has been around for years now, and implementing it would be a massive performance improvement for sites with huge media libraries and/or slow file systems like NFS using the WordPress Quota system.

@peterwilsoncc wanted to bring attention to #45114. You can read the conversation here. The brief conclusion was to outline 3 options to resolve this (wont fix, move hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., add new hooks) and take a vote. Please add any contributions to the conversation on the trac issue. Comment 27 onwards is a good place to start.

@chanthaboune shared the “sure to ship” items for WP5.6 right now. The struck out items won’t make it to 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., based on posts/tickets/comments/feedback/etc. A full post detailing the changes will be published soon.

Ship: Navigation menus 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. and screen in Core.
Ship: Automatic updates for major WordPress Core releases (opt-in).
Ship: New features from the block editor upgrades.
Ship: Widgets-editing and 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. support in Core.
Ship: Default theme, including an FSE compatible version.
Ship: PHP 8 support.
Ship: Public beta of Full Site Editing.
Ship: oEmbed changes
Ship: Misc patches/proposals from the community

@azaozz has been going back and forth on the jQuery update to 3.5.1 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 would welcome more eyes on: https://github.com/WordPress/wordpress-develop/pull/536, stating that the more difficult part is updating UIUI User interface to 1.12.1 as the build process for that version is completely different. If you have any thoughts, please leave them on the ticket.

WP Accessibility Day is taking place this Friday, October 2nd. More details can be found here: https://wpaccessibilityday.org/

And the week-long WordPress Translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. Day celebrations are currently taking place! Find out more about the full schedule of events here: https://wptranslationday.org/2020-events/

@helen welcomed feedback on whether some round 2 iterative work should be done on Starter Content to get it back to its original intended goal of also enhancing theme previews on 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/. You can see the start of the conversation here, and Helen will be following up with a make/core post.

Next Dev Chat meetings

The next meetings will take place on Wednesday, October 7, 2020, 05:00 UTC and Wednesday, October 7, 2020, 20:00 UTC in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. Please feel free to drop in with any updates or questions.

#5-5-1#5-5-2#5-6#dev-chat#summary

#5-6, #dev-chat, #summaries, #summary