Tag Archives: summary

thelmachido a11n 5:18 pm on September 24, 2020
Tags: , , , , 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

Laura Nelson 12:39 pm on September 17, 2020
Tags: , , , summary,   

Dev Chat Summary: September 16 2020

Greetings! 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 16, 2020, 05:00 UTC and Wednesday, September 16, 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/15/dev-chat-agenda-september-16th-2020/ 

Announcements

@pbiron shared that there will be an Upgrade/Install component 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 today (September 17) at 18:00 UTC. Everyone is welcome to attend! More info can be found here: https://make.wordpress.org/core/2020/09/16/upgrade-install-component-bug-scrub-for-wordpress-5-6 

@flixos90 would like more thoughts and feedback on a proposal to enhance image preview: https://make.wordpress.org/core/2020/09/15/enhancing-image-preview-core-proposal/. Please leave your comments on the post.

Due to the speed WP5.6 is moving at, and some unexpected items (oEmbed & PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.0), @chanthaboune has organized a meeting with the 5.6 release squad to discuss. This will take place today (September 17) at 20:00 UTC. @helen proposed streaming the meeting and the squad is still deciding whether to do this. In any case, notes will be taken and published.

Highlighted Posts

A bug scrub was held before the 20:00 UTC dev chat: https://make.wordpress.org/core/2020/09/15/i18n-component-bug-scrub-for-wordpress-5-6/. @helen explained that updates were left on tickets reviewed from the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. reports, and @justinahinon added that progress has been made on all 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. 5.6 slated tickets.

Updates from Component Maintainers/Focus Leads

Upgrade/Install
Will explore adding some UIUI User interface elements to manage email notifications on 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 theme auto-updates.
@audrasjb highlighted the bug scrub taking place today (September 17) at 18:00 UTC.

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

Comments
@imath requested a second opinion on ticketticket Created for both bug reports and feature development on the bug tracker. #50521, and also shared that he’s been working with @dshanske on writing a kick-off post to launch a project to develop the WP Comment Types feature from a plugin. They would like guidance on how to make this post public on make.wordpress.org/core.

Site Health
@clorith shared that they’re doing some 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 work for this cycle and besides that general bug watching.

(Classic) Menus and Widgets
@audrasjb reviewed some tickets with a 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 put a few of them into milestone 5.6.

Build/Test Tools
@johnbillion noted the continued progress on PHP 8 compatibility.

Design
@karmatosed shared “A little note if any components/focuses want design help this release just pop a keyword on or hop into #design. There’s an awesome group of people ready to help this release so great to catch all those little tickets and things.”

Open Floor

@bduclos asked if there are any mockups of the new Twenty Twenty One theme available, and will the project be 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/. @melchoyce will be sharing more details about this in a post, due to be published soon.

There was a lot of discussion regarding the announcement from Facebook & Instagram that they’ll be dropping unauthenticated oEmbed support; mainly around timing and how to communicate this update to WordPress users.
It was noted that the removal of those blocks in v9.0 of 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/ is complete – if need be it can be reverted.
@whyisjake volunteered to put a post together so that the conversation could be continued.

There was an update in response to privacy/data deletion request in issue #43437. It is not anticipated that there will much of a change to the current tools. Concluding with it is not foreseen that there will be any significant breaking type changes for the ticket.

A proposal was put forward to create a #sustainability 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 for those interested in improving the sustainability of WP, through performance enhancements and more. @isabel_brison is putting together a blogblog (versus network, site) post to discuss further. @webcommsat shared this post: https://make.wordpress.org/marketing/2020/06/01/sustainability-working-group-update/ which details some of the work that has been done in this area so far.

@webcommsat highlighted that a week celebrating WordPress translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. will take place from 28 September to 4 October 2020. If you have any ideas on how the translation process for WordPress releases could be promoted, please leave comments on this post: https://make.wordpress.org/polyglots/2020/09/09/lets-celebrate-international-translation-day-together/.

Next Dev Chat meetings

The next meetings will take place on Wednesday, September 23, 2020, 05:00 UTC and Wednesday, September 23, 2020, 20:00 UTC in the #core Slack 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, #summary

thelmachido a11n 7:17 pm on September 10, 2020
Tags: , , , , 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

thelmachido a11n 7:02 pm on September 2, 2020
Tags: , , , , , summary   

Dev Chat Summary: (5.6 Week 3)

This post summarizes this week’s meetings happening on Wednesday, September 2, 2020, 07:00 AM GMT+2 and Wednesday, September 2, 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

@thewebprincess facilitated the meeting and took notes.

2000 core devchat

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

Both groups followed the pre-prepared agenda and started the chat by acknowledging the adjustment to the new timing of the chat having moved it a day earlier.

Announcements

The group was excited about the release of version 5.5.1. @audrasjb thanked everyone who contributed to the release, specifically @winstina and @hauwaabashiya who hosted their first release parties.

Highlighted blogblog (versus network, site) posts

  • The discussion then turned to how best to accommodate Daylight Savings time changes – whether to shift the meeting or keep it at the UTC times which means time changes for participants.
    “ … how do we adjust for daylight savings?” see  @thewebprincess post. In recent years, the switch was made after all countries shifted to DST. What’s being proposed is that we switch that in favour of consistency with UTC. There’s a loosely described process on the matter in the handbook Daylight Saving Time (DST), however, given the more diverse geography attending dev chat, it may be time to reassess the process.
    We need to decide and document it in time for the first change due to take place on September 27 when NZ adjusts their clocks. The group agreed that the decision will be made next week in the meantime if you have something to add to help inform that decision, please leave comments on the post.

Then in the open time, two issues were discussed.

  • Then this issue https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/ was raised by @markparnell, asking the question ” what’s the feeling about this given the volume of jQuery issues after 5.5? are we ready to take the next step, or should we take things a little more slowly?” After some discussion, the conclusion was made that it’s too early yet for a decision and that timing of that point would be best before 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. release (@pwcc) so the group will revisit in a couple of weeks. View slack archive.
    Afterwards, @timothyblynjacobs made a comment on the ticketticket Created for both bug reports and feature development on the bug tracker. “If we upgrade to jQuery 3.0 do we anticipate using any jQuery 3.0 features? Or if WordPress Core won’t be reliant on jQuery Migrate, … follow the conversation on Update jQuery step two ticket.
  • Awareness was raised on  Writing Developer Notes handbook for all contributors interested in writing dev-notes for future releases. Also, view the handbook on Leading Bug Scrubs that was based off a post during version 4.7 it was published recently.

Component maintainers

There is nothing of note from Build/Test Tools this week, but if anyone is interested in helping out with adding end to end / functional tests to the core then check out the post from a couple of weeks ago by @francina.

The Site Health team is assessing focuses for version 5.6 in their meeting next week.

@whyisjake – “While the release team is wrapping up the 5.5 processes, they want to reach out to the wider community for perspectives on the process and what could be done in the future to make releases smoother for everyone. Comments can be publicly shared directly on the post that is to come later, or as part of this form. All responses will be catalogued and then shared.”

Closing Remarks 

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.9 was released yesterday by @jorgefilipecosta! Of note, the new widgets screen was moved out of experimental. There will be more to come in the “What’s New” post for the release. A call for testing will be published 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/ after some design changes are done.

@sergey This is for anyone working on unit tests in core, stricter type checking by using assertSame() should generally be preferred now to assertEquals() where appropriate, to make the tests more reliable. This is helpful in the ongoing work on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 support. See ticket for more details.

Next Dev Chat meetings

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

thelmachido a11n 1:20 am on August 27, 2020
Tags: , , , , summary   

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-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). 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

Dee Teal 5:55 am on August 21, 2020
Tags: , , summary   

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

Laura Nelson 5:34 pm on August 20, 2020
Tags: , , , , 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, #summary

Justin Ahinon 4:53 pm on April 23, 2020
Tags: , , , summary   

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 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). 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