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 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, #summary

Dev Chat Summary – 23 August 2020

Greetings! Here’s what happened in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Wednesday, September 23, 2020, 07:00 AM GMT+2 and Wednesday, September 23, 2020, 10:00 PM GMT+2 on the #agenda.

0500 core devchat

@thewebprincess led the discussion in the meeting was a bit slow the team decided to run a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub. Find the full Slack archive here.

2000 core devchat

@laurora facilitated the chat and @thelmachido took notes. Find the Full Slack archive here.

Announcements

To see an overview of what’s happening keep an eye on make/updates, we’ve got quarterly updates from the team coming soon.

Highlighted blogblog (versus network, site) posts

Dual licensing Gutenberg under GPL v2.0 and MPL v2.0
We need to gather feedback on the proposal to dual-license 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/ under GNU General Public License, v2 (GPLGPL GNU General Public License. Also see copyright license. v2) and the Mozilla Public License v2.0 (MPL v2.0). Please share your perspective on the proposal from Maxime by adding comments to the post.

Introducing the next WordPress default theme – Twenty Twenty One Weekly meetings on the theme will start on Monday 28 September at 15:00 in #core-themes. @chanthaboune clarified that the team will be shipping one theme, based on Seedlet, bundled with the release and they will be exploring a second FSE theme, after the first is stable, that is not bundled with the release. Besides what was discussed in 5.6 planning post, FSE will now be done in the Gutenberg PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party as a 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. feature. See what the team said in the full slack discussion and another on-going discussion is going to be opened on make/core.

Proposal on REST API Authentication / Application Passwords
George Stephanis has put together a proposal for this, the hoped timeline for this proposal is version 5.6 but the team is not yet certain. There have been attempts to get other authentication mechanisms to a considerable state but none have been proposed for core as yet. See what the team contributed to the discussion in slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. The discussion from here on out will be on #core-passwords even though they had temporarily been in #core-restapi. Feel free to join the discussion there.

How gather updates from component maintainers & focus leads
Go through the post and share your opinion on the best way to gather updates as we are getting closer to release. Please share your perspective by commenting on the post by Wednesday 30 September.

Facebook embeds being deprecated
How will cached embed look after the deprecation date?. There is need to test and collect data on how the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. scripts included in the embed will look after deprecation. How will the marketing crew share this information and more broadly with users as a whole?. These are some of the discussions that will be wrapped up in the comment section of the post.

Component maintainers

Build/Test Tools
Continued work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support. With quite a few fixes to unit tests and some fixes to core, this brings the tests from 87 errors and 331 failures on PHP 8 a couple of weeks ago (when the work has just started) to only 5 errors and 17 failures now (still to be addressed). Ticketticket Created for both bug reports and feature development on the bug tracker. #50913 includes most of the progress on this, some work was also done in other related tickets here.

For 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. component one change was committed this week. The Default Language networknetwork (versus site, blog) option in 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 now has a language icon next to it. View ticket #51359.

Menus & Widgets have a couple of tickets that are waiting for committers to have a look at them.

Upgrades & Install the first 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. for Major Core auto-updates ticket has been added, also there are a couple of tickets that are waiting for committers to have a look at them.

Additional eyes needed on testing and review for backlog on the Privacy component.

No updates of note this week from Date/Time, Permalinks or Site Health.

Open Floor

@ramiy put together a Post & Infographic on WordPress release facts & stats.

@enricocarraro is working towards making WordPress Strict CSP-compatible. Inline scripts refactoring #39941 and Inline event handlers and JavaScriptJavaScript JavaScript 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/. URIs refactoring #32067. If anyone could review his PR that would be greatly appreciated.

Next Dev Chat meetings

The next meetings will take place on Wednesday, September 30, 2020, 07:00 AM GMT+2 and Wednesday, September 30, 2020, 20: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-5-1, #5-5-2, #5-6, #dev-chat, #summary

Dev Chat Summary: (5.6 Week 4)

Greetings! Here’s what happened in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Wednesday, September 9, 2020, 07:00 AM GMT+2 and Wednesday, September 9, 2020, 10:00 PM GMT+2 on the agenda.

0500 core devchat

@thewebprincess led the meeting and took notes. Find the full 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/. archive here.

2000 core devchat

@laurora led the chat; @thelmachido took notes. Here’s the full archive.

Both groups followed this agenda: https://make.wordpress.org/core/2020/09/08/dev-chat-agenda-september-9th-2020/

Announcements

We started by celebrating WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Ogijima in Japan over the weekend! 

@thewebprincess also highlighted a post by Shinichi Nishikawa about how they set up the tech and will share the link when she finds it.

Highlighted blogblog (versus network, site) posts

Timezones and Daylight savings:

After some discussion across timezones, the two dev chats have agreed to pin meeting times to UTC and let people adjust calendars locally. If the changes mean fewer people at meetings or involved in the project, several folks noted we can also change back.

The version 5.5 release team is still looking for feedback

Please share your perspective on the process — especially what people and teams can do to make future releases smoother for everyone. Please comment by Saturday at 8:00 UTC.

What’s next in Gutenberg

@annezazu updates the community once a month on all things 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.. It’s a great way to stay informed (planning your 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 or theme roadmap?) and get involved!

A comment on the agenda post:

 @pbearne asked for feedback this ticket. @peterwilsoncc answered and will give him  design feedback.

Component maintainers

Upgrade/Install 

Will explore adding some UIUI User interface elements to manage email notifications on plugin and theme auto-updates.

Privacy 

@carike reported in: “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.” 

No updates of note this week from 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, Options/MetaMeta Meta 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., Roles, Menus & Widgets, Build/Test Tools or Customize.

What if a component maintainer can’t make devchat?

After some discussion, this request from the group: Please add your updates as a comments on the Agenda post. 

Open Floor

@thewebprincess asked the people represented to call out the areas they’re focusing on. 
That morphed into a conversation about people’s desire to dig into contributing to E2E testing. At first, it looked imperative to wait for progress from the working group mentioned here – but the group decided there’s no real block to diving in now.

  • Should there be a 5.5.2? 
  •  Ever thought about being a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.? Here’s how you get there.
  • How can we help someone new — or even just watching from the sidelines —  find their place, or is it trial and error? See what people said in the full discussion.
  • One of those quizzes you get on social media all the time, “find your WordPress spirit animal”  led us to this tool, which the WCEU team used for contributor days. How could people use this — or a version — inside teams?

Next Dev Chat meetings

The next meetings will take place on Wednesday, September 9, 2020, 07:00 AM GMT+2 and Wednesday, September 9, 2020, 10:00 PM GMT+2 on the agenda.

 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-5-1, #5-5-2, #5-6, #dev-chat, #summary

Dev chat summary, July 8, 2020

@whyisjake hosted from this agenda, edited by @marybaum.

Announcements

WordPress 5.5 beta 1 landed yesterday! Tell everyone you know to download it, test everything and try to break all the new features—that’s what 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. releases are for.

@audrasjb  shared some stats: as of Beta 1, WordPress 5.5 has 190 new core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org.! A lively discussion followed, covering stats and going back several years, in some detail. Check it out here.

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/ 8.5 is live!
https://make.wordpress.org/core/2020/07/03/whats-next-in-gutenberg-july/

This is the last Gutenberg release going into WordPress 5.5 and is the major focus for this month.

From now until the final release of WordPress 5.5, Gutenberg is also in a feature freeze. That means the only tickets that will move on are bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes and code regressions; everything else will get punted to 5.6 or a future release.

Another result of the feature freeze is that TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and the Gutenberg should both see fewer last-minute commits. So look for the Beta 2 release party to start a little earlier next week (July 14) in a bow to our European contributors’ schedules.

@pbiron  #50449 could use some 
from those who are knowledgeable about RTL
#50449: Sitemap style for RTL sites

Component check-in

@marybaum announced a schedule change for the about page. She’ll attach the copy and layout to the ticketticket Created for both bug reports and feature development on the bug tracker. for 5.5 on Friday. She issued shoutouts to new contributors @abhanonstopnewsuk and @yvettesonneveld for their research with folks in the Marketing team, and @estelaris for in-depth research in design.

@justinahinon updated the group on 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, and 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 5.5 and issued a call for writers. You can see progress on the Trac notes on this Google Sheet  and Gutenberg-related notes here on GitHub.   

Open Floor

@desrosj has a post coming soon that will focus the ongoing discussion of exactly which bugs and tasks get the ticket love in two periods: the beta-to-RCrelease 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). period (for 5.5, that’s now: it started July 7 and will run until RC1 lands on July 28) and the RC-to-release period (for 5.5, the two weeks from July28 to August 11).  

For now, you can see earlier discussion on the topic here.

Finally, @whyisjake brought up a pull request that got his attention because of licensing issues it raises for part of the contributor toolchain.

#5-5-2, #devchat, #summary

#5-5, #dev-chat