Dev Chat Agenda, June 15, 2022

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

In this post you will find the agenda for the weekly WordPress Developers Chat at June 15, 2022, at 20:00 UTC. All welcome to join the chat in the #Core channel of the Make 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/..

1. Welcome

Dev Chat summary, June 8, 2022

2. Announcements

3. Blogblog (versus network, site) posts

What’s new in Gutenberg 13.4 (June 10, 2022 post)

A Week in Core – June 13, 2022

Discussion: on disallow assignments in conditions and remove the Yoda condition requirement for PHP. This continues the discussion on the WordPress Coding Standards (WPCS) repo.

4. Upcoming releases

a) WordPress 6.0 ‘Arturo’ Retrospective – the form is open until June 19, 2022

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

Early bug scrub schedule for 6.1

c) Next 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.: 6.0.1

6.0.1 Editor Tasks board

5. Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org.

The first of a number of sprints to help update the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Contributor Handbook will take place on Monday June 20, 2022, 20:00 UTC. All welcome.

A sprint will take place in July in APAC time, more dates to follow.

If you would like to assist with this or have a page of the handbook that you would like to focus on, please contact @marybaum and @webcommsat who are pulling together items for the sprints.

6. Open Floor

If you have any items for Open Floor, please add them in the comments below.

If you are a component maintainer and wish to raise a ticketticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.

a) Component maintainers – any issues?

b) Tickets to raise?

c) Any other items?

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

malthert 6:52 am on June 15, 2022

Hey

I’d like to discuss a few tickets to get feedback and get them merged/a PR added:
https://core.trac.wordpress.org/ticket/55605
https://core.trac.wordpress.org/ticket/54669
https://core.trac.wordpress.org/ticket/54233
https://core.trac.wordpress.org/ticket/53125
https://core.trac.wordpress.org/ticket/51585
https://core.trac.wordpress.org/ticket/51340
Héctor Prieto 5:54 pm on June 15, 2022
Hi! I’d like to add a few topics to the agenda:
- The 6.0 retrospective will close this Sunday, 19th June. Please submit your feedback by then!
- Once the retrospective is closed and the results published, I’d like to second @jeffpaul‘s suggestion of starting to collect volunteers for the 6.1 squad and, similarly, I would like to make a call for volunteers for 6.0.x minor releases.
- Regarding 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. squads, what do core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. think of increasing its size to allow folks to shadow the process, in an effort to spread the knowledge around it? As @hellofromtonya pointed out in Slack, the current way minor release squads work is documented here.
Jessica Lyschik 6:32 pm on June 15, 2022

I’ve opened this issue today about older default themes and Google Fonts: https://core.trac.wordpress.org/ticket/55985
Would be helpful if this can get some attention and if possible answer the question if it can be one single pull request or one pull request per theme is preferred.
Jonathan Desrosiers 7:53 pm on June 15, 2022

I was asked to share a summary of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team happenings at 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. Europe contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., but I cannot make today’s meeting. So wanted to provide it ahead of time!

At WCEU, the Core tables were initially focused on helping contributors set up their local development environments. To my knowledge, every contributor for the Core team that showed up wanting to learn how to contribute was able to successfully get a local environment up and running and found a component or focus area they were interested in.

Contributors worked on testing and creating 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. reports, writing unit tests, testing patches, and more throughout the day.

Comments are closed.