Tide Chat Summary: January 9th

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

Feedback on code reviews

  • Open question on caching and results in relation to plugin versioning
  • Aiming to merge develop to master next week when folks are back from vacation, update to come next week
  • @peterbooker noted performance on sync server could improve (e.g. svn changelog from a specific revision), will review more during next week's meeting
  • Any Issues and PRs can get filed to github.com/wptidegithub.com/wptide/tide-issues is a generic place to dump issues if you’re not certain which repo to use

UX of PHP compat integration into WP.org

  • Based on followup from @mapk, @rheinardkorf and @obenland@joshuawold sketched up some options for how the PHP compatibility results could display on the plugin. Feedback is welcome on the linked GitHub issue. The biggest thing that would help is getting a sense of which option we should work toward.
  • Mockups show an error count, those relate to errors that cause incompatibility with a specific PHP version
  • PHP compat results are primary focus within UX, "Tide Standards" and any other copy around what those mean, how they’re generated, etc. are secondary though helpful

Next meeting

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