Tide Chat Summary: February 20th

This post summarizes the Tide chat meeting from February 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

Reliability of sniffs

  • @rheinardkorf began process of refactoring the Audit Server in Go and noticed some anomalies in the PHPCompatibility standard (grammar used in messaging has been inconsistent), while waiting for a fix he wrote a parser to understand the messages which then generated a compatibility map for the audit server
  • Results should now be more accurate and inclusive of versions below or above the reported version that violates a sniff (e.g., some features work only on 5.3 but no other version)
  • @rheinardkorf to release the tests and mapping to `wptide/pkg` repo shortly, this is a Go library with tools being used for the Go driven services with the Sync Server as the first one to adopt the package and the new Audit Server will as well

PHP compatibility integration planning

  • 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).

WCEU Contributor Day

  • @milana_cap organizing WCEU Contributor Day and looking to see if Tide plans to participate
  • Please comment on this post or share in #tide if you’re planning to attend WCEU and have interest and ability to help lead a group contributing to Tide
  • We’ll revisit this topic next week and look to decide if Tide will be present and if so who can help coordinate

Next meeting

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

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 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 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 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 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 Summary: January 9th

This post summarizes the Tide chat meeting from January 16th in the #tide Slack channel (agenda, Slack archive).

Feedback on code reviews

  • Open question on caching and results in relation to plugin versioning
  • Aiming to merge develop to master next week when folks are back from vacation, update to come next week
  • @peterbooker noted performance on sync server could improve (e.g. svn changelog from a specific revision), will review more during next week's meeting
  • Any Issues and PRs can get filed to github.com/wptidegithub.com/wptide/tide-issues is a generic place to dump issues if you’re not certain which repo to use

UX of PHP compat integration into WP.org

  • Based on followup from @mapk, @rheinardkorf and @obenland@joshuawold sketched up some options for how the PHP compatibility results could display on the plugin. Feedback is welcome on the linked GitHub issue. The biggest thing that would help is getting a sense of which option we should work toward.
  • Mockups show an error count, those relate to errors that cause incompatibility with a specific PHP version
  • PHP compat results are primary focus within UX, "Tide Standards" and any other copy around what those mean, how they’re generated, etc. are secondary though helpful

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 Summary: December 12th

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

Tide focus

  • Current focus/priority/goal 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

Progress on code open sourcing

  • @valendesigns: we are working towards being 100% Open Source and having the API back online (with re-audit) no later than December 20th, likely sooner. The transition to Open Source is not a straight forward task and has been pretty much been the teams singular focus since last week. We are rebuilding the local dev environment to make it easier to contribute. We can't open the sources without exposing sensitive data so all the repos are being rebuilt.
  • @valendesigns @rheinardkorf @danlouw @jbpaul17 from XWP are working on Tide
  • Tide API will include WPCS and PHPCompatibility output, scoring will no longer exist
  • wptide.org site from WCUS was a client to demo what COULD be done, it wasn’t meant to be what WILL be done on actual Tide integration to WordPress.org
  • Demo from WCUS wasn't 100% functional, some things may have worked better than others
  • After code is available as open source, we'll need lots of testing to help ensure results are faultless
  • @sergey has done work on some PHP-related tickets, would be good to have him gloss over the PHP compat part of the code when released
  • @williampatton able to assist with docs if there is guidance on what's needed
  • @barry to handle WP.org integration, @otto42 waiting until API is ready to query against

UX for integration of PHP Compat from Tide into WordPress.org

  • @joshuawold is the design lead at XWP managing UX for how PHP Compatibility could be integrated into WordPress.org, working with @maximsiebert on UX options
  • We'll want input from someone on the Meta and Design teams as feasible to review the UX/design
  • @obenland can cover Design from Make/Plugins
  • #40934 is prior work covering UX around not being able to install a plugin when your PHP version is not compatible, @joshuawold to review this and as input on PHP Compat UX for WP.org
  • @joshuawold to review UX with @mapk who was the original designer for the plugin directory
  • Updates on UX/design to be shared in #tide as they're available

Next week’s meeting

The next meeting will take place on December 19, 2017 at 22:00 UTC / December 19, 2017 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 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