Jeffrey Paul 2:20 am on May 22, 2018
Tags:   

CANCELLED – Tide Chat: May 22nd

This week’s Tide meeting is cancelled due to conflicting meetings. If you have roadmap wishlist items or something to add to next week’s agenda, then please leave a comment below. See you next week!

#tide-chat

Jeffrey Paul 6:16 pm on May 16, 2018
Tags: GCP, roadmap, , ThemeReview,   

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

Jeffrey Paul 1:19 am on May 15, 2018
Tags: ,   

Tide Chat Agenda: May 15th

This is the agenda for the weekly Tide meeting on May 15, 2018 at 21:00 UTC / May 15, 2018 at 21:00 UTC:

  • Roadmap wishlist
  • 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

Jeffrey Paul 6:13 pm on May 9, 2018
Tags: ,   

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

Jeffrey Paul 7:09 pm on May 2, 2018
Tags: ,   

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

Jeffrey Paul 2:30 am on May 1, 2018
Tags: ,   

Tide Chat Agenda: May 1st

This is the agenda for the weekly Tide meeting on May 1, 2018 at 21:00 UTC / May 1, 2018 at 21:00 UTC:

  • GCP migration
  • Roadmap wishlist
  • 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

Jeffrey Paul 2:37 am on April 24, 2018
Tags:   

CANCELLED – Tide Chat: April 24th

This week’s Tide meeting is cancelled due to several vacations. If you have anything to add to next week’s agenda, please leave a comment below. See you next week!

#tide-chat

Jeffrey Paul 7:30 pm on April 19, 2018
Tags: ,   

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

Jeffrey Paul 4:00 am on April 17, 2018
Tags: ,   

Tide Chat Agenda: April 17th

This is the agenda for the weekly Tide meeting on April 17, 2018 at 21:00 UTC / April 17, 2018 at 21:00 UTC:

  • PHP Compat UX
  • 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

Jeffrey Paul 7:18 pm on April 11, 2018
Tags: , ,   

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