Tide Chat Summary: February 12th

This post summarizes the Tide chat meeting from February 12th 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-beta2 + documentation

  • Continued search for folks to help with documentation and testing, please reach out if you’re available.
  • Also continued search for folks with Go and/or Google Cloud Platform experience to help finish off items for Tide 1.0.0, please reach out if you’re available.
  • Discussion on current docs process and site, will investigate Gutenberg handbook documentation process to see if it would apply well for Tide
  • Looking for simple/easy way to push docs up to a site like wptide.org from a GitHub repo

Tide Dashicon

  • @cathibosco1: Marketing team let us know that Community-team handles the stickers and pins for WordCamps, sent request to #community-team channel to get Tide icon added to the collection
  • Long-running project to convert Dashicons to SVG not likely to wrap soon, so @jeffpaul to continue looking to get Dashicons update merged at beginning of WP 5.2 release cycle

Theme Review Team

  • @joyously joined the chat to follow discussion from #themereview meeting on possibly leveraging Tide with the Theme Sniffer
  • Tide could utilize TRT ruleset and audit the existing themes and then all new submissions/updates, could also integrate other theme-specific rulesets as desired
  • Existing themes could be audited in a couple of hours, but work would be needed to support the new ruleset and specific integration with TRT tools and processes
  • Will investigate this further after .ORG integration of PHP Compat data

Next meeting

The next meeting will take place on February 19, 2019 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

Tide Chat Summary: February 5th

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

1.0.0-beta2

  • @valendesigns reviewing wptide#173 and docs#19 to merge into 1.0.0-beta2
  • Otherwise looking to complete work on the failed tests in pkg before cutting the 1.0.0-beta2 release
  • If you have PRs you’re working on, let us know so we can try and get them into 1.0.0-beta2

Tide Dashicon

General announcements

  • We continue to search for folks with Go and/or Google Cloud Platform experience to help finish off items for Tide 1.0.0, so please reach out if you’re available… thanks!

Next meeting

The next meeting will take place on February 12, 2019 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

Tide Chat Summary: January 22nd

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

Tide Dashicon

General announcements

  • For those with availability and interest, please review and provide feedback to the Our Strengths and Challenges post on Make/Updates
  • We continue to search for folks with Golang and/or Google Cloud Platform experience to help finish off items for Tide 1.0.0, so please reach out if you’re available… thanks!
  • Note that @jeffpaul will be out-of-the-office and unable to run Tidechat on January 29, 2019 so we’ll take a one week break on Tidechat and come back to meet in February.

Next meeting

The next meeting will take place on February 5, 2019 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

Tide Chat Summary: January 15th

This post summarizes the Tide chat meeting from January 15th 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-beta2 timing

  • Proposal to merge wptide-PR#173 and docs-PR#19, then tag 1.0.0-beta2 with any other updates ready to land
  • Next step will be ensuring docs on wptide.org are accurate and there’s a straightforward way to manage them (ideally via a GitHub repo or /docs/ folder)
  • Docs need to be stable (see above) and the pkg-PR#17 needs tests fixed before 1.0.0-beta2 can be released

General announcements

  • Note that WPCS 2.0.0 was released this week
  • @cathibosco1 making progress on getting Tide dashicon available for use on Make/Tide and other marketing efforts

Next meeting

The next meeting will take place on January 22, 2019 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

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.

#summary, #tide-chat

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

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

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

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

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