Jeffrey Paul 2:28 pm on October 24, 2018  

Tide Chat Summary: October 23rd

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

Repo decommissioning + deletion

Transition to office hours

  • @jeffpaul will be out of the office for the next couple of weeks, so we’ll be transitioning to <office-hours> during our normal <tidechat> times until his return the week of November 12th
  • Feel free to call out questions/issues/concerns in the #tide Slack channel and we’ll plan to respond asynchronously in the meantime

General announcements

Next meeting

As noted above, we’ll be transitioning to office hours for the next couple of weeks while @jeffpaul is away.  Please drop in to the #tide Slack channel in the meantime and we’ll respond asynchronously. 

The next meeting will take place on November 13, 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.

Jeffrey Paul 9:50 pm on October 22, 2018
Tags: ,   

Tide Chat Agenda: October 23rd

This is the agenda for the weekly Tide meeting on October 23, 2018 at 20:00 UTC:

  • Repo decommissioning + deleting
  • Transition to office hours
  • 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:02 pm on October 3, 2018
Tags: ,   

Tide Chat Summary: October 2nd

This post summarizes the Tide chat meeting from October 2nd 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.

Repo deletion

  • Reminder that we decommissioned several repos for the alpha version of Tide from WCUS 2017 and we’ll be deleting those repos shortly, see:
    • https://github.com/wptide/api/issues/9
    • https://github.com/wptide/lighthouse-server/issues/3
    • https://github.com/wptide/sync-server/issues/17
    • https://github.com/wptide/audit-server/issues/26
    • https://github.com/wptide/tide-local/issues/14
  • Please call out any questions or concerns about fully deleting those repos here, in #tide, or on the issues linked above

Setup and testing feedback

  • When testing the Tide local setup, use this branch as it addresses the issue where the Lighthouse image was failing to build
  • Looking for feedback (ideally via GitHub issues) from anyone who has been able to attempt the setup and running of Tide locally
  • For those who get the time to run through the local setup and can provide feedback (positive or negative), then we’d appreciate the contribution!

Next meeting

The next meeting will take place on October 9, 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.

#summary, #tide-chat

Jeffrey Paul 2:43 am on September 27, 2018
Tags: , ,   

Tide Chat Summary: September 25th

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

1.0.0 planning

  • As noted last week (and the week before), the GitHub repo is setup with 1.0.0 and Future Release release labels, will continue to work through the 1.0.0 items and  appreciate any additional contributions on those labeled issues

Repo decommissioning + deleting

  • As noted previously, we decommissioned several repos for the alpha version of Tide from WCUS 2017 and have opened issues noting that we’ll be actually deleting those repos shortly, namely:
    • https://github.com/wptide/api/issues/9
    • https://github.com/wptide/lighthouse-server/issues/3
    • https://github.com/wptide/sync-server/issues/17
    • https://github.com/wptide/audit-server/issues/26
    • https://github.com/wptide/tide-local/issues/14
  • Note that none of those repos are still relevant to the 1.0.0-beta version of Tide and can cause confusion when people view those repos while trying to setup and run Tide locally
  • Please call out any questions or concerns about fully deleting those repos here or on the issues linked above

Setup + testing feedback

  • When testing the Tide local setup, use this branch as it addresses the issue where the Lighthouse image was failing to build
  • Looking for feedback from anyone who has been able to attempt the setup and running of Tide locally
  • For those who get the time to run through the local setup and can provide feedback (positive or negative), then we’d appreciate the contribution!

Next meeting

The next meeting will take place on October 2, 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, #summary, #tide-chat

Jeffrey Paul 3:18 pm on September 24, 2018
Tags: ,   

Tide Chat Agenda: September 25th

This is the agenda for the weekly Tide meeting on September 25, 2018 at 20:00 UTC:

  • 1.0.0 planning
  • Repo decommissioning + deleting
  • Setup + testing feedback
  • 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:11 pm on September 19, 2018
Tags: , ,   

Tide Chat Summary: September 18th

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

1.0.0 planning

  • Looking for feedback on people setting up / using v1.0.0-beta
  • With GitHub issues fully scrubbed, looking to see who is able to contribute to items labeled as 1.0.0
  • Challenge issued to those following along to try setting up Tide v1.0.0-beta locally and providing feedback

Next meeting

The next meeting will take place on September 25, 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, #summary, #tide-chat

Jeffrey Paul 10:37 pm on September 5, 2018
Tags: , , ,   

Tide Chat Summary: September 4th

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

1.0.0 planning

Theme ruleset

  • Discussion with @joyously on being able to utilize Tide and the WPThemeReview repo and ruleset to help automate Theme Reviews
  • Update from @jrf that Theme Review will become a stand-along project consisting of a Theme Review specific PHPCS ruleset WPThemeReview using sniffs from PHPCS, WPCS, PHPCompatibility (probably) and some Theme Review native sniffs
  • @jrf cleaning the repo out, when done the repo can be pulled in using Composer and the WPThemeReview ruleset could be used by Tide for themes

Next meeting

The next meeting will take place on September 11, 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, #summary, #themereview, #tide-chat

Jeffrey Paul 5:57 pm on August 21, 2018
Tags: , ,   

Tide Chat Summary: August 14th

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

1.0.0 planning

  • 1.0.0-beta announced earlier this summer, beginning discussion on items worth including in release candidate(s) and an eventual release of Tide 1.0.0
  • Likely to include upgrade to WPCS v1.0+, polish docs, complete API to integrate with .ORG, update API to note which version of the standard the audit used
  • Will use next week tidechat time slot to scrub GitHub issues and label items ideally within the 1.0.0 release

Theme and plugin rulesets

  • Important to begin working on expanding to specific rulesets for plugins and themes so that we’re not just using the full WordPress Core ruleset when auditing plugins and themes
  • This is something we’re looking to the community to help with and hope that we can get direct feedback and assistance from the Plugin and Theme Review teams
  • If you have interest and availability to assist on this, then please reach out in #tide or ping @jeffpaul or @valendesigns directly
  • See proof of concept from @jrf as well as talk where she demo-ed the concept, this is a great starting point for these custom rulesets
  • In order to release Tide 1.0.0 we want to include a custom ruleset

Next meeting

The next meeting (note focus on bugscrub) will take place on August 21, 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, #summary, #tide-chat

Jeffrey Paul 1:52 am on August 14, 2018
Tags: ,   

Tide Chat Agenda: August 14th

This is the agenda for the weekly Tide meeting on August 14, 2018 at 20:00 UTC:

  • 1.0.0 planning
  • Theme and plugin rulesets
  • 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:38 pm on June 27, 2018
Tags: , , , ,   

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