@marybaum graciously offered to help lead Dev Chat next week. While many folks will be at WCEU, there are many others that will not. The meeting shall go on! Thanks Mary!
WordPress 5.2.2 Updates
5.2.2 co-lead @marybaum mentioned that tomorrow the RC2 process will begin and the time was agreed to be 15:00 UTC. The following dates are the updated schedule for releases:
Release 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). 2: Thursday, June 13, 2019, 15:00 UTC
Final Release: Tuesday, June 18, 2019
WordPress 5.3 Updates
@chanthaboune discussed timing for the release saying, “Folks with suggested major focuses have all gotten their best timing estimates to me and it’s shaping up to look pretty good. The focuses seem land-able by late Sept/early Oct, which leaves about a month before WCUS.”
Scope of 5.3 as it relates to the 9 Projects for the Year
@jeffpaul asked “Is the hope that 5.3 includes the final portions of release-related projects from Matt’s list of 9 projects for the year? Asked differently, what remains from that list that we should be aiming to include alongside 5.3?”
@chanthaboune mentioned that the 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. directory is currently awaiting design feedback. Next steps are to be determined and will be mentioned in a 5.3 update post.
@earnjam said the content registration features for themes seems a bit nebulous. In particular:
Porting all existing widgets to blocks.
Upgrading the widgets-editing areas in wp-admin (and super admin)/widgets.php and the Customizer 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. to support blocks.
@aduth provided a very handy link on the current status of these features on the roadmap: https://github.com/WordPress/gutenberg/blob/master/docs/roadmap.md
Jeff asked a follow up question “Is of the remaining projects that are incomplete which (1) are near completion and just need some assistance or (2) are of the upmost priority to try and complete by the end of the year. Knowing the answers to those could help show folks the best places to swarm and help get projects to completion?” @chanthaboune offered to address this and the other roadmap items in a 5.3 update post after WCEU.
@clorith asked “Will this be the final release of the year, and how does that align with our plans to (possibly, depending on how 5.2 rolls along) update minimum requirements to PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 7.x ?” This will also be addressed in the 5.3 update post Josepha offered to tackle after WCEU. @jorbin shared some great stats on the current state of PHP versions finding that “We are under 20% for below 5.6” which is a massive improvement!
Updates from component maintainers
Call for new maintainers of components:
There are a handful of components that are in need of a maintainer to watch over and nurture them:
@azaozz offered to be a maintainer of Script Loader and everyone cheered! Thank you Ozz! Discussion also took place on the collective noun for multiple Ozz, as it would be greatly appreciated to have more of them to help maintain some of the above components. 🙂
Please comment below this post if you are interested in any of the above components, or feel free to reach out to @chanthaboune if you’d rather volunteer privately.
General Announcements and Open Floor
Jonny Harris is working on a feature plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. that gives REST endpoints for menus. This is in preparation for upcoming navigation blocks, but it also serves as an excellent way of exposing menus to headless applications using WordPress. He would like some feedback on the plugin 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 would appreciate thoughts on considering this in the scope of 5.3. Please leave on this PR: https://github.com/WP-API/wp-api-menus-widgets-endpoints/pull/22
@presskopp mentioned a commented made here on the 5.3 call for tickets post. @chanthaboune mentioned that there is agreement and it is wrapped into the triage work from the 9 projects mentioned earlier in notes.
@bph asked, “There is a big knowledge gap that there is actually user documentation available for Gutenberg. Where would a discussion be placed best design/core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor to surface the document within the block editor?” @aduth said that it was mentioned in a recent #core-editor chat and linked some action items from that chat here: https://wordpress.slack.com/archives/C02QB2JS7/p1558532425222200 Andrew proceeded to offer to help in creating a 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/ issues for this. @bph offered to make a post to discuss this further. More to come soon!
These notes were taken by @antpb and proofread by @chanthaboune.
#5-2-2, #5-3, #devchat, #summary