Editor chat summary: 25 September 2019

This post summarizes the weekly editor chat meeting on Wednesday, 25 September 2019 at 1300 UTC held in Slack.

The agenda can be found here.

News

• WordPress 5.3 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. 1 is out

Weekly Priorities

• Weekly Priorities are the remaining important issues and tasks needed for WordPress 5.3: https://github.com/WordPress/gutenberg/projects/34?fullscreen=true
  • still considering the 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. content areas related work as a priority for the project

Task coordination

Note: If you’re reading this summary outside of the meeting, please drop a comment if you can/want to help with something!

• @andraganescu
  • refactored the MediaFlow component to be a drop in component nstead of a HoC. it looks kind of ready https://github.com/WordPress/gutenberg/pull/16200
  • the PR implementing a smarter block appender could use a new review https://github.com/WordPress/gutenberg/pull/16708
• @youknowriad
  • works on the WP 5.3 board above,
  • also working on dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.,
  • Trying to help fix bugs
  • Reviewing Block Content areas work as time allows.
• @mapk
  • I’m watching the project board like a hawk.
  • Testing @getdave’s responsive spacing PR: https://github.com/WordPress/gutenberg/pull/16790
  • Helping with the Inserter Panel Previews. https://github.com/WordPress/gutenberg/pull/17493
  • Keeping movement on the Block Patterns: https://github.com/WordPress/gutenberg/issues/17335
• @brentswisher
  • will be back to his PRs
• @getdave
  • works on the DimensionControl component and needs feedback https://github.com/WordPress/gutenberg/pull/16791
  • needs feedback on ResponsiveBlockControl too https://github.com/WordPress/gutenberg/pull/16790
• @jorgefilipecosta
  • implements the first version of custom Gradient picker
  • needs review on https://github.com/WordPress/gutenberg/pull/17154
  • also working on compiling WordPress 5.3 Gutenprops. If you have not yet associated your 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/ to your WP.org profile, please do so, to make the props work easier and to make sure props are attributed!
• @mcsf
  • focusing back on improving remote vs. local autosaves

Open floor

• @paaljoachim raised some issues for discussion
  • there was a discussion on an option to use text link instead of auto embed ended with needing to clarify more on the issue
  • there was a discussion on the social block features needed for it to make it in WP 5.3 resulted in not having a light version because of the risk that we’d introduce breaking changes in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
• @desaiuditd and @youknowriad discussed about https://github.com/WordPress/gutenberg/pull/17311

---

The next meeting is on 02 October 2019 at 13:00 UTC.

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