Tide Chat Summary: April 10th

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

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.

#summary, #tide-chat

Tide Chat Summary: January 23rd

This post summarizes the Tide chat meeting from January 23rd 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.

Feedback on code reviews

  • Continuing to look for feedback on Tide repos or existing plugin and theme audit results (focused specifically on PHP Compatibility)
  • @timothyblynjacobs looking for ability to test audit server by passing a JSON payload to it
  • @valendesigns noted it can be tested locally but you need AWS resources to do it (i.e., an SQS queue and an S3 bucket), AWS comes with a free trial to test it out
  • @danlouw looking into way to mock SQS for testing, to try to have something for next week's chat and add to one of the README's
  • The audit server was a proof of concept and intent is to rebuild it with Go, which could include mocked testing, but adding it to the current  implementation is unlikely
  • Best to document improvements desired as Issues filed to respective GitHub repo, and if uncertain which to choose just use tide-issues

UX of PHP compat integration into WP.org

  • @joshuawold added two more mockups into the issue, will look to add a mockup showing a theme page and simplify listing of errors/warnings
  • Plan to assemble mockups and look to #meta for feedback or confirm approach

Documentation

Next meeting

The next meeting will take place on January 30, 2018 at 22:00 UTC / January 30, 2018 at 22: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.

#summary, #tide-chat