X-post: WCEU 2020 – Leave no Contributor Behind
X-comment from +make.wordpress.org/updates: Comment on WCEU 2020 – Leave no Contributor Behind
Tide Chat Summary: January 21st
This post summarizes the 2-hour Tide active working session from January 21st 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
- @derekherman to test and merge wptide#198
- @pierlo to review wporg-tide-api#6
- Research notes added to wptide#178, tagged @kkoppenhaver on that in hopes he can help triage
- @derekherman to review wptide#199, @pierlo to continue iterating and wrap up work on it as well
- Discussion on docs site and that setup is not ideal, but it’s a low priority to resolve those and will let it ride until after we ship Tide v1.0.0
- @jeffpaul reviewed docs#36, added update to related markdown file, otherwise looks good to merge
- @jeffpaul reviewed docs#37, but not certain we’re following WPCS for docs files so that PR may be dismissable
Next meeting
Schedule conflicts with the meeting time have led us to move the meeting time an hour earlier, so please update any local calendar events you have to account for the new meeting time of 19:00 UTC on Tuesdays.
The next meeting, a 30-minute update/open floor session, will take place on Feburary 4, 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.
Tide Chat Agenda: January 21st
This is the agenda for the 2-hour Tide active working session on January 21, 2020 at 20: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!
Tide Chat Summary: January 7th
This post summarizes the 30-minute Tide status update and open floor discussion from January 7th 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
- wp-tide-api#30 and wporg-tide-api#7 merged, only wptide#198 remains for @derekherman to review, merge, and deploy for the update to WP 5.3.1
- @derekherman to review wporg-tide-api#6 to ensure it handles wptide#186
- Final issue to be resolved in 1.0.0 milestone remains as wptide#178
Next meeting
The next meeting, a 2-hour active working session, will take place on January 21, 2020 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.
Tide Chat Agenda: January 7th
This is the agenda for the 30-minute Tide status update and open floor discussion on January 7, 2020 at 20: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!
Tide Chat Summary: December 17th
This post summarizes the 2-hour Tide active working session from December 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.
1.0.0
- Closed wptide#177 in favor of wptide#198, current plan to update to WP 5.3.1 via three PRs across the Tide stack and then a GCP deploy
- wporg-tide-api#6 not yet ready to merge
- Issue with Travis builds unable to connect to the MySQL database resolved by changing from
xenialback totrustyon Travis - Merged wporg-tide-api#7 to close wporg-tide-api#4 and merged wp-tide-api#30 to close wp-tide-api#29
- @derekherman to review the cache invalidation PR, once that’s merged we’ll deploy to GCP
Next meeting
The next meeting, a 30-minute update/open floor session, will take place on January 7, 2020 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.
Tide Chat Agenda: December 17th
This is the agenda for the 2-hour Tide active working session on December 17, 2019 at 20: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!
Tide Chat Summary: December 3rd
This post summarizes the 30-minute Tide status update and open floor discussion from December 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
- @derekherman been sidelined by work travel and holidays, will work to merge in various PRs (wptide#198, ) and deploy to GCP
- Discussion continues on wptide#178 on whether its an update to the keys in the env file or if a code change is needed
- Will reasses issues remaining in our next meeting after @derekherman merges existing PRs
Next meeting
The next meeting, a 2-hour active working session, will take place on December 17, 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.
Tide Chat Agenda: December 3rd
This is the agenda for the 30-minute Tide status update and open floor discussion on December 3, 2019 at 20: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!