Editor chat summary: January 23

This post summarizes the latest weekly Editor meeting, held in the #core-editor 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/. channel, on Wednesday, January 23, 2019, 14:00 UTC. These meetings coordinate collaboration in the development evolution of 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. https://wordpress.org/gutenberg/ project.

Releases: Gutenberg 4.9

  • Gutenberg 4.9, a large milestone, has now been released.

Support Requests Change:

  • Proposed change to the wording in 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. https://github.com/ issue template designed to align the Gutenberg support with the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. support.
  • Opinions offered about what to do with open support calls.
    • Concern over appropriateness of Slack for support.
    • @gziolo Slack not ideal since it is not archived nor crawlable by Google.
    • @clorith Slack not ideal because of its lack of moderation tools
    • @Matt Bolt expressed dismay about losing Slack as a resource for developer support.
    • @nerrad suggested StackExchange.
    • A GitHub App built with Probot was suggested.
    • @sheri advised incorporating thoughts from #support weekly team meeting -and added to their agenda.
  • @clorith raised concerns with bulk closing open support requests.

Tasks Coordination

Following last week’s meeting, participants have been asked to provide any updates:

  • @ajitbohra – started testing PR’s and trying to review a few. Also selected Latest Post 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. for iteration. A suggestion was made that Latest Post Block could be divided up into smaller tasks.
  • @sheri – hoping to continue with the work this week.
  • RSS Block, Video Subtitles and Alternative File blocks are all progressing.
  • No progress on server-side rendering – @gziolo hopes to start work on this later in the week.
  • @jorgefilipecosta has started work on a legacy widget block.
  • Over the next week, the following work is planned:
    • Circle back to ServerSideRendering @aduth @gziolo.
    • Finish the first iteration of the RSS block @soean (needs a second review).
    • Improvements to the video block @soean.
    • Continue the work on the classic widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. block @jorgefilipecosta.
    • Removing useless PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher code (post 5.0 merge) @aduth .
    • More widgets 2 blocks reviews @gziolo.
    • Latest posts block iterations @ajitbohra.

Pull Requests & Issues

Open floor

  • @youknowriad raised the issue that we have more open pull requests than reviewers, the two issues to resolve are:
    • How to get more reviewers for PRs
    • How to split approvers responsibilities across an area of expertise?
  • Some easy solutions tabled by @aduth are to assign code owners to the various parts of the repo using Github’s functionality. Create educational resources to assist with reviews.
  • People are asked to identify themselves if they wish to be added as a code owner for a particular area they are interested in – an issue is to be set up to track this.
  • @youknowriad has proposed the following for the coming week:
    • Create an issue where we identify the different areas of expertise.
    • Use the code owners feature for the “approvers/owners/committers”.
    • Use Github teams for the reviewers per area.

The meeting archive is here.

The agenda for the next meeting is here, please add anything you want to discuss.

#meeting-notes, #core-editor, #editor, #gutenberg