Jeffrey Paul 9:00 pm on February 18, 2019
Tags: ,   

Tide Chat Agenda: February 19th

This is the agenda for the weekly Tide meeting on February 19, 2019 at 20:00 UTC:

  • 1.0.0-beta2
  • Tide Dashicon
  • 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 5:11 pm on February 13, 2019
Tags: ,   

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

Jeffrey Paul 4:59 pm on February 12, 2019
Tags: ,   

Tide Chat Agenda: February 12th

This is the agenda for the weekly Tide meeting on February 12, 2019 at 20:00 UTC:

  • 1.0.0-beta2
  • Tide Dashicon
  • 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:31 pm on February 6, 2019
Tags: ,   

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

Jeffrey Paul 2:52 am on February 5, 2019
Tags: ,   

Tide Chat Agenda: February 5th

This is the agenda for the weekly Tide meeting on February 5, 2019 at 20:00 UTC:

  • 1.0.0-beta2
  • Tide Dashicon
  • 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 3:00 pm on January 28, 2019
Tags:   

CANCELLED – Tide Chat: January 29th

This week’s Tide meeting is cancelled due to several folks being out-of-the-office. If you have something to add to next week’s agenda, then please leave a comment below. See you next week!

#tide-chat

Jeffrey Paul 5:12 pm on January 23, 2019
Tags: ,   

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

Jeffrey Paul 3:49 pm on January 22, 2019
Tags: make.wordpress.org/updates, p2-xpost   

X-post: Our Strengths and Challenges

X-comment from +make.wordpress.org/updates: Comment on Our Strengths and Challenges

Jeffrey Paul 7:03 pm on January 18, 2019
Tags: ,   

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

Jeffrey Paul 9:00 pm on December 17, 2018
Tags: , ,   

Tide Chat, Office Hours, Holiday Schedule

Note that we’ll have Tide office hours this week (Tuesday, December 18th), then off for two weeks for the holidays, then back with office hours (Tuesday, January 8th), and hopefully back to a full Tidechat schedule by Tuesday, January 15th.

We will be mainly focused on GitHub issues in the 1.0.0-beta2 and 1.0.0 milestones, but otherwise will be around for 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, #bugscrub, #tide-chat