Tag Archives: meeting

Jorge Costa 12:41 pm on October 24, 2023
Tags: , , , meeting, ,   

Editor chat summary: Wednesday, October 18, 2023

This post summarizes the weekly editor chat meeting on Wednesday, 18 October 2023, 14:00 UTC, held in Slack.

Agenda of the meeting at https://make.wordpress.org/core/2023/10/17/editor-chat-agenda-wednesday-18-october-2023/.

Announcements

Last week we had security and maintenance releases for both WordPress and the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 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: https://wordpress.org/news/2023/10/wordpress-6-3-2-maintenance-and-security-release/ and https://github.com/WordPress/gutenberg/releases/tag/v16.8.1. Please make sure they are both updated.
WordPress 6.4 RC1 was released on October 17 https://wordpress.org/news/2023/10/wordpress-6-4-release-candidate-1/.

Open floor

There were two questions raised by Andrei Glingeanu.

Question 1:

Is the possibility of adding custom tabs here prohibited intentionally?

Print screen of the 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. inspector sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. with a custom item added at the side of the page and block.

@jorgefilipecosta said:

 We never added extensibility api’s to create new tabs there. There was not an intentional decision to never do it, but there was also never a decision to do it. I guess the best bet for now is to create a custom sidebar.

Question 2:

Is there a standard way of outputting dynamic css for a custom block besides putting it inline in style="" attributes and without outputting <style> tags in the edit function of the block?

@jorgefilipecosta said:

In my personal opinion, it depends on the case:

  • If the dynamic CSSCSS Cascading Style Sheets. styles you want to add should affect just a single instance of the block I think using the style attribute may be the way to go.
  • If the dynamic CSS styles you want to add should affect all the instances of your custom block, I guess a good option is to use the global styles filters and filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. to add the styles you want for the block dynamically.
  • If it is dynamic but there is a limited set of different possible styles e.g.: dynamic but there are like 5 different style configurations. Probably creating classes as part of the block styles CSS and then dynamically deciding which class to add to the block seems to be the way to go.

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

Brian Alexander 11:44 pm on October 18, 2023
Tags: , , , meeting,   

Dev Chat Summary, October 18, 2023

The WordPress Developers Chat meeting took place on October 18, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Announcements

Highlighted Posts

  • WordPress 6.4 Release Candidate Phase: Learn or refresh your knowledge of what happens during 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).. Questions? Please post them in the comments.
  • 6.4 Dev Notes: It’s been a busy time in the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site)! Stay updated on the latest technical updates by checking out posts conveniently tagged with #dev-notes-6-4. Major props to 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, 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. authors and wranglers who have worked tirelessly to make this happen! 🎉
  • WordPress core is now using Playwright for all browser-based tests: e2e fans rejoice! This milestone promises improved test stability and better options for authoring tests. If you’ve been holding back while the migrationMigration Moving 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 has been underway, now is a great time to jump back in to improve Core e2e coverage.
  • What’s new in Gutenberg 16.8 (11 October): Check out updates to the Cover 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., Font Library, and more in this roundup of the latest release.

Release Updates

WordPress 6.4

RC 2 is scheduled for next Tuesday, October 24, 2023.

Stay in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with 6.4 by following:

Additional release updates from the floor included:

  • A question was raised in #6-4-release-leads about removing some 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/-only packages from the next npm package update to Core.
  • Some 6.4 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. drafts are still needed for a couple of areas, so a gentle reminder was raised to keep the official 6.4 Documentation Tracker updated with latest progress. Reach out on the Tracker for help or to the Documentation release group in the #6-4-release-leads channel.

WordPress 6.3.2

  • WordPress 6.3.2 – Maintenance and Security release: This follow-up to 6.3.1 introduces several 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 security updates. Make sure to update!
  • Keep tabs on the #6-3-release-leads channel for future updates.

Open Floor

Automated Welcome/Signposting for #core

@webcommsat asked if Core would consider utilizing an automated messaging/workflow tool similar to that used by Training. When users joined the channel, they would receive a private message from Slackbot that includes channel-specific info and links, such as the Dev Chat schedule, or orientation for new contributors and contributor days. Abha agreed to draft a proposal to seek broader input from Core and new contributors.

Use of noopener noreferrer in New Window/Tab Links

@presskopp had a question regarding use of rel="noopener noreferrer" in links with target="_blank", which were supposed to have been removed. To help resolve instances where this unneeded behavior remains (in Core and Gutenberg), contribute to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. #53843: Remove adding of rel=”noopener” to links with target=”_blank”.

Next Meeting

The next meeting will be on October 25, 2023 at 20:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel.

Props @webcommsat for peer review of this post.

#6-3, #6-4, #dev-chat, #meeting, #summary

Emily Clarke 11:35 am on October 17, 2023
Tags: , meeting, ,   

Performance Chat Agenda: 17 October 2023

Here is the agenda for this week’s performance team meeting scheduled for Oct 17, 2023 at 15:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.

This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Jorge Costa 11:11 am on October 17, 2023
Tags: , , , meeting   

Editor Chat Agenda: Wednesday, 18 October 2023

Facilitator and notetaker: @jorgefilipecosta.

This is the agenda for the weekly editor chat scheduled for Wednesday, 18 October 2023, 03:00 PM GMT+1.

This meeting is held in the #core-editor channel in Making WordPress 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/..

  • Announcements
  • Project updates
  • Task Coordination
  • Open Floor

If you are not able to attend the meeting, you are encouraged to share anything relevant to the discussion:

  • If you have an update for the main site editing projects, please feel free to share it as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

Abha Thakor 10:53 pm on October 11, 2023
Tags: , , , meeting,   

Dev Chat summary, October 11, 2023

Summary of the WordPress developers chat meeting in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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.

Key links

Start of the Dev Chat meeting on the Core Slack

Dev Chat agenda followed – thanks to @webcommsat for preparing.

Announcements

  • WordPress 6.4 Beta 3 is available: Please help test and make the release the best it can be! Thanks to everyone who contributed toward 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, as well as those who came and facilitated the release party on October 10. Note the Twenty Twenty Four images issue has been resolved, and the images are rendering correctly in Beta 3.
  • The WordPress 6.3.2 minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. has moved to tomorrow, October 12, 2023 (more information under release updates to follow).

Highlighted Posts

  • Four Weeks in Core: Many thanks to @audrasjb for this update covering the amazing activity in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between September 4 and October 9, 2023:
    • 269 commits
    • 337 contributors
    • 295 tickets created
    • 43 tickets reopened
    • 277 tickets closed
  • Reminder: Hallway Hangout: Working session on consolidating various navigation modes: Taking place on November 15, 2023 at 16:00 UTC. This is part of efforts to improve 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) in the Site Editor.
  • The Dev Blog is looking for a writer for the following topic: How to add commands to the command palette. Please respond on the 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/ ticketticket Created for both bug reports and feature development on the bug tracker. if you are interested.

Release Updates

Next major releasemajor release A 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.: 6.4

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). 1 is scheduled for next Tuesday, October 17, 2023. 

This hallway hangout is happening tomorrow, October 12, 2023: What’s new for developers in WordPress 6.4. 

Stay in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with 6.4 by following:

6.4 tickets that need attention

@rajinsharwar highlighted #52529 and requested testing of the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to see if they can replicate the errors mentioned.

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.

@webcommsat for the release documentation group: A reminder that 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. is due to be published next week. This is so the link can be included in the release’s About Page. It would be great to have as many dev notes ready in draft as soon as possible, so they can have a final review and be published.

6.4 dev notes tracking project board for reviews and publishing is in progress.

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/ – Some Gutenberg tickets have already been labelled and clustered. There is a significant list that is being clustered and labelled, and these will then get added to the documentation tracker for 6.4. The tracker will show the edit, review and publish status of the dev notes – the view that will be most useful for this is ‘dev notes’. For Gutenberg, the wrangling and discussion on clustering and inclusions will happen in the Gutenberg tracker. Thanks to @bph who is going to be helping with this.

Core – If you are a component maintainer, and have not already shared that you are working on 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, 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. relating to a Core Trac ticket or cluster of tickets, please add a comment on this issue and link any google docs, and we will populate the tracker with this.

For End user and Core tickets, the labelling is continuing. As we are being advised of dev notes needed or in progress by maintainers, they are being added to the documentation tracker.

For performance dev notes, issues are being added to the documentation tracker once confirmed for reviews and publishing purposes. Wrangling and discussion of inclusion of tickets is happening on the Performance GitHub ticket.

Reviews – If any devs are able to assist with technical reviews of dev notes if needed, let @webcommsat know to update the list.

Next minor release: 6.3.2

  • *A note on the 6.3.2 release schedule change:* In order to accommodate the need for hosts to deal with an important curl 8.4.0 security release on Wednesday, the 6.3.2 final release has been moved to Thursday, October 12, 2023.
  • Thanks to everyone who led, supported, helped test, raised issues, and helped to fix tickets in these releases! 

Gutenberg

Gutenberg 16.8.0 shipped during dev chat. An update on this release will be published soon and will be findable on the tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) #gutenberg-new on the Make/ Core blogblog (versus network, site).

Component Maintainers requests

@rajinsharwar highlighted Trac ticket #55335. Requested confirmation if it should be considered 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..

Open floor

No additional items were raised. A reminder of the Field Guide and dev notes was shared.

Props to @webcommsat for the agenda and summary, and to @ironprogrammer for facilitating the meeting and reviewing the summary.

#6-3, #6-4, #dev-chat, #meeting, #summary

Emily Clarke 9:27 am on October 10, 2023
Tags: , meeting, ,   

Performance Chat Agenda: 10 October 2023

Here is the agenda for this week’s performance team meeting scheduled for Oct 10, 2023 at 15:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.

This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Abha Thakor 2:46 pm on October 5, 2023
Tags: , , , meeting   

Developer Blog editorial meeting summary: October 5, 2023

A complete transcript of the meeting can be found in the #core-dev-blog channel in Making WordPress 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/..

Notes of the last editorial meeting on September 7, 2023 – thanks to @bph

Attendees: @bph, @milana_cap, @greenshady, @marybaum, @webcommsat, @oglekler

Site updates and new posts

Since the last editorial meeting, the following posts have been completed by writers and reviewers.

@bph shared a huge thank you to the writers, and their reviewers! Fantastic job!

Project board

Posts in progress

Posts for review

At the time of the meeting time, these posts were in need of review.

2nd review: New developer focused workflow article about how the login and registration works in WordPress.
1st review: A tutorial about the highlights of the browser and focus modes of the Navigation Block
1st review: #151 Type series post 3: Setting body-conscious type for long-form text#156

Action: comment on the 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/ issue if you can review.

Posts on the to-do list

These were all approved topics, with writers assigned:

On the to-do list

@webcommsat to look at how to highlight call for writers on Dev Chat agendas post 6.4.

Posts that need writers

Two topics are still looking for writers:

Actions: If you know someone or want to write it yourself, post in the Developer-Blog channel on Slack.

Posts for approval

The group approved one new topic:

Open floor

Discussion to encourage writers to share GitHub tickets, Google Docs, public preview links to accompany a call for review in Slack to help reviewers. When writers and reviewers contributing in opposite time zones, these links can be particularly helpful.
Action: to guide contributors to use GitHub to capture comments/ changes, including when posts have moved to the CMS phase.

In the last quarter, many new writers have been inducted to the Dev Blogblog (versus network, site). Proposed a post for new writers with input from contributors recently joined.
Action: @webcommsat and @bph to take forward the post.

Agreement to allocate Documentation badges to contributors for writers and reviewers of the Dev Blog.
Action: @bph and @milana_cap

#core, #core-dev-blog, #dev-blog, #meeting

Emily Clarke 11:32 am on October 3, 2023
Tags: , meeting, ,   

Performance Chat Agenda: 3 October 2023

Here is the agenda for this week’s performance team meeting scheduled for Oct 3, 2023 at 15:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.

This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Abha Thakor 8:48 pm on September 28, 2023
Tags: , , meeting,   

Dev Chat Summary, September 27, 2023

The notes from the weekly WordPress developers chat which took place on September 27, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key links

Announcements

WordPress 6.4 Beta 1 is available – please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed to getting this 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. 1 and those who came and led the release party on September 26.

Highlighted posts

The following were listed on the agenda but not highlighted during the meeting due to a discussion on 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/ and Beta 1:

  • WordPress Performance team has a new version of the Performant Translations 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 with improved compatibility and performance. It has more than 1000 installations as at September 26, 2023. More testers will be needed and @swissspidy has created a proof-of-concept core patch in the meantime.

Release updates

Next major WordPress release: 6.4

WordPress 6.4 Beta 2 is scheduled for October 3, 2023.

Discussion at Dev Chat focused on Gutenberg 16.7 and WordPress 6.4. More on this discussion will be available in a separate post on the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel soon. Link to start of the discussion on Slack.

@joemcgill suggested adding comments to the discussion from the WordPress Community Summit: Community Summit Discussion Notes: Aligning processes and contributions between WordPress Core and Gutenberg.

Stay in the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with 6.4 by following:

Next minor WordPress release: 6.3.2

Call for ticketticket Created for both bug reports and feature development on the bug tracker. reviews by @joemcgill 

The scrub on September 27, 2023 focused on the 6.3.2 milestone in preparation for another minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..
Five tickets in the milestone remain to be fixed in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision..
Request/ Action: reviews are needed of these tickets to move them forward, and if they are able to get in this week. Of note, are a few that need to be synced from the Gutenberg repo. If someone has planned to help with this, please comment in the 6.3 releases leads channel on Slack.

Also six tickets that are fixed, but need to be back ported to the 6.3 branchbranch A 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"..
Request: if committers have some time to review and help, that would be a big help.

Discussion followed in Dev Chat and after on potential target dates for the next minor, which would allow time for work to be wrapped up on the remaining tasks. Provisional dates included October 10, earlier in the day from Beta 3. @joemcgill able to help with the 6.3.2 release and noted contributors are still need to be identified for official release roles.
Action: If you can volunteer to help with 6.3.2, comment in the 6.3 release leads channel on Slack. The date for the release is still under discussion.

Gutenberg

Help requests: Components maintainers & Tickets

No other tickets were raised in the agenda comments or after Dev Chat.

Open Floor

This item did not feature at this week’s Dev Chat due to time constraints.

Next meeting

The next meeting will be on Wednesday October 4, 2023, at 20:00 UTC.

Props to @webcommsat, @nalininonstopnewsuk, @ironprogrammer, and @hellofromtonya and @marybaum for review.

#6-4, #dev-chat, #meeting, #summary

Paal Joachim Romdahl 9:49 am on September 26, 2023
Tags: , , core-editor core-editor-agenda, meeting   

Editor Chat Agenda: 27 September 2023

Facilitator and notetaker: @paaljoachim

This is the agenda for the weekly editor chat scheduled for Wednesday, September 27 2023, 03:00 PM GMT+1. This meeting is held in the #core-editor channel in the Making WordPress 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/..

  • Announcements
  • Project updates
  • Task Coordination
  • Open Floor – extended edition.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-core-editor-agenda, #meeting