@francina facilitated on this agenda. @sageshilling compiled this summary; @marybaum edited.
Celebration: WordPress turns 17!
@francina asked the group: What’s the next 17 years of WordPress look like? And then commented, “Futuristic I hope, maybe some steampunk.”
Which led to this barrage from the group:
- Radio buttons everywhere.
- Blink tags, it’s all about attention grabbers.
- Even more admin (and super admin) messages.
- More animated gifs? I’m going to have nightmares. (edited)
And this commentary:
- Well that’s me not sleeping tonight.
- No dancing baby unless it’s Leo [son of a Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committer 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.]
@francina got the meeting underway by pointing out two Highlighted/Need Feedback Blog (versus network, site) Posts:
As often happens on a Wednesday, just before devchat, the Editor team issued a 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.. This week: 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/ 8.2.0 featured block 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. patterns and significant speed boosts, plus a long list of other enhancements.
To quote @francinadirectly: “Really, kudos, Gutenteam!”
Through the rest of today, May 28, 2020. @jeffpaul has been shepherding this process and will announce the new reps.
@whyisjake will lead 5.4.2 and confirmed he’s planning on this 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. in two weeks.
Last week the group agreed on releasing a public 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. June 3 and the full release June 10th.
@whyisjake added that there is one ticket Created for both bug reports and feature development on the bug tracker. left in the milestone, and it has security implications. In the interest of making the web safer, the folx working on that ticket are thinking of backporting it to version 5.1 – which would be an exception to the project’s current policy
@audrasjb gave his Accessibility 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) update: two of three 2020 projects will make it into 5.5. The first of those, Alternate Table Views Choices, will likely be ready to discuss next week.
@garrett-eclipse brought a proposed UI User interface change from Meta 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., that would add a dev-note field in Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:
Also from Meta, the act of adding a PR to a ticket will toggle some keywords: has-patch 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./needs-patch/needs-refresh and needs-unit-tests/has-unit-tests.(meta:#5080)
Garrett thanked @dd32 for working on this, and @desrosj told the group it’s on his priority list for the next several days.
@johnstonphilip asked the group to discuss ticket #50214: Consider introducing the concept of “Editors”, and several people immediately got going in a lively thread.
@desrosj proposed a new enhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. in this ticket: #50268: Improve the plugin/theme auto-update emails
@Howdy_McGee asked for some eyes on his patch of #50070: ‘post_type’ query variable not set for taxonomy queries
Per his comment on the agenda, @apedog asked the group about avenues to overturn decisions that have already been made.
@justinahinon asked about next steps on APAC-friendly meetings, per https://make.wordpress.org/core/2020/04/29/proposals-an-apac-dev-chat-town-hall-meetings/
@carike also reminded us that Sitemaps is scheduled to be merged into 5.5.