Dev Chat Agenda: September 2nd 2020

Here is the #agenda for this week’s meetings happening at:
Wednesday September 2nd 05:00 UTC and Wednesday September 2nd 20:00 UTC.

Please share any items you’d like to include in the comments below.

  • Announcements
  • Highlighted blogblog (versus network, site) posts 
  1. Deprecated JS globals – No action required, posting for awareness
  2. 5.5.1 – No action required, posting for awareness
  3. Core Chat – Timezones and Daylight savings – Request for comments please
  4. Bug Scrub Schedule No Action required: Posted for awareness
  • Calls from component maintainers
  • Open Floor

If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat meetings will be held on Wednesday September 2nd 05:00 UTC and Wednesday September 2nd20:00 UTC These meetings are held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-6, #agenda, #dev-chat

Dev Chat Summary: August 26 (5.6 Week 2)

This post summarizes the dev chat meeting from August 26th facilitated by @thewebprincess on this agenda.

Full meeting transcript on slack

General Announcements

See @audrasjb post for details on the scheduled maintenance release for WordPress 5.5.1 after a handful of bugs were identified on WordPress 5.5 “Eckstine”. The first 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). is planned to be on Thursday, August 27, 2020, and the Final release planned to be on Tuesday, September 1st, 2020 estimated time 20:00–21:00 UTC or later depending on work to be done on the remaining tickets.

Highlighted blogblog (versus network, site) posts

Components check-in and status updates

The first CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. is being hosted today at 4pm EDT in the #core-css channel. One hour before the weekly Core CSS chat.  

@carikee flagged milestone tickets for privacy initiatives that still open and need to be looked at #51092, #51110 & 51144.

There is nothing of note from the Build/Test Tools component at the moment other than the before mentioned post about PHP updates.

Open Floor

The meeting pivoted into a 5.5.1 pre-RC scrub run

Ticketticket Created for both bug reports and feature development on the bug tracker. #50910 has had some testing but could use some more tests.  It is hopefully going to land for 5.5.1-RC1, so the more eyes the better similarly for #51129.  

@carikee asked committers for their input on whether to use the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. to expose user consent on the front-end. Also, the need to add the extra 10KB or so to expose wp.data to the front end.

@audrasjb flagged  5.5.1 milestones that need to be cleared and @pbiron also flagged 5.5.1 tickets that are still open.  

The meeting continued as a 5.5.1 pre-RC scrub run by @desrosj.

Next Dev Chat meeting 

The next meeting will take place on Wednesday, September 3, 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-5, #5-5-1, #5-6, #core, #summary

Dev Chat Agenda for August 26, 2020

Here is the #agenda for this week’s meeting happening later today: Wednesday, August 26, 2020, 10:00 PM GMT+2. Please share any items you’d like to include in the comments below.

  • Announcements
  • Highlighted blogblog (versus network, site) posts 
  1. Discussion on the proposal to drop support for old PHP versions via a fixed schedule
  2. Request for Input: Consent Preferences for Logged In Users (Consent API)
  3. Request for comments on Dev Chat – APAC Edition Meeting Summary – August 20 2020
  4. Timing of release WordPress 5.5.1
  • Calls from component maintainers
  • Open Floor

If you have something else you want to include to the agenda, please mention it in the comments below.

The #dev-chat  meeting will be held on Wednesday, August 26, 2020, 10:00 PM GMT+2. This meeting is held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-5, #5-5-1, #5-6, #agenda, #dev-chat

Dev Chat – APAC Edition Meeting Summary – August 20 2020

@peterwilsoncc called us to order and introduced @thewebprincess as the release coordinator and handed the chat over to her facilitation. 

The chat started out loosely following the same agenda as the earlier chat celebrating the commencement of the new release and release squad.

This sparked an excited response about having an APAC based release coordinator and a cheeky question about whether or not the release party would now fall into APAC timezones as a result. (Let’s cross that bridge when we come to it).

We also highlighted the same two posts for review.

Open floor

As it was initially a fairly quiet gathering @thewebprincess took the opportunity to ask some probing questions about what it’s like to contribute to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. when you’re based in the APAC timezones; specifically “What are the biggest challenges to contributing from this part of the world? And what more could be done to help alleviate those challenges?” 

There were some great responses to arise out of this conversation, which you can read in detail here

There was agreement that the advent of dev chat and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. in APAC timezones have made the feeling of isolation from the core conversations has lessened somewhat which is great to hear.

The regional participants are also really hopeful that having release leadership based in this timezone will be a really positive step forward to increasing the cohort of participants in the region. 

We then discussed steps to help improve participation in the APAC region, these were the areas we covered:

  • @webcommsat advised that the marketing team have an initiative under way to help promote different meetings – so next steps is for a chat to happen to talk about what that might mean for APAC dev chat (and dev chat in general).
  • Making the APAC dev chat a bit more visible by taking and posting notes after the call (we have made a commitment to do this going forward, starting with these notes).
  • We then discussed the timing of the meeting and whether moving the APAC chat to before the Americas/EMEA one would help reduce barriers to entry for APAC participants (opening for discussion below).
  • Changing the language used to describe each dev chat in order to give them equal weight as a means to help increase participation/perceived value.

Requests for Comment

  1. The consensus for the members present was that there would be significant benefit in moving the APAC call forward (earlier) by 24 hours. This would mean:
  • The agenda notes would need to be posted 24 hours earlier than the APAC call to allow both discussions to follow similar agendas
  • There may be an increased need for maintainer teams to add their updates to the agenda post for discussion in the chats as most maintainers won’t be available for the earlier call
  1. Adjusting the language around how we describe the dev chats to give each equal weight – currently we have ‘dev chat’ and ‘APAC dev chat’ let’s discuss what a more equable format might look like… here are a couple of options that were thrown in to the call such as using UTC time to differentiate chats (2000UTC dev chat or 0500UTC dev chat), using regions – America/EMEA Dev Chat and APAC Dev Chat or something else…

What do you think?

Before making such changes it is important to open this up for discussion so that all interested/affected parties might add their thoughts to the conversation, we’d love to hear from you below if you have anything to contribute.

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

Dev Chat Meeting Summary – August 19, 2020

@thewebprincess facilitated the chat on this agenda.
Meeting recap by @laurora with @marybaum editing.

Full meeting transcript on Slack

Announcements

This meeting marked the official start of the 5.6 release – run by an all-woman team.

@yvettesonneveld summed it up: “Tonight we’re writing history!”

In another first for WordPress, @webcommsat said the 5.5 Question and Answers for Developers is in its final fact-checking.

Highlighted posts

Upcoming releases

WordPress 5.5.1

@audrasjb will run a 5.5.1 bugs scrub next Monday at 20:00 UTC.

Components check-in and status updates

@johnbillion  reminded the group that if you’re interested in helping maintain a component, whether active or not, feel free to speak up—to current maintainers, project leads or release leads.

AND if you’re a current maintainer who needs to step back for any reason, please feel free to do that at any time. Again, please pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” a release or project lead. 

@jeffpaul flagged that for 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//editor-related items intending to ship in 5.6, it would be helpful to understand what may be needed from the other coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. component teams to ensure we have maintainers / committers / etc. ready to help.

An update on build/test tools from @jorbin: The top priority is #46149 — critical to support PHP8.

From Upgrade/Install, @whyisjake said he’s excited about the core auto-updates coming in #50907 and would love some feedback on getting started.

The 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 team has no firm plans for 5.6, but @johnbillion would like to reboot weekly chats again and carry on with the mini roadmap that started with default 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. values landing in 5.5.

On themes, @williampatton shared that the main goal this release cycle was to help unblock anything that #core-editor hits snags with.

@francina pointed out that the plan for 5.6 calls for a new default theme—ideally, one that starts to showcase 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. editor in template parts outside the_content.

Open floor

5.5.1

@joostdevalk raised 5.5.1 timing, since #50999 has unleashed a heavy support burden on his team.

The group supported a faster 5.5.1 release; there will be 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. scrubs on Friday and Monday, after which the team will make more concrete plans.

See the full discussion here.

Top Comments 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

@francina shared a plugin used on the Community Team blogblog (versus network, site) called ‘Top Comment’. It adds a final comment that recaps all the other comments in a discussion—a handy way to summarize discussions that have been going on a while.

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

#5-5-1, #5-6, #dev-chat

WordPress 5.6 Release Planning

Kudos to the wonderful group of people who contributed to the successful release of WordPress 5.5 yesterday!  We now turn our focus to the final 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. of the year with WordPress 5.6.

Release Squad

As @chanthaboune noted back in March, WordPress 5.6 will feature an all-women release squad with the hope of increasing the number of women who have experience on a release squad and return as contributors to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and elsewhere.  Then in May when the 5.5 release squad was announced it also noted many of the 5.6 release squad members who would shadow the 5.5 team and learn the release process.  With @chanthaboune on sabbatical until 21 September 2020, I have the pleasure of sharing the 5.6 release leads and the various cohort groups who will be supporting those leads, as well as the release scope and schedule for 5.6.

Release Scope

The following are the remaining goals for the year that are targeted as part of WordPress 5.6.

  • Complete: Convert the widgets-editing areas complete.
  • Complete: Remove support for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 5.6.x.
  • 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 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. of Full Site Editing.

Release Schedule

The schedule from today, 12 August 2020, until the WordPress 5.6 release can be found on the 5.6 development cycle page.  In summary, some key milestones for the release are:

  • Kickoff: 19 August 2020
  • Beta 1: 20 October 2020 (~9 weeks from kickoff)
  • 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: 17 November 2020 (4 weeks from Beta 1)
  • General Release: 8 December 2020 (3 weeks from Release Candidate 1)

If you want to dive deeper into 5.6, development is discussed at a weekly meeting 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 and occurs next at Wednesday at 20:00 UTC. Wish us luck!

This post was compiled with the help of @jeffpaul and reviewed for clarity and accuracy by @cbringmann.  Props to @cbringmann, @angelasjin, @francina, and @desrosj for helping assemble this fantastic release squad and to @chanthaboune for the inspiration to lead the project in this direction!

#5-6

2020 WordPress Release Squads

Update, June 6 – Changed to include the newest member of the release squad, Mary Baum, on Marketing. -Josepha

Excellent progress has been made on WordPress 5.5 so far, and I’m here to do some updates! One of the big things missing from that post was some clarity around who was joining the release squad to help make sure this is a success. This post has the names we know, and I’m happy to take corrections or suggestions as well. 🙂

  • Release leadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg @matt
  • Release coordinator: Jake Spurlock @whyisjake
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM: David Baumwald @davidbaumwald
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech: Sergey Biryukov @sergeybiryukov
  • Editor Tech: Ella van Durpe @ellatrix
  • Editor Design: Michael Arestad @michael-arestad
  • Media Tech: Andrew Ozz @azaozz
  • 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) Tech: JB Audras @audrasjb
  • Docs coordinator: Justin Ahinon @justinahinon
  • Marketing/Release Comms: TBD @marybaum

Joining simultaneously is the WordPress 5.6 release squad! I’ve tagged all of them here, but have left out role assignments. If they make it part way through the ride along process of WP5.5 and decide it’s not what they signed up for after all, then they can step back and someone else can join. 🙂 The WP5.6 release squad will be announced in a roundup/kickoff post of their own.

@afshanadiya @alliennimmons @amandahdm @amykamala @anchenlr @angelasjin @anyssa @annezazu @aurooba @Azhiyadev @bethannon1 @bethsoderberg @breannmcdede @cguntur @chanthaboune @daydah @elmastudio @eringoblog @estelaris @francina @helen @hellofromTonya @isabel_brison @jainnidhi @katiejrichards @laurora @luminuu @m_butcher @marybaum @mbguery @meaganhanes @meher @mekalekahi @melchoyce @metalandcoffee @michelleames @monikarao @newyorkerlaura @planningwrite @poena @rebasaurus @sarahricker @shital-patel @sncoker @thelmachido @thewebprincess @tray @trisha_cornelius @whitneyyadrich @yvettesonneveld

#5-5 #5-6 #planning

Devchat meeting summary – April 22, 2020

The chat was led by @davidbaumwald based on this agenda.

The full meeting transcript is available on Slack.

Highlighted blogblog (versus network, site) posts

@davidbaumwald shared some posts from the Make CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog.

5.4 Retrospective – Call for feedback: the deadline is April 30 and everyone is welcome to leave a feedback.

Proposal: Core Team Rep Elections: the deadline for nominations and self-nominations is May 4.

We’re applying to Season of Docs: a new working group that needs help!

WordPress 5.5: Call for Tickets: the deadline is April 30.

Upcoming Releases

WordPress 5.4.1 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 was supposed to be released yesterday Wednesday, but there were some miscommunication between Core team and 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/ team. The RC has then been pushed back to this Friday. The Gutenberg changes that are going to be included in the release are listed in this pull request. The milestone for this point release is also cleared.

@davidbaumwald reminded that for 5.5, all the maintainers have been pinged about potential features and focuses.  If you’re a component maintainer and haven’t replied yet, please do, so scope and schedule can be proposed.

He also said that work for 5.6 release, aka all-women release, continues. All the women that expressed interest have been contacted. @chanthaboune, @angelasjin, @cbringmann and @francina will work on phase 2: identifying missing roles and cohorts to organize the team that will ride along with 5.5.

Components Check-in

@francina has pinged #meta team about having a weekly scheduled post to check Components status; @dd32 expressed some concerns about the noise that it will create. @davidbaumwald suggested to move on with this for a three-month test.

@audrasjb gave an update about plugins and themes auto-update feature. The team released version 0.6.0 of the Feature Plugin yesterday Wednesday.

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. contains all the identified must-have features and the UIUI User interface was reviewed by several teams. The team is now about to write the Core merge proposal post on Make/Core. More infos here.

Open Floor

@apedog asked a question about routing in WordPress Core. He stated that the WP class having $_SERVER hard-coded into it. And this would require re-writing the methods inside WP class, but without changing its functionality.

@clorith said that he’s generally against the bot idea for a general channel with lots of chatter, and the loss of potential input to backscroll. If it’s going to happen, it should be on Make/* somewhere for consistency and visibility.

@audrasjb pointed out to #16557, a long standing ticketticket Created for both bug reports and feature development on the bug tracker. raised by some people in the French WordPress community. It appears it would be a great SEO enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. to provide proper filters on redirect_guess_404_permalink() function.

He milestoned the ticket to 5.5.0 and refreshed the existing 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. against 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. after testing it. This still needs some unit tests, but before writing them, it would be nice to get a quick review on the current proposal.

@netpassprodsr called for review on #49832.

#5-4-1, #5-5, #5-6, #summary

Dev Chat Agenda for April 22, 2020

Here is the agenda for the weekly meeting happening later today: Wednesday, April 22, 2020, at 20:00 UTC.

Announcements

If anyone has any announcement to make, now is the time!

Upcoming Releases

  • Work has started on WordPress 5.4.1 lead by @whyisjake
  • All the maintainers have been pinged about 5.5. Some replied, some didn’t – please do, so scope and schedule can be proposed.
  • Work for 5.6, aka all-women release, continues. All the women that expressed interest have been contacted. @chanthaboune, @angelasjin, @cbringmann and I will work on phase 2: identifying missing roles and cohorts to organise the team that will ride along with 5.5

Highlighted blogblog (versus network, site) posts

Components Check-in

I have pinged 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. about having a weekly scheduled post to check Components status – @dd32 expressed some concerns about the noise that it will create. I would still suggest to move on with this for a three-month test.

But in the meantime… the usual:

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration

Open Floor

Got something to propose for the agenda, or a specific item relevant to our standard list above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you, accordingly.

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

#5-4-1, #5-5, #5-6, #agenda, #dev-chat

Dev Chat summary – March 25, 2020

@francina facilitated the chat on this agenda.

Full meeting transcript on Slack

This devchat marked week 11 of the 5.4 release cycle.

Announcements

WordPress 5.4 Release Candidate 4 was released on Tuesday March 24, 2020 and everything went smoothly.

@audrasjb shared an update on WP Auto-updates Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.: it was moved from his personal 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/ account to WordPress/wp-autoupdates which is the new official GitHub repository of this project. The #core-auto-updates team will try to ship version 0.4 before WP 5.4 is released. This new version aims to handle auto-updates for themes.

@afragen asked for a review of some Trac tickets which are all associated with Theme compatibility checks and will likely have interaction with the auto-updates feature. The idea is to ship them early in WordPress 5.5.

@whyisjake pointed out that he really like the work that is going on in #core-auto-updates 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 and think that trying to land in the next few releases would be excellent. Related, He’d love to see #core-passwords (two-factors authentification – 2FA) land in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. too. In his opinion, the 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 is so mature at this point that having it left out almost seems like an omission. @whyisjake is going to work on a merge proposal.

@clorith raised that it would be necessary to make sure that the 2FA proposal also highlights the concerns with how to address users locking them selves out (which was the major holdback previously).

@azaozz announced that the patch for image lazy-loading attribute is ready for testing.

Upcoming Releases

The current major is 5.4, scheduled to go out on March 31st 2020; please keep testing for all the bugs!

There are two ways do it:

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. has been branched to 5.5 on the beginning of March. That means 5.5 is officially in Alpha.

@francina announced that work for 5.6 –which is going to be an all-women release– has kicked off with an initial round of messages going out to the women that expressed interest. @angelasjin @francina and Chloé Bringmann are contacting them to hear if they are still interested, what skills they have and what expectations.

Components Check-in

@francina shared a proposal to change the Components Check-in. This is always done towards the end of the chat and feels rushed. There is never really time to dig into the topics they might bring up. Francesca shared two ideas:

  1. Schedule a weekly post where they can leave their status update, like the one for Community deputies.
  2. Adopt a Slack Bot that once a week will ask the maintainers for a status update: maybe in a new component-maintainers Slack channel. Core is getting very busy with TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and Travis bots, and RSS.

@johnbillion added that trying a weekly post could be a good idea. Maybe every Tuesday so it’s ready for the dev chat on Wednesdays in case anything comes up.

@francina proposed to talk to #meta to set this up and test drive it for 8 weeks.

Open floor

@isabel_brison proposed to create a set of guidelines for Internet Explorer support. The CSSCSS Cascading Style Sheets. team kind of decided on starting to deprecate it, and “graceful degradation” seems a good way to go forward, meaning Core can use unsupported technology to make non-essential enhancements. Isabel wants to agree on what’s “essential” here, and created a Trac ticketticket Created for both bug reports and feature development on the bug tracker. to start the discussion: #49696

@paaljoachim suggested to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) default full screen mode to 5.5 as there is a pull request on Gutenberg project GitHub repository to provide an alternative approach.

@audrasjb pointed out that the proposal in this pull request would be a way better than the current implementation.

@whyisjake added that this is not a realistic change for WP 5.4, it’s a proof of concept, and not a fully tested feature.

@francina confirmed that @matt took the decision to ship WordPress 5.4 with this feature. Matt also commented in the Accessibility Team statement post.

@joyously stated it’s hard to contribute when concerns are ignored. @chanthaboune answered she can understand how they can feel ignored. A lot of that research gets done solo, and it’s often hard to remember to recap your own research. For full site editing to be a reality by the end of the year, the work can start bringing incremental changes. This change is feeling very jarring, but there is more worry about not have any mid-point between here and Full Site Editing.

@peterwilsoncc, @clorith and @audrasjb agreed that since RC4 was released, it’s not realistic to revert this change. The discussion can continue in a post-mortem post on Make/Core.

#5-4, #5-5, #5-6, #dev-chat, #feature-autoupdates, #feature-lazyloading, #two-factor