Tide Chat Summary: April 17th

This post summarizes the Tide chat meeting from April 17th 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.

PHP Compat UX

WordPress-specific PHPCompatibility standard

  • @nikolam met with @williampatton and had proposal for detecting WP shims and handling fallback code
  • @jrf and @valendesigns confirmed proposed approach wasn’t viable, but open to other ideas on how to solve these issues (see: 301 and 569)

Next meeting

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

#php-compatibility, #summary, #tide-chat, #ux

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.

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

Tide Chat Summary: March 27th

This post summarizes the Tide chat meeting from March 27th 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.

Tidechat meeting time

  • We’re adjusting our weekly meeting time back an hour, so the weekly Tidechat will start on Tuesday’s at 21:00 UTC beginning next week

WordPress-specific PHPCompatibility standard

Infrastructure migration

  • @valendesigns still working hard on moving everything from AWS to GCP just have been pulled in a couple different directions and causing slight delays

Next meeting

The next meeting will take place on April 3, 2018 at 21:00 UTC / April 3, 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

Tide Chat Summary: March 20th

This post summarizes the Tide chat meeting from March 20th 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

Dashicons

  • We continue to look for help on a PR related to the issue of creating a Dashicon for Tide, please reach out if you’re able to assist
  • Work on this will likely need to be folded into #41074

Next meeting

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

#dashicons, #php-compatibility, #summary, #tide-chat

Tide Chat Summary: March 13th

This post summarizes the Tide chat meeting from March 13th 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

  • Current PR will move to parent PHPCompatibility repo’s library and work to add includes/excludes for WordPress will continue there
  • Once WP ruleset is pulled into PHPCompatibility, @jrf will add a section to the readme about how these can be used
  • @joshuawold iterated on the PHPCompat integration UX, awaiting further feedback on updated mockup before submitting Meta Trac ticket to continue discussion on PHP Compat integration

Dashicons

General announcements

  • @brechtryckaert looking for docs on contributing to Tide (example), able to help craft docs as well, recommends using handbook over a docs repo or devhub
    • @jbpaul17 will work to prioritize this and iterate in the handbook

Next meeting

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

#dashicons, #documentation, #php-compatibility, #summary, #tide-chat

Tide Chat Summary: March 6th

This post summarizes the Tide chat meeting from March 6th 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

PHP compatibility integration planning

  • Current plan is to create the custom sniffs, to verify accuracy, and we should be able to integrate after that
  • @joshuawold working through feedback on the UX for integration
  • No additional input on this topic has come in several weeks, so we’ll plan to drop this from the agenda next week but please call out  in Slack with anything additional that should be covered before/during integration.

Dashicons

Next meeting

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

#dashicons, #php-compatibility, #summary, #tide-chat

Tide Chat Summary: February 27th

This post summarizes the Tide chat meeting from February 27th 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

PHP compatibility integration planning

  • Current plan is to create the custom sniffs, to verify accuracy, and we should be able to integrate after that

WCEU Contributor Day

  • @grapplerulrich plans to attend and work on WP Theme specific WPCS rulesets, so for now that will be the Tide teams’ presence
  • If anyone else confirms their attendance and interest in helping lead, then please reach out to @jbpaul17 (@jeffpaul on Slack) and @milana_cap (@zzap on Slack)

Next meeting

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

Tide Chat Summary: February 20th

This post summarizes the Tide chat meeting from February 20th 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

Reliability of sniffs

  • @rheinardkorf began process of refactoring the Audit Server in Go and noticed some anomalies in the PHPCompatibility standard (grammar used in messaging has been inconsistent), while waiting for a fix he wrote a parser to understand the messages which then generated a compatibility map for the audit server
  • Results should now be more accurate and inclusive of versions below or above the reported version that violates a sniff (e.g., some features work only on 5.3 but no other version)
  • @rheinardkorf to release the tests and mapping to `wptide/pkg` repo shortly, this is a Go library with tools being used for the Go driven services with the Sync Server as the first one to adopt the package and the new Audit Server will as well

PHP compatibility integration planning

  • If you have additional tasks that you see as necessary ahead of final integration of PHP Compatibility details on WordPress.org, then please reach out to @jbpaul17 (@jeffpaul on Slack).

WCEU Contributor Day

  • @milana_cap organizing WCEU Contributor Day and looking to see if Tide plans to participate
  • Please comment on this post or share in #tide if you’re planning to attend WCEU and have interest and ability to help lead a group contributing to Tide
  • We’ll revisit this topic next week and look to decide if Tide will be present and if so who can help coordinate

Next meeting

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

Tide Chat Summary: February 13th

This post summarizes the Tide chat meeting from February 13th 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.

PHP compatibility integration planning

  • There is still a need to validate the accuracy of results
  • Concern from @timothyblynjacobs on audit results (WP CLI-related and WP shimmed functions-related) and their ability to provide confidence on PHP compatibility, but some disagreement on whether these issues should be handled by PHPCompatibility or Tide
  • Need identified in creating a PHPCompatibility ruleset that takes into account WordPress shims and other WP-specific issues, even if it is just a WPPHPCompatibility standard with `ruleset.xml` that includes `PHPCompatibility`
  • Further, a need identified for a repo for rulesets that import standards and add inclusions and exclusions
  • If you have interest and availability to help with the above items, then please reach out in the #tide channel… thanks!
  • If you have additional tasks that you see as necessary ahead of final integration of PHP Compatibility details on WordPress.org, then please reach out to @jbpaul17 (@jeffpaul on Slack).

Next meeting

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

Tide Chat Summary: February 6th

This post summarizes the Tide chat meeting from February 6th 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.

PHP compatibility integration planning

  • If you have tasks that you see as necessary ahead of final integration of PHP Compatibility details on WordPress.org, then please reach out to @jbpaul17 (@jeffpaul on Slack).

General announcements

Next meeting

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