Editor Chat Summary: May 29th

AgendaSlack Transcript


Gutenberg 5.8 was released today, congratulations to everyone who participated in this releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.!

The release agenda for WP 5.2.2 is out https://make.wordpress.org/core/2019/05/28/5-2-2-release-agenda/.

Regarding the WP 5.2.2 release, from the editor side, we have two PRs to be backported. https://github.com/WordPress/gutenberg/pulls?utf8=%E2%9C%93&q=is%3Apr+label%3A%22Backport+to+WP+Core%22+is%3Aclosed+milestone%3A%225.8+%28Gutenberg%29%22+.

@youknowriad volunteered to backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. the PR’s.

Task Coordination

  • @aduth
    • Toyed with a first GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ Actions workflow for the project, to auto-assign merged pull requests to milestones https://github.com/WordPress/gutenberg/pull/15826
    • Explored preferences persistence, which initially seemed there could be a simple option to reuse existing features https://github.com/WordPress/gutenberg/pull/15800.
    • Plans to merge some improvements to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the build faster.
  • @youknowriad wants to work on
    • Exploring grid helpers when resizing images.
    • Exploring more animations (snackbars, moving blocks…).
    • document the release tool.
    • automate npm releases.
  • @nerrad
    • Implemented useSelect hook and it’s powering withSelect.
    • Is working on the useDispatch hook.
  • @gziolo
    • Spent one full working day triaging issues last week
    • https://make.wordpress.org/core/2019/05/27/the-block-registration-api-status-update/ – Is still awaiting feedback for the block.json proposal, hopes to finalize it this week.
    • Is helping @joen with improved UXUX User experience for nested blocks.
    • Wants to start on Bring consistency to 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. toolbar for text blocks .
  • @mapk
    • Is working on a few Table block issues.
    • Is looking at word breaks in the Media_Text block.
    • Will look into custom fields checkbox in the Options menu.
    • Will check spacer block clearing floats.
  • @andraganescu
    • continues to work on the media blocks update flow.
  • @kjellr
    • Still helping support the nested block work from @joen
    • Thinking about providing suggested column layouts: https://github.com/WordPress/gutenberg/issues/15663#issuecomment-496568894
    • Narrowing down the icons for the Group block: https://github.com/WordPress/gutenberg/issues/15602
  • @jorgefilipecosta
    • Past week:
      • Worked on the widgets screen endpoints and frontend rendering of blocks in the widget areas, a summary of the work was posted in https://github.com/WordPress/gutenberg/issues/13204#issuecomment-496934219.
      • Worked on other enhancements e.g.: text color in the heading, link UIUI User interface on the images and some editor bugbug 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. fixes.
    • Next week:
      • Will explore a short term very specific project board to make organizing PR’s and issues easier.
      • Continue the work to solve generic block editor problems affecting the widgets screen and probably external usages of the block editor.
      • Address reviews on the image link UI.
      • Work on some bug fixes and UI enhancements e.g. explore insert by URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org on cover and media text blocks to make them more similar to the other media blocks.
      • Improve the contrast checking to make aware of parent colors (e.g: group block) and solve some bugs.
  • @iseulde
    • Plans to continue with this roadmap: https://github.com/WordPress/gutenberg/issues/13778.
    • Is a bit busy with conferences.

To anyone reading this, it is possible to participate in the task coordination in an async way. Feel free to comment in this post with the tasks that you worked on during the last week and/or what tasks you plan to work on during the next week.

Inline color support

@paaljoachim asked participants in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor chat to discuss his comment https://github.com/WordPress/gutenberg/issues/8171#issuecomment-496304938, that proposes the addition of inline color support.

@youknowriad said:

I think that is something we can consider, it should be tracked in its own issue separately from the block level color support tracked in 8171.

@mapk volunteered to create an issue to track this task.

@iseulde said that this task is on the rich text roadmap, but would be good if there’s a separate issue.

@mapk referred that @phpbits volunteered to implement this feature. Thank you @phpbits!

@youknowriad would like some design and APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. explorations and referred that the following questions should be considered:

  • What inline formatting do we want to support aside colors?
  • Do we want to gather these in a panel/popover?
  • In terms of API, how can we control the availability of these options?

Open Floor

@iseulde proposed a dedicated place (a specific meeting/a channel) to have conversations related to the RichText component.

@youknowriad asked why does it need to be separate from the current meeting? While adding that he not suggesting we don’t do it but was wondering if a section during the core editor meeting could be dedicated to RichText when needed.

@iseulde shared that in her opinion core-editor has become very broad and she thinks it might be good to have something smaller. She is not sure about set meeting times, she thinks that perhaps just a space where people can chat async is enough.

The conversation went on with some people trying to understand the current challenges communication related to RichText faces, and some people showing support to the idea of a RichTextspecific communication medium.

@youknowriad ended the meeting by saying that we should experiment and see what works and asked @iseulde to keep us updated.

#core-editor, #editor-chat, #summary