Tide Chat Summary: June 26th

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

WCEU recap

  • Contributor Day had WiFi issues for the first half of the afternoon so setting up Tide locally was a bit harder for folks than it should have been
  • Contributors mostly discussed what Tide is and the GCP setup and capacity over AWS
  • There we a couple PR’s that came out of Contributor Day
  • @grapplerulrich did a great job leading the team while @valendesigns had focus split getting the final GCP issues ironed out

GCP migration & .ORG integration

  • The migration to GCP is for the most part complete. Now that we’re in v1.0.0-beta we only have a couple of issues to fix.
  • There are docs that need to be tested and updated, a duplicate audits issue where Firestore is not locking the message quick enough and other kubernetes pods are running the same audits more than once (not on every item but enough to be an issue), and the endpoint for .ORG that allows a push instead of pull architecture (this code is written but @valendesigns need to test and merge).
  • Seeing a lot more capacity over AWS, maybe 8-10 times more. We were doing at peak around 1.3-1.8k an hour on AWS and on GCP we were doing 12-13.4k an hour.
  • When all of the issues mentioned above are sorted we will release v1.0.0 and plan to do a few RC’s until they are addressed
  • @jeffpaul to open issue for item that @grappIerulrich found that is not working, if anyone else runs into issues, please open issues in GitHub

Theme and plugin rulesets

  • This was discussed some at WCEU, but the idea is to create a ruleset for auditing WordPress themes and another for WordPress plugins. The complete WPCS ruleset isn’t quite the best approach for plugins and themes individually, so we’re considering creating a ruleset specific to each.
  • @grapplerulrich looking to run the subsets instead of the whole `WordPress` ruleset? These would be `WordPress-Core`, `WordPress-Docs` and `WordPress-Extra`. This would give us more fine tuned results and exclude `WordPress-VIP`. If we make the change now then we will have a few plugin version to be able to understand the trend.
  • We had a conversation with roughly 10 or so contributors on Saturday and the work @jrf has done could be used as the base for targeting plugins/themes. It’s going to need a lot of discussion but some of the heavy technical lifting has already been done.
  • We’ll likely look to open upstream issues with WPCS to further the discussion on this topic, we’ll share those issue links here once they’re created.

General announcements

  • In order to accommodate a wider audience, we’ll be moving the Tidechat one hour earlier starting next week, so we’ll now meet weekly at 20:00 UTC.

Next meeting

The next meeting will take place on July 3, 2018 at 20: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.

#1-0-0, #gcp, #summary, #tide-chat, #wceu

Tide Chat Summary: June 5th

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

GCP migration

  • Completed the initial standup of Tide on GCP in a Dev account and tested all services are working, though we have found some minor bugs that we’re currently addressing
  • Working to fix the minor bugs and setup Tide on the new Prod account the next couple of days and start the re-audit of all themes and plugins by the end of the week
  • Next week we’ll be setting up DNS to transfer from the AWS to the GCP version of Tide, we’ll then be at Tide 1.0.0-beta and ready to find all the bugs and test the new API
  • Current issue is the local MongoDB is not connecting to the Go services correctly and we’re working on a fix
  • The new repo is an all-in-one Tide repo for development and deployment, can be installed locally, and will be released as soon as the Mongo issue is fixed
  • Tide will be available by WCEU, and can be demonstrated at contributor day on Thursday, June 14th
  • After WCEU we’ll work to create a few candidate releases until we feel Tide is stable and ready to be tagged 1.0.0

.ORG integration

  • @jeffpaul and @valendesigns to chat with @otto42 on the webhook integration of Tide’s PHP Compatibility results into .ORG
  • Identifying any changes needed to the input to, processing of, or output from Tide as it relates to .ORG so we know what gaps need to be closed in order to support a .ORG integration. Updates to follow as we’re able to meet with @otto42, but that will likely be after WCEU.
  • In the meantime, review and feedback on the proposed UX for the integration would continue to be welcomed
  • Integration will provide a list of compatible versions, could be used to allow of disallow plugin activation per note from @joyously

General announcements

  • With folks traveling next week to WCEU, we’ll cancel the weekly tidechat and catch up the following week

Next meeting

The next meeting will take place on June 19, 2018 at 21:00 UTC / June 19, 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, #php-compatibility, #summary, #tide-chat

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

Tide Chat Summary: May 8th

This post summarizes the Tide chat meeting from May 8th in the #tide Slack channel (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.

WCEU Contributor Day

  • @grapplerulrich to help on the Tide front while @jrf will be with the Coding Standards group, with both teams sitting next to each other
  • Focus will be to get people familiar with WPCS and PHPCompatibility. Potentially getting folks setup to run their own code through WPCS and PHP Compat to see where they can improve things. If they’re more evolved than that, potentially having folks look at contributing to WPCS issues or PHP Compat issues.
  • Additionally, spending some time with the Meta crew and discussing the proposed UX for integrating the PHP Compat results on WordPress.org would be beneficial

Roadmap wishlist

  • Currently collecting ideas, will asses feasibility, and share roadmap as its ready
  • Note on post-chat idea from @joyously: There’s a handy tool online that scans your plugin or theme zip and tells you the minimum required WP version. Seems like something that Tide could do.
  • If you have roadmap wishlist ideas, then please leave them as a comment on this post and we’ll capture them as we work towards publishing a potential roadmap for Tide

Next meeting

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

#summary, #tide-chat

Tide Chat Summary: May 1st

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

GCP migration

  • @valendesigns: mostly been going smoothly but we’ve hit a blocker in the new Go version of the audit server which we’re working to address
  • We’re hoping to get back on track next week and finally replace the AWS SDK with GCP equivalents but we can’t continue that work until we’re unblocked by the partly working Go audit server
  • GCP infrastructure has been tested and works we’re just trying to get past this last hurdle to stand everything up on GCP
  • If you have Go experience, please reach out to @jbpaul17 (@jeffpaul in Slack) as this is an area that needs help on Tide

PHPCompatibility

  • @valendesigns: we are testing the new phpcompat for WP ruleset in the new Go server. Unfortunately, processes are not blocking and causing the audit to not happen so we haven’t gotten a result back using the new ruleset
  • Once we get a result back though we can unblock @joshuawold and give him a result example to use for real data

Roadmap wishlist

  • As we work through the PHP Compatibility integration, we’re asking for input on roadmap wishlist items to consider post-PHP Compat integration
  • @lukecarbis: I wish there was a page on w.org where I could upload a theme / plugin and get all the tide audit results (including PHPCS). Use case is to upload plugins / themes as I work on them to get the PHPCS results (without having to figure out how to install PHPCS on my machine).
  • For devs that want to see results without publishing code on wp.org, input was that this might be best hosted elsewhere on a separate domain
  • If you have roadmap wishlist ideas, then please leave them as a comment on this post and we’ll capture them as we work towards publishing a potential roadmap for Tide

Next meeting

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

#summary, #tide-chat

Tide Chat Summary: April 17th

This post summarizes the Tide chat meeting from April 17th 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 Compat UX

WordPress-specific PHPCompatibility standard

  • @nikolam met with @williampatton and had proposal for detecting WP shims and handling fallback code
  • @jrf and @valendesigns confirmed proposed approach wasn’t viable, but open to other ideas on how to solve these issues (see: 301 and 569)

Next meeting

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

#summary, #tide-chat

Tide Chat Summary: April 10th

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

WordPress-specific PHPCompatibility standard

  • two open Core tickets to add two more back-fills, once those are merged @jrf will add them to the ruleset
  • The current ruleset covers the whole `wp-includes/compat.php` file and some extras, any additional backfills in Core should moved to the appropriate place
  • PRs to PHPCompatibility for this should be merged reasonably quickly as long as they are accompanied with a link to the source code where the backfill can be found

PHPCompatibility update

Future consideration

  • @jrf created a QA ruleset for WP projects + a custom report for that and I’ve given some talks about this; ruleset used for the talks could possibly be used as inspiration for the next step of the Tide project
  • The QA ruleset is basically PHPCompatibility + WPCS – all the codestyle related sniffs, so just focuses on PHP cross-version compat + PHP and WP best practices and it offers a custom report
  • Voting on proposal in WPCS on this topic would be welcome

PHP Compat UX

  • @joshuawold and @karmatosed have been iterating on the UX and updates are tracking in GitHub
  • current approach is an accordion display of partial error types and then a “show all” option to view a full list of errors/warnings
  • If you have feedback on this approach, please comment on the GitHub Issue
  • Once UX is set, we’ll hand off to the #meta team for integration with the Tide API results using the PHPCompatibility ruleset

Infrastructure

  • We should be moved to GCP in the next couple weeks, this means the API will be moving and the data rebuilt from scratch to test the platform
  • Will include a new local setup coming soon that will be for GCP and remove all the dependencies on AWS

WCEU attendance

  • Currently @jrf, @valendesigns, and @joshuawold plan to attend
  • Comment on this post if you also plan to attend so we can try to coordinate a get-together for those in Belgrade

Next meeting

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

#summary, #tide-chat

Tide Chat Summary: March 27th

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

Tidechat meeting time

  • We’re adjusting our weekly meeting time back an hour, so the weekly Tidechat will start on Tuesday’s at 21:00 UTC beginning next week

WordPress-specific PHPCompatibility standard

Infrastructure migration

  • @valendesigns still working hard on moving everything from AWS to GCP just have been pulled in a couple different directions and causing slight delays

Next meeting

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

#summary, #tide-chat

Tide Chat Summary: March 20th

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

WordPress-specific PHPCompatibility standard

Dashicons

  • We continue to look for help on a PR related to the issue of creating a Dashicon for Tide, please reach out if you’re able to assist
  • Work on this will likely need to be folded into #41074

Next meeting

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