This post summarizes the Tide chat meeting from April 10th in the #tide SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel (agenda, Slack archive).

Reminder that the current Tide focus is integrating PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. Compatibility data from Tide into WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://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 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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 sniffssniff A module for PHP Code Sniffer that analyzes code for a specific problem. Multiple stiffs are combined to create a PHPCS standard. The term is named because it detects code smells, similar to how a dog would "sniff" out food. 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` categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., 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 PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. 3.2 whitelist comments as the sniffsniff A module for PHP Code Sniffer that analyzes code for a specific problem. Multiple stiffs are combined to create a PHPCS standard. The term is named because it detects code smells, similar to how a dog would "sniff" out food. 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 + WPCSWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016. – 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 UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it.

• @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 GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Issue
• Once UX is set, we’ll hand off to the #meta team for integration with the Tide APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. 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