Jeffrey Paul 2:30 pm on May 11, 2020
Tags: ,   

Tide Chat Agenda: May 12th

This is the agenda for the 2-hour Tide active working session on May 12, 2020 at 18:00 UTC:

  • 1.0.0
    • Review open PRs for issues blocking merging, commit to owners to resolve those, aiming to get to merge by end of the working session
    • Review open issues needing PRs, commit to owners to submit those PRs, aiming to get to code review and possibly merge by end of the working session

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

Timi Wahalahti 12:26 pm on May 11, 2020
Tags: ,   

X-post: WCEU Online 2020 Contributor Day: Submit your introduction videos, office hours times and introductory session needs this week

X-post from +make.wordpress.org/updates: WCEU Online 2020 Contributor Day: Submit your introduction videos, office hours times and introductory session needs this week

Jeffrey Paul 3:22 am on May 1, 2020
Tags: ,   

Tide Chat Summary: April 28th

This post summarizes the 30-minute Tide status update and open floor discussion from April 28th 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

  • We need help with testing, specifically why the services are not connecting to the API after the latest merges to upgrade WordPress
  • When starting the services locally they appear to authenticate with the API but when something is added to the queue it never is picked up for the audit by the service
  • Everything worked prior to upgrading WordPress
  • Alternatively it could be something is wrong with the connection to the local MonogDB instance that the queue is polling from, but this seems less likely
  • So if you’re able to pull down the lastest master branches and test locally to help triage that would be AMAZING. Help, please.

Next meeting

The next meeting, a 2-hour active working session, will take place on May 12, 2020 at 18: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:30 pm on April 27, 2020
Tags: ,   

Tide Chat Agenda: April 28th

This is the agenda for the 30-minute Tide status update and open floor discussion on April 28, 2020 at 18:00 UTC:

  • 1.0.0
    • Updates on progress of open PRs and issues in the milestone
  • Open floor

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

Timi Wahalahti 9:52 am on April 24, 2020
Tags: ,   

X-post: WCEU Online 2020 Contributor Day update: times, registration, platforms and team video introductions

X-post from +make.wordpress.org/updates: WCEU Online 2020 Contributor Day update: times, registration, platforms and team video introductions

Timi Wahalahti 7:22 am on April 15, 2020
Tags: ,   

X-post: WordCamp Europe 2020 Contributor Day Update

X-post from +make.wordpress.org/updates: WordCamp Europe 2020 Contributor Day Update

Jeffrey Paul 8:22 pm on April 1, 2020
Tags: ,   

Tide Chat Summary: March 31st

This post summarizes the 30-minute Tide status update and open floor discussion from March 31st 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

Next meeting

The next meeting, a 2-hour active working session, will take place on April 14, 2020 at 18: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 1:28 am on March 31, 2020
Tags: ,   

Tide Chat Agenda: March 31st

This is the agenda for the 30-minute Tide status update and open floor discussion on March 31, 2020 at 18:00 UTC:

  • 1.0.0
    • Updates on progress of open PRs and issues in the milestone
  • Open floor

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:00 pm on March 16, 2020
Tags: ,   

Tide Chat Agenda: March 17th

This is the agenda for the 2-hour Tide active working session on March 17, 2020 at 19:00 UTC:

  • 1.0.0
    • Review open PRs for issues blocking merging, commit to owners to resolve those, aiming to get to merge by end of the working session
    • Review open issues needing PRs, commit to owners to submit those PRs, aiming to get to code review and possibly merge by end of the working session

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:00 pm on March 4, 2020
Tags: ,   

Tide Chat Summary: March 3rd

This post summarizes the 30-minute Tide status update and open floor discussion from March 3rd 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

  • @kkoppenhaver making progress on caching issue, working on a proof of concept to ensure code fires when it’s put in the proper place, aiming for an update in our meeting in 2 weeks
  • @derekherman been sidetracked on other work, reviewed PR for upgrading WP and things are working just need to merge and deploy to GCP, aiming for resolving that by our next meeting
  • @pierlo been sidetracked on work, will attempt to look into Redis caching issue by our next meeting
  • @jeffpaul digging into docs site, opened three issues recently with docs#41 likely being most important to consider as it relates to bumping docpress versions

Next meeting

The next meeting, a 2-hour active working session, will take place on March 17, 2020 at 19: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