Felix Arntz 7:46 pm on March 3, 2018
Tags: core-php ( 32 ), PHP ( 26 ), servehappy ( 9 ), summary ( 154 )

PHP Meeting Recap – February 26th

This recap is a summary of our previous PHP meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

You can find this meeting’s chat log here.

Chat Summary

The agenda for the meeting was to discuss the API endpoint for which a first version was introduced the previous week.
It was ensured that the endpoint parses PHP versions correctly and allows for flexibility by parsing out the actual version number from strings which may contain additional environment-specific information.
Some concerns regarding the structure of the response were expressed, particularly related to redundancy, future maintainability and inconsistencies.
By the end of the meeting, it was agreed to go with the following response structure:
- recommended_version – string – The PHP version recommended by WordPress
- is_supported – boolean – Whether the PHP version is actively supported
- is_secure – boolean – Whether the PHP version receives security updates
- is_acceptable – boolean – Whether the PHP version is still acceptable for WordPress
It was also decided to remove all IP address-related functionality, as it is unlikely that those will be needed in the future. Detecting hosts by IP address and maintaining host-specific data via the API would be a huge maintenance burden, and additionally passing the IP address would overcomplicate the current efforts by having to deal with possible privacy concerns.

Call for Testing

Since the meeting, the API endpoint has been updated to use the aforementioned response data structure, and an updated patch for the PHP nag in core, implemented as a dashboard widget like previously decided, is ready to be applied.

Please thoroughly test the API endpoint and patch. The API is already live, and the current plan for the patch is to commit it to core next week.

The API endpoint is available at https://api.wordpress.org/core/serve-happy/1.0/, and it requires a php_version query parameter to be passed.
The patch for the core nag is available at https://core.trac.wordpress.org/attachment/ticket/41191/41191.6.diff, making use of the API endpoint. When applied and your installation is not on PHP 5.2, you can “simulate” the behavior by going into the src/wp-admin/includes/dashboard.php file, looking for the wp_check_php_version() function and temporarily hard-coding ‘5.2’ in there instead of the actual PHP version. For the related ticket, see #41191.

Next week’s meeting

Next meeting will take place on Monday, March 5, 2018 at 16:00 UTC in #core-php.
Agenda: Discuss the patch for the core nag.
If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#core-php, #php, #servehappy, #summary

Matias Ventura 7:02 pm on March 2, 2018

What’s new in Gutenberg? 2nd March

This release includes significant progress in consolidating the codebase and refining aspects of the experience. Notably, it introduces APIs for extending Gutenberg beyond blocks, allowing plugins to register a full sidebar for their functionality. There are also expansions to the template support (now allows to declare nested structures), ability to duplicate blocks, various design adjustments, etc. Overall the tone has been fine tuning existing elements and simplifying implementations.

2.3 🍇

Continue editing flow iterations by adding a line between blocks to insert new content — it also works within nested groups.
Add support for nested templates.
Allow duplicating a block through a menu button.
Automatically set a matching block as the default when a post format is set and the post is empty. This continues the path of matching blocks with post formats.
Add CodeMirror (core library) to the HTML block for syntax highlighting.
Simplify design presentation of editor header area for better consistency. (Add label for "Preview" action.)
Introduce new API for allowing plugins to register sidebars. ⭐️ It allows plugins to further extend Gutenberg natively with non-content functionality. Note: the public facing functions are marked as experimental as they are being iterated in the context of the major extensibility work going on outside of blocks.

HTML block, now with syntax highlighting.

Other Changes

Improve the "invalid block" dialog by reducing the options and adding a new convert to blocks feature as we have solidified the transformations.
Allow adding images to a gallery without going through the media library.
Show the block appender even if the last block is non empty paragraph.
Show the side inserter on empty paragraphs within nested blocks.
Add a script that creates a PHP file based on a POT to make the plugin translatable.
Refactor float alignment to avoid margin calculations and simplify rendering.
Support registering and invoking actions in the data module.
Add hook to validate useOnce blocks.
Add viewport module. (Showing explorations with data module.)
Provide a fix for apiRequest in sites configured to use plain permalinks. (Reported several times!)
Remove specific grammar support for more tag as we consolidate the syntax and reduce weight.
Move filter for registering block types before validation happens.
Allow removing the selected image in a gallery block using backspace/delete keys.
Make saved blocks preview available to keyboard users.
Refactor reducer enhancers as higher-order reducer creators.
Refactor query HOC usage with withSelect.
Refactor API calls in Gutenberg to always use wp.apiRequest.
Register core blocks on init hook.
Removed DefaultBlockAppender when a template Lock exits.
Reduce and simplify float code.
Refactor and cleanup for the Ellipsis and More Menu components.
Add focus styles for Windows High Contrast mode.
Move meta boxes out of the generic editor module.
Make the "more" tag visible in the Classic block.
Expose ImagePlaceholder component in wp.blocks.
Rename TermTreeSelect to TreeSelect and move it to components.
Reuse isHorizontalEdge for RichText component and remove duplication.
Improve CSS for gallery caption and avoid UI shifts.
Use TreeSelect in HierarchicalTermSelector.
Flatten components modes directory organization.
Mutate editor store reference in middlewares application.
Consider term names as case insensitive.
Resolve an issue where removing a block which had contained inner blocks would not clear those inner blocks from state.
Make sure block usage is incremented (for calculating frequency and recency) when adding blocks with the side inserter.
Hide non editor specific notices, pending further improvements.
Update shortcode block icon.
Disable post format input if the theme does not support post formats.
Remove margin from initial insertion point and fix misalignment.
Polish header for mobile and accommodate other more languages.
Improve handling of block toolbar on mobile.
Show taxonomies in the document inspector separately, uncoupling Categories & Tags.
Fix issue with gallery images not cropping within link wrappers.
Fix bug in paragraph blocks affecting input behaviour when block is positioned on left or right.
Fix minor inconsistency with block margins and the default appender.
Fix description typo in freeform block.
Fix issue with focus transfering between citation and content.
Fix issue with floated block toolbar on adjacent floats.
Fix duplicate upload of media on drag.
Fix issue that prevented adding new rows or columns in Table block.
Fix issues with z-index and the sidebar.
Fix accessibility issues with mover icons.
Fix issue with default block replace resulting in incorrect order.
Fix sidebar tab padding.
Fix certain conflicts with markdown plugins.
Fix IconButton indent regression.
Fix issue with self embedding WP posts and the processing of the embed markup.
Fix extraction of _nx translation function.
Fix wp.data.query backwards compatibility with props.
Fix problem with delete key in empty contentEditables.
Resolve an issue with the data module's unsubscribe behavior which can result in a listener callback being invoked even after its been unsubscribed.
Remove the api-request JavaScript shim which had existed while WordPress 4.9 was in pre-release.
Remove explicit handling of "bottom reached" within writing flow as redundant.
Remove invalid reference to WeakMap polyfill.
Remove unused wpautop fixture files.
Remove non-functional custom taxonomies meta boxes.
Remove is- prefix from embed alignment class.
Switch get_locale() to get_user_locale().
Remove unnecessary $current_screen code.
Reduce duplication in 'No saved blocks' and 'No blocks found' component messages.
Include string extraction in production build.
Add deprecation helper functions for consistent messaging.
Improve string cast render test.
Add Gutenberg svg to docs.
Add documentation describing block transforms.
Add documentation for nested template definitions.
Add documentation for registering sidebar APIs. Move them to extensibility docs.
Update WordPress packages to the latest versions.

Jeffrey Paul 10:00 pm on March 1, 2018
Tags: 4.9.5 ( 8 ), authentication ( 3 ), contributor day ( 3 ), core ( 65 ), core-php ( 32 ), core-restapi ( 26 ), dev chat ( 218 ), gdpr-compliance ( 9 ), summary ( 154 ), two-factor ( 8 )

Dev Chat Summary: February 28th (4.9.5 week 4)

This post summarizes the dev chat meeting from February 28th (agenda, Slack archive).

4.9.5 planning

@danieltj and @audrasjb to work as co-leads with @sergey to work as deputy
@danieltj and @audrasjb to run bug scrub meetings on Tuesdays from 20:00 to 21:00 UTC
If you have interest and availability to help run additional bug scrubs, then please reach out to @danieltj @audrasjb @sergey or @jeffpaul
4.9.5 schedule to be communicated in next week’s devchat meeting

Updates from focus leads and component maintainers

The REST API team is still having difficulty with a meeting time that works for all parties. Join them in #core-restapi if you’re interested in discussing a time that works for US/EMEA and another that overlaps better with APAC.
The PHP team posted notes from their meeting last week and meet again Monday at 16:00 UTC in #core-php.
The GDPR Compliance team posted notes from their meeting last week and you can continue to follow along in #gdpr-compliance.
@obenland cross-posted from Make/Meta about Two Factor Authentication on WP.org and you can continue to follow along in Meta#77.

WCEU Contributor Day

@flixos90 looking for volunteers for the core team to lead WordCamp Europe contributor day.
@getsource will be there, but helping with Hosting Community
@kadamwhite will be there, but his experience from WCUS shows it may be better for REST API folks to embed with another team and support their efforts (e.g., the Editor team)
@antpb willing to talk on setting up a local for Gutenberg and Core development
@sergey will be there helping with Meta team, but open to helping with Core during afternoon
Also, please keep your eyes out on tickets that would be good to be tackled at WCEU contributor day
If you’re attending WCEU and interested in leading the core team or targeted sub-teams (JavaScript, REST API, etc.), then please reach out to @flixos90.

General announcements

Progress on implementing a way to catch the issue from the 4.9.3 release is being tracked in #43395
@mte90 looking for review on eight tickets:
- #40810: patch has been refreshed including unit tests, needs review
- #34706: needs review on whether work is required or not as the desired enhancement may already exist; @danieltj to take a look
- #14148: needs review to see if a refresh is needed, otherwise needs testing
- #17025: needs review before another likely refresh
- #28112: needs review and docs; @audrasjb to test the patch
- #36661: needs review
- #15145: needs review
- #17019: needs testing
@helgatheviking looking for review on #18584, but likely wait on this for now until Gutenberg lands as nav menus might get a bit of an overhaul

Next meeting

The next meeting will take place on March 7, 2018 at 21:00 UTC / March 7, 2018 at 21:00 UTC in the #core Slack 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.

#4-9-5, #authentication, #contributor-day, #core, #core-php, #core-restapi, #dev-chat, #gdpr-compliance, #summary, #two-factor

Daniel Bachhuber 3:00 pm on March 1, 2018

Introducing the Gutenberg Plugin Compatibility Database

Ideally, the majority of WordPress users should be able to use Gutenberg on the day WordPress 5.0 is released. They'll hit "Update WordPress", navigate back to the editor, and continue publishing in Gutenberg with all of the functionality they expect in the Classic Editor.

But plugins! If any one of their active plugins are incompatible with Gutenberg, the WordPress user is likely to experience pain, misery, and bad fortune. Many WordPress installations have a dozen or more active plugins, so WordPress plugins are a significant risk vector for Gutenberg incompatibility.

Enter the Gutenberg Plugin Compatibility Database. The goal for this crowdsourcing tool is to identify whether or not WordPress.org plugins are compatible with Gutenberg. With this data set, we'll be able to:

Know the most likely causes of incompatibility.
Focus developer outreach on the highest impact problems.
Proactively educate WordPress users on whether or not their WordPress installation is ready for Gutenberg.

The only gotcha: we need lots and lots of person-hours for testing. If each plugin takes roughly 1 minute to test, we'll need ~75 person-hours to get through the remaining ~4500 plugins in the database.

Check out the project README.md for a more complete introduction to what's involved. This includes a definition for "Gutenberg-compatible", explanation for why only 5000 plugins are in the database, and other design decisions.

Do you or someone you know have access to lots of person-hours (e.g. WordCamp contributor day, hosting support team, etc.)? I'd love to chat! Feel free to leave a comment, ping me on WordPress.org Slack (I'm 'danielbachhuber'), or get in touch however most convenient.

Jeffrey Paul 2:56 am on February 28, 2018
Tags: 4.9.5 ( 8 ), agenda ( 277 ), contributor day ( 3 ), core ( 65 ), dev chat ( 218 )

Dev Chat Agenda: February 28th (4.9.5 week 4)

This is the agenda for the weekly dev meeting on February 28, 2018 at 21:00 UTC / February 28, 2018 at 21:00 UTC:

4.9.5 planning
Updates from focus leads and component maintainers
WCEU Contributor Day
General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-5, #agenda, #contributor-day, #core, #dev-chat

K�nst�nt�n Ob�nland 3:45 am on February 27, 2018
Tags: make.wordpress.org/meta, p2-xpost ( 9 )

X-post: Two Factor Authentication on WP.org

X-post from +make.wordpress.org/meta: Two Factor Authentication on WP.org

Alain Schlesser 3:52 pm on February 26, 2018
Tags: core-php ( 32 ), PHP ( 26 ), servehappy ( 9 ), summary ( 154 )

PHP Meeting Recap – February 19th

You can find this meeting’s chat log here.

Chat Summary

Main topic for this meeting was to discuss the two different implementations of the servehappy notice we have so far:
- an admin notice that appears at the top of all pages;
- a dashboard widget that only appears on the dashboard.
@flixos90 quickly described the main benefits of the alternative dashboard widget approach:
- it requires less logic;
- it is harder to unintentionally hide;
- it matches what the browsehappy project did.
We discussed how best to set the priority of the widget, so it won’t be displayed below the fold. @clorith noted that adding it to dashboard.php would ensure it is always shown first, just like the browsehappy one.
Those present during the meeting unanimously voted for the dashboard widget, instead of the admin notice. We thus decided to go with the alternative approach of the dashboard widget moving forward.
We decided to work on getting this into trunk for now, with the option of backporting it to the next minor release if there’s consensus later on.
The reshowing of the widget should not be included in the code for now, but could be part of the “database migration” code that gets run on updates. This lets us defer the decision of when to reshow.
The discussion then moved on to a ServeHappy API endpoint on wp.org that could be used to dynamically control the behavior of the dashboard widget.
@flixos90 has implemented a first version of the API endpoint following the details we’ve discussed, and it is already available right now: https://api.wordpress.org/core/serve-happy/1.0/?php_version=5.2
The information that is sent to the ServeHappy API endpoint (PHP version + indirectly IP address through server access logs) might have implications on GDPR compliance. We should raise this concern in the #gdpr-compliance channel.
We discussed how to let hosts provide upgrade information. A mechanism using constants or filters would be preferable to providing this through the API endpoint, as we’d want to decentralize this information and not maintain it ourselves.

Next week’s meeting

Next meeting will take place on Monday, February 26, 2018 at 16:00 UTC in #core-php.
Agenda: Discuss the new API endpoint.
If you have suggestions about this but cannot make the meeting, please leave a comment on this post so that we can take them into account.

#core-php, #php, #servehappy, #summary

Jeffrey Paul 7:11 pm on February 22, 2018
Tags: 4.9.5 ( 8 ), core ( 65 ), core-editor ( 58 ), core-media ( 13 ), dev chat ( 218 ), gdpr-compliance ( 9 ), gutenberg ( 38 ), summary ( 154 )

Dev Chat Summary: February 21st (4.9.5 week 3)

This post summarizes the dev chat meeting from February 21st (agenda, Slack archive).

4.9.5 planning

@danieltj self-nominated to lead this minor release, but as a first time lead we’d like someone who already led one to be deputy. Please reach out to @jbpaul17 (@jeffpaulon Slack) or comment on this post with nominations.
@audrasjb able to assist with bug scrubs, testing, and triage
4.9.5 timeline is still dependent on reducing the number of sites stuck on 4.9.3
Auto-update needs automated end to end tests, @jorbin to look into specifying what’s needed and @joostdevalk on getting implementation assistance
@schlessera to investigate why the update via WP-CLI didn’t fatal whereas the cron update did

Updates from focus leads and component maintainers

The Editor / Gutenberg team released version 2.2 last week and continues to meet #core-editor on Wednesdays with bug scrubs on Thursdays.
The GDPR Compliance team posted notes from their meeting last week, posted a proposed roadmap on tools for compliance, met earlier today, and you can continue to follow along in #gdpr-compliance.
The Media team posted notes from their meeting last week and meet again tomorrow in #core-media.

General announcements

@iandunn ready to commit the following tickets, but would like a quick review from another committer first:
- #41112 – Show WordCamps higher up in the News Dashboard widget – @sergey to review and mark for commit
- #42282 – Provide means of executing PHPUnit continuously over watched files in local environments
- #43101 – Test to ensure MediaElement SWFs aren’t accidentally added to build
@benoitchantre looking for review on four tickets:
- #36455 – Call opcache_reset() after plug-in, theme or core update
- #14877 – Ability to create exclusive custom taxonomies
- #27111 – Turning off global comments should include existing content
- #42645 – Support passing version number to add_editor_style() – @danieltj has a patch for this but it needs testing
@mte90 looking for review on four tickets:
- #40810 – wp_mail fails to send email on WP auto update when wp-cron is called directly by php
- #30991 – Post type object capability ‘delete_posts’ is referenced in the posts list table but does not exist unless ‘map_meta_cap’ is set to true for post type
- #20037 – Introduce ‘noindex’ filter for robots meta tag
- #14148 – wp_get_attachment_url() is not url encoding

Next meeting

The next meeting will take place on February 28, 2018 at 21:00 UTC / February 28, 2018 at 21:00 UTC in the #core Slack 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.

#4-9-5, #core, #core-editor, #core-media, #dev-chat, #gdpr-compliance, #gutenberg, #summary

WordPress.org

Make WordPress Core

Welcome!

Communication

PHP Meeting Recap – February 26th

Chat Summary

Call for Testing

Next week’s meeting

What’s new in Gutenberg? 2nd March

2.3 🍇

Other Changes

Introducing the Gutenberg Plugin Compatibility Database

Dev Chat Agenda: February 28th (4.9.5 week 4)

X-post: Two Factor Authentication on WP.org

PHP Meeting Recap – February 19th

Chat Summary

Next week’s meeting