Editor chat summary: January 9

Gutenberg 4.8

  • Gutenberg 4.8 is released and in WordPress 5.0.3. For the full list of change refer the release post.
  • This release was focused on bug fixes and performance improvements which are included in WordPress 5.0.3.
  • Due to the small gap between 5.0.3 RC and 5.1 beta, Gutenberg 4.8 will be included as is in WordPress 5.1.

Release schedule

  • A new release schedule was proposed:
    • Automatically release a new plugin version every 2 weeks with what’s already available on the master.
    • The remaining PRs in the milestone will automatically be moved to the next release.
    • Build a zip and do a call for testing on Monday, release on Wednesday
    • This will bring more clarity to the schedule and less stress for contributors.
  • There was also a discussion to remove the RC period for the plugin, but no decision reached.

Phase 2 Scope and features

  • There is an issue starting to outline the scope for Phase 2.
  • One of the focus areas for Phase 2 is “widgets 2 blocks“. There are a bunch of PRs that require reviews and may development. Would be great to get some contributions there for those looking to help.
  • An ‘async mode’ has been introduced to batch state updates and improve the performance of the editor with long content. As part of this, there is a structural change to the data module, everyone is encouraged to test for regressions with their custom blocks
  • There is proposed a ‘Generic block editor module’, to build a post agnostic editor. This will make it easier to embed Gutenberg in other places, such as widgets screens.

Open floor

@chrisvanpatten temporarily steps down from Gutenberg docs lead due to personal priorities and @dryanpress will step up instead.

The meeting archive is here.

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

#5-0-3, #meeting-notes, #editor-chat

#docs

Editor Chat Notes: December 19th

These are the notes the weekly editor chat meeting held on Wednesday, 19th December 2018, 14:00 GMT:

  • Next week there will be no meeting to pause for holidays.
  • Volunteers for notes each week were asked for and @pbrocks, @orientedvirus8 and @ajitbohra volunteered.
  • Gutenberg 4.7.1 has been released with small fix for editor.BlockListBlock filter that was causing some BC issues for ACF blocks and other plugins.
  • Update on the Commit and merge status https://make.wordpress.org/core/2018/12/19/gutenberg-commits-and-merge-status-update/
    • Idea to bring some organising to the Gutenberg repo. We have a new branch called g-minor that will contain critical fixes to be back ported to core via package releases.
    • It was raised to consider using gitflow completely and document what the name means.
    • Some discussion rose around name of the branch and using gitflow.
  • 5.0.3 Focus: https://github.com/WordPress/gutenberg/milestone/83
    • This is the main focus now.
    • Uncertain if 5.0.3 will happen soon, dev chat will confirm this, however continue as if happening.
    • Please review, merge and fix those issues.
  • Update on the Widgets to Blocks conversion https://make.wordpress.org/core/2018/12/17/status-update-porting-widgets-to-blocks/
  • @gziolo is playing with e2e tests to include popular plugins: https://github.com/WordPress/gutenberg/pull/12578. Asked for help from anyone that has an idea how to make this easier. Ideally there would be one command which could run against a plugin name/url/zip.
  • @notnownikki has a testing request for: https://github.com/WordPress/gutenberg/pull/12981.
  • @chrisvanpatten gave a docs update
    • Trying to merge PRs quickly this week.
    • Thanks for everyone contributing.
    • Dev docs are improving rapidly.
    • User docs are focused on publishing a draft Google doc by the end of this week. A p2 post on make/docs will outline how anyone can contribute to this.
    • Docs meetings are on a haitus until January 8th but please continue follow in GitHub and on Slack in #docs.

The meeting archive is here.

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

#5-0-3#meeting-notes#core#editor-chat

GDPR Compliance Chat Recap – April 11

(full text on slack)

First deploy of ticket #43481

  • Core ticket #43481 is about tabs and placeholders to privacy tools page in wp-admin and a first version has been committed into dev. Goal is to have it inside the 4.9.6 release.
  • These screens will allow the site admin to get validation from the requester follow-up on requests. Requests could come in from different sources (email, phone request, contact page, etc) so a dedicated place is needed.

Announcements: Available texts and where to publish them

Plugin dev guidelines

Privacy section in readme.txt

  • Besides the functions in Core and the upcoming filters/hooks that plugin authors will be able to use, there might also be a need to have privacy related info in the readme.txt
  • The advantages of a section in the readme.txt would be:
    • availability in plain text in downloads
    • parsable, can be displayed in tab on plugin repo
    • translation, since readme is in Core’s i18n tools on translate.wordpress.org
    • Version control
  • The eventual section in the readme.txt will however not substitute the need of having the privacy information also delivered using filters/hooks as the purpose and possibilities are different.
  • Another idea was to add a ‘Privacy URL’ keyword where a URL could be provided to a privacy statement hosted on a website.

Trac tickets: https://core.trac.wordpress.org/query?status=!closed&keywords=~gdpr
GDPR agenda and recaps: https://make.wordpress.org/core/tag/gdpr-compliance/

#gdpr-compliance #summary