Dev Chat Summary: October 17 (5.0 Week 3)

This post summarizes the dev chat meeting from October 17th (agendaSlack archive).

5.0 planning

  • @chanthaboune shared a granular timeline for 5.0 noting blockers for each team, the Google Sheet in the post is updated regularly as additional information is identified.
  • The 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. team had a bugscrub focused on open issues for Gutenberg tagged Backwards Compatibility. There were some additional requests for help noted:
    • A review from an experienced core dev was requested on
    • Help adding a filter for GB#9089 (as noted in the comments) was requested on
    • A PR was requested for GB#8151 based on the mock-up on the ticketticket Created for both bug reports and feature development on the bug tracker..
    • Also some help on cross-block selection:
  • 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”) team added a weekly bugscrub on Tuesdays occuring at 15:00 UTC in #core-restapi. All are welcome!
  • The Gutenberg team has started a documentation effort for the Gutenberg handbook (which will include information from both phases 1 and 2). @chrisvanpatten is coordinating people for that and is accepting all help!
  • @allancole introduced Twenty Nineteen with current mockups and prototypes which will ship with full Gutenberg support including both front and back-end styles.
    • There will be weekly half-hour meetings every Tuesday at 16:00 UTC in #core-themes development will happen on GitHub. Once the theme is stable, it will be merged into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the 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. repo will be depreciated.
    • @laurelfulford added a request for some additional help to review the old default themes as they get updated.
  • @desrosj shared an update on plans related to PHP 7.3 that will be fully supported with our next release. The post includes a breakdown of the changes in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 7.3 that 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 Plugin Directory or can be cost-based plugin from a third-party and theme developers need to be aware of and should accommodate in their code.
  • We discussed some logistics at this point:
    • The alpha nightly builds of 5.0 are available. These builds will probably be sent to 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. tester plugin.
    • Current plan is to have Gutenberg 4.1 included in WordPress 5.0 beta1, with older versions of Gutenberg disabled.
    • After Beta 1 commits need to be approved by relevant release leads or @pento as detailed in the commit management post.
    • As of this writing, Beta 1 is still expected for Friday, Oct 19. Gutenberg is expected to be feature complete at this time.

Updates from focus leads and component maintainers

  • The Gutenberg team released v4.0 to bring Gutenberg into the 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). stage including the introduction of a new data structure for RichText that will allow building sophisticated interfaces for inline content that we can make portable and relevant to mobile too.
  • The REST API team shared a meeting summary from last week which includes updates on 5.0 priority tickets (in progress, resolved, punted).
  • The Privacy team shared a meeting summary from last week including ticket milestone changes out of 4.9.9, a proposed v2 roadmap, a Gutenberg review, and a cross-platform privacy working group across open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. CMS teams.
  • The PHP team shared a meeting summary with focus on WSOD protection.
  • The 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. team shared a meeting summary which includes handling Gutenberg merge props, internationalization, plugin and 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. scaffolding, and the pending bump of node’s LTS version from 8.x to 10.x.
  • @audrasjb wanted to note that the AccessibilityAccessibility 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). ( team is working to choose team reps this Monday with likely rotation every three months. They’ve also started collaborating on the Twenty Nineteen work.

General announcements

  • No announcements, although Gary did end with a nice thank you to everyone who has contributed so far and those who are helping in our push across the finish line.

Next meeting

The next meeting will take place on Wednesday, October 24, 2018, 3:00 PM CDT in the #core SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at 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.