This post summarizes the Tide chat meeting from April 10th in the #tide Slack channel (agenda, Slack archive).

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

• @jrf looking to create a native PHPCompatibility specific report, that requires a change in PHPCS that’s currently earmarked for PHPCS 3.3.0
• 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

Future consideration

• @jrf created a QA ruleset for WP projects + a custom report for that and I’ve given some talks about this; ruleset used for the talks could possibly be used as inspiration for the next step of the Tide project
• The QA ruleset is basically PHPCompatibility + WPCS – all the codestyle related sniffs, so just focuses on PHP cross-version compat + PHP and WP best practices and it offers a custom report
• Voting on proposal in WPCS on this topic would be welcome

PHP Compat UX

• @joshuawold and @karmatosed have been iterating on the UX and updates are tracking in GitHub
• current approach is an accordion display of partial error types and then a “show all” option to view a full list of errors/warnings
• If you have feedback on this approach, please comment on the GitHub Issue
• Once UX is set, we’ll hand off to the #meta team for integration with the Tide API results using the PHPCompatibility ruleset

Infrastructure

• We should be moved to GCP in the next couple weeks, this means the API will be moving and the data rebuilt from scratch to test the platform
• Will include a new local setup coming soon that will be for GCP and remove all the dependencies on AWS

WCEU attendance

• Currently @jrf, @valendesigns, and @joshuawold plan to attend
• 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.

#aws, #gcp, #infrastructure, #php-compatibility, #summary, #tide-chat, #ux, #wceu