Tide Chat Summary: January 16th

This post summarizes the Tide chat meeting from January 16th 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/priority/goal to provide the biggest impact to the community.

Feedback on code reviews

  • audit-server image is not building due to something changing in one of the base images, @valenddesigns to troubleshoot that and merging the PRs
  • sync-server not worth trying to optimize it as its doing the job it was intended to do, a bulk repo audit. An ideal would be for a new job to be sent to SQS at the time the repo produces a new zip. The sync-server really should not be required at all. The sync-server can be removed if there is a push notification sent to initiate the SQS message i.e. webhook or similar. In a perfect world the sync-server would be decommissioned and the svn repo would send a request to be audited.
  • It would help to identify audit-server failure points and understand why some plugins/themes cannot be audited, making this more performant is definitely something we should and are planning to do. Possibly convert it to Go, but still requires PHPCS. Go can run concurrent processes, so utilizing max amount of CPU resources per image, it will not make PHPCS quicker, but will make better usage of resources.

UX of PHP compat integration into WP.org

Infrastructure migraiton

  • We will be working on migrating the infrastructure to Google Cloud Platform (GCP) over the next few weeks. There is a decent amount of DevOps and automation to redo in order to make that work, plus we need to replace all the AWS SDKs.
  • Step 1: lift and shift the infrastructure without changing the SDKs, while updating the automation (i.e. Docker image build/push from Travis to GCP)
  • Step 2: replace the SDKs and re-architect

Next meeting

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