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 Agenda: February 13th

This is the agenda for the weekly Tide meeting on February, 13 2018 at 22:00 UTC / February 13, 2018 at 22:00 UTC:

  • PHP compatibility integration planning
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#agenda, #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

Tide Chat Agenda: February 6th

This is the agenda for the weekly Tide meeting on February, 6 2018 at 22:00 UTC / February 6, 2018 at 22:00 UTC:

  • PHP compatibility integration planning
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#agenda, #tide-chat

Tide Chat Summary: January 30th

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

Feedback on code reviews

  • If you are having questions on getting setup to test Tide or any other issues that could be addressed please reach out in the #tide Slack channel

UX of PHP compat integration into WP.org

General announcements

  • @valendesigns: I'm still working on the GCP migration, things are getting a slow start but should have an update on progress maybe next week

Next meeting

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

This is the agenda for the weekly Tide meeting on January, 30 2018 at 22:00 UTC / January 30, 2018 at 22:00 UTC:

  • Feedback on code reviews
  • UX of PHP compat integration into WP.org
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#agenda, #tide-chat

Tide Chat Summary: January 23rd

This post summarizes the Tide chat meeting from January 23rd 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.

Feedback on code reviews

  • Continuing to look for feedback on Tide repos or existing plugin and theme audit results (focused specifically on PHP Compatibility)
  • @timothyblynjacobs looking for ability to test audit server by passing a JSON payload to it
  • @valendesigns noted it can be tested locally but you need AWS resources to do it (i.e., an SQS queue and an S3 bucket), AWS comes with a free trial to test it out
  • @danlouw looking into way to mock SQS for testing, to try to have something for next week's chat and add to one of the README's
  • The audit server was a proof of concept and intent is to rebuild it with Go, which could include mocked testing, but adding it to the current  implementation is unlikely
  • Best to document improvements desired as Issues filed to respective GitHub repo, and if uncertain which to choose just use tide-issues

UX of PHP compat integration into WP.org

  • @joshuawold added two more mockups into the issue, will look to add a mockup showing a theme page and simplify listing of errors/warnings
  • Plan to assemble mockups and look to #meta for feedback or confirm approach

Documentation

Next meeting

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

This is the agenda for the weekly Tide meeting on January 23, 2018 at 22:00 UTC / January 23, 2018 at 22:00 UTC:

  • Feedback on code reviews
  • UX of PHP compat integration into WP.org
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#agenda, #tide-chat

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

Tide Chat Agenda: January 16th

This is the agenda for the weekly Tide meeting on January 16, 2018 at 22:00 UTC / January 16, 2018 at 22:00 UTC:

  • Feedback on code reviews
  • UX of PHP compat integration into WP.org
  • Infrastructure migration
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#agenda, #tide-chat