(Updated June 17, with Core handbook update sprints dates and links, and proposal for weekly Editor Bug Scrubs @webcommsat)
Start of the meeting on Slack.
@marybaum and @webcommsat ran the meeting on this agenda.
Last week’s summary.
1. Welcome
@marybaum welcomed new contributors who had joined and thanked everyone involved in welcoming and supporting new contributors to core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
2. Announcements
It was a quiet week for announcements.
Just before dev chat, the core-editor team released Gutenberg 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/ 13.5 RC1.
3. Blog (versus network, site) posts of note
What’s new in Gutenberg 13.4 (June 10, 2022 post)
A Week in Core – June 13, 2022
Discussion: disallow assignments in conditions and remove the Yoda condition requirement for PHP. The post continues the discussion on the WordPress Coding Standards (WPCS) repo.
@chanthaboune shared a design post of relevance to core – Thinking Through the WordPress Admin Experience from @matveb.
@ndiego would like to start holding weekly editor-focused bug scrubs on June 28.
4. Upcoming releases
@priethor continues to collect your thoughts on the 6.0 release retrospective, through to Sunday, June 19, 2022. If you have feedback, please share before then.
The next major 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. is 6.1
Work on features has been in alpha since the release of the RC1 version of 6.0; when the release squad forms ahead of beta 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., that will be almost the end of the time for anything new.
To that end, two items:
Roadmap to 6.1 from @matveb
And @costdev has a schedule for early bug scrubs for 6.1. Thanks to @costdev, @audrasjb, and @chaion07 for facilitating these scrubs.
The next minor 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. is 6.0.1
6.0.1 Editor tasks board on Github.
5. Contributing to Core
a) Handbook sprints
@webcommsat highlighted the first of a series of Core Handbook sprints that will happen on Monday, June 20, 2022 to update several sections that are in need of update. Please join in! The sprint will be in #Core Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. A number of other live collaboration sprint dates are in the post and there will be opportunities for asynchronous contribution.
Read the Sprint posts and check out the live collaboration dates.
@desrosj shared this report asynchronously:
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 bug 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.
In last week’s meeting, there was an update on some of the cross-team collaboration at WCEU from core with documentation, training/ Learn WordPress teams.
Thinking about core tables at WordCamp 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. US Contributor Day will start soon.
c) The next New Contributor meeting will be Wednesday, June 22, 2022, an hour before dev chat.
6. Open floor
a) Items to highlight from component maintainers
@sergeybiryukov gave an update on I18N 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.: A translatable string is now used for displaying a user’s first name and last name in various places. This allows locales to switch the order of the first name and last name, should they prefer to do so. Ticket #17025 for more details.
b) Bug scrubs – latest links are in the Releases section above.
c) Core or Gutenberg tickets requested to highlight
i) Trac ticket #55985
@luminuu: I’ve opened this issue today about older default themes and Google Fonts.
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.
@luehrsen highlighted the issue as it related to GDPR violation, and that the ticket Created for both bug reports and feature development on the bug tracker. proposed and a proof of concept on GitHub 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/ has been prepared as a potential way forward. Review of these were requested.
More on this ticket discussion during the meeting – Slack link.
Couple of tickets raised by @malthert for some attention.
ii) Trac Ticket 54233
iii) Trac Ticket 53125
This has moved on since posted on the dev chat agenda, thanks @sergey.iv) Trac Ticket 51585
The last request on this was to update some internal docs so that beta/RC 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). releases are tagged the same way that releases are tagged. @malthert is asking for guidelines to do this.
v) Trac Ticket 51340
vi) Trac Ticket 54669
d) @costdev raised a discussion about scope as Core developers. Link to more details in the slack discussion. @marybaum suggested a P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post as the next step.
Props to @marybaum and @webcommsat for preparing and facilitating the meeting, and the dev chat summary.
#dev-chat, #summary
