Tide Chat Summary: April 10th

Reminder that the current Tide focus is integrating PHP Compatibility data from Tide into WordPress.org. Once PHP Compatibility is integrated into WordPress.org, we’ll assess the next focus to provide the biggest impact to the community.

WordPress-specific PHPCompatibility standard

two open Core tickets to add two more back-fills, once those are merged @jrf will add them to the ruleset

The current ruleset covers the whole `wp-includes/compat.php` file and some extras, any additional backfills in Core should moved to the appropriate place

PRs to PHPCompatibility for this should be merged reasonably quickly as long as they are accompanied with a link to the source code where the backfill can be found

PHPCompatibility update

current backlog of 14 new sniffs to be pulled; 8 for values passed in function call parameters, 5 for various changes to list syntax, 1 for control structure changes

PHPCompatibility has all the sniffs in the `PHP` category, but considering changing that, would impact all rulesets which don’t just include `PHPCompatibility`, but in/exclude individual sniffs; will also impact people who have started to use the new PHPCS 3.2 whitelist comments as the sniff names will change

WCEU attendance

Comment on this post if you also plan to attend so we can try to coordinate a get-together for those in Belgrade

Next meeting

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