Tide Chat Summary: December 5th

This post summarizes the Tide chat meeting from December 5th in the #tide Slack channel (Slack archive).

Discussion highlights

Tide priorities

  • Priority is working to integrate Tide into WordPress.org
  • Success is defined as seeing PHP compatibility and error/warnings on WordPress.org plugin/theme pages
  • Will need to work through UX of what’s best to display on WordPress.org (@joshuawold @maximsiebert working through options)
  • We need to figure out exactly where the Audit Server & API is going to live and whether we’re moving to GCP (not an easy lift) from AWS or if this will be hosted on the .ORG servers (@chanthaboune @barry to provide input)
  • Next step is to define actions to integrate Tide into WordPress.org, who owns each action, and a timeline for each action
  • Once Tide has been integrated into WordPress.org we’ll reassess community input and move on to what’s next most impactful for the community
  • If you have ideas, please comment on this post and we’ll collect them for prioritization post-integration

Tide documentation

  • The following items need to be assembled to start working as a community:
    • Correct wptide.org redirects to correctly go to make.wordpress.org/tide (aka “make/tide”)
    • Open source Tide repo
    • Open source Tide documentation + architecture diagram (dependent on integration with wp.org details, @joshuawold to clean up diagram of current ecosystem)
    • Create Tide handbook pages (e.g., code/issues/release planning lives on GitHub, deadlines aren’t arbitrary, background on the creation of Tide, you can use phpcbf to fix the easy stuff)

Tide contributions

  • Will need to figure out how best to support community contributions, dependent on final infrastructure
  • One way of contributing indirectly would be to get involved with the various projects/standards used to generate audit results: PHPCS, WPCS, PHPCompatibility, Theme Review team standards

General announcements

  • Where can I see results like I saw at the Tide booth at WCUS?
    • While there is not an immediate timeline, that will happen as soon as we can finish the integration into WordPress.org.

Next week’s meeting

The next meeting will take place on Tuesday, December 12, 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

New Home

Welcome to the new website for the Tide project!

Tide already has a private code repository and an issue tracker, which will be made public in the next few weeks. Subscribe to this blog for updates when it becomes public, or join us in the #tide channel on Slack.

The mission of Tide is to raise the code quality of all the plugins and themes in the WordPress.org directories. Tide’s name reflects this mission, derived from the proverb “a rising tide lifts all boats”.