Tide Chat Summary: May 29th

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

Roadmap wishlist

  • Met previously with folks from Theme Review, coordinating to meet with Plugin Review folks after WCEU on how Tide might best help them
  • If you have roadmap wishlist ideas, then please leave them as a comment on this post, ping @jeffpaul directly, comment in the #tide channel, or add your input as an issue in the `tide-issues` repo and we’ll capture them as we work towards publishing a potential roadmap for Tide

GCP migration

  • Working to migrate to GCP and finishing the Queue and Storage providers for GCP this week; Cloud Storage is finished and Cloud Firestore is WIP; implementing local only providers also
  • Testing the services on GCP this week, depending on how the code review and testing of the Firestore implementation goes
  • By the end of the week we should have a local MongoDB queue provider and be feature complete and ready to clean up the repo, test all services E2E on GCP, and release the new version to the wptide org in GitHub
  • Local setup with be Docker containers, one for each service (API, PHPCS Server, Lighthouse Server, and Sync Server)
  • Assumption that being able to run Tide 100% locally should help make setting it up more appealing to contributors
  • Also adding coverage to the wp-tide-api plugin to ensure it’s solid and ready for the next release
  • Goal by next tidechat is to be ready to have people test the new local setup of Tide and smooth out any issues in regards to needing a cloud provider (AWS or GCP)

WCEU + Contributor Day

  • @valendesigns @jrf @grapplerulrich @nikolam will all be at WCEU and Contributor Day
  • Anyone else who attends should consider stopping by Contributor Day as the Tide and WPCS tables should be next to each other and worth discussing and collaborating then

General announcements

Next meeting

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

#contributor-day, #gcp, #roadmap, #summary, #tide-chat, #wceu

Tide Chat Summary: May 15th

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

Roadmap wishlist

  • Currently collecting ideas, will asses feasibility, and share roadmap as its ready
  • Discussion on things PHPCS is unable to check for that would benefit the #ThemeReview Team (@grapplerulrich, @joyously, @valendesigns):
    • if you are a child or parent theme
    • If a theme has a specific tag in the `style.css` if a certain `add_theme_support()` is defined in the `functions.php`
    • A specific example would be the `custom-header` tag with `add_theme_support( ‘custom-header’ );`
    • The problem is that PHPCS only checks things per file and can’t remember what it has already checked for.
    • things that coordinate between files
    • It would require checking for `add_theme_support` and building an array then verifying that it’s tagged in the header.
    • Benefit is that it would help verify that a theme is actually adding the support for a feature if it using the tag or that if a theme has the feature then it should be tagged correctly so to make it better to search for.
    • Additional details are listed in WPCS issue#578 under Rules which would need another solution
    • We would have to add a new server with a new audit type and wouldn’t be in the phpcs payload
  • If you have roadmap wishlist ideas, then please leave them as a comment on this post, ping @jeffpaul directly, comment in the #tide channel, or add your input as an issue in the `tide-issues` repo and we’ll capture them as we work towards publishing a potential roadmap for Tide

GCP migration

  • We are currently switching to the Google SDKs and then will test everything on GCP. There will be a new repo coming very soon.
  • We will be looking for help testing very soon to setup the new repo, but the goal is to keep the option to use AWS or GCP and, if we can, a local-only option
  • Google Storage and S3 are easy to replace locally. However, SQS is not as easy to replace locally and we’re planning to use Firestore on GCP so two very different solutions that when trying to create a local queue is a bit more work and may not be ready by next week.
  • The migration to GCP and rebuild of the server in Go will ideally be ready for WCEU

Next meeting

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

#gcp, #roadmap, #summary, #tide-chat