Dear Ozone Devs,
Please find the US time zone community sync notes below.
Agenda Topics Discussed:
1.
*Release planning: 1.4.1 release? I think we have some snapshot
issues(any other critical?) that did not land in 1.4.0.* *Discussion
Notes:*
1.
Snapshot issues
2.
Zero Copy changes
3.
Porting RM manager guide from Wiki to website and will be up for
review.
4.
We may need Ratis' release.
5.
Is it appropriate to include Zero Copy changes in . release.
6.
Please add your target version if you would like to include changes
in the release.
1.
*Any thoughts on how we can get the users question and answers from
slack channels to mailing lists for better indexing (for search).*
*Discussion
Notes:*
1.
Ritesh will be sending an email with the proposal to start using github
discussions / mailing lists. Slack can be used for any immediate help and
pinging some to help in review etc.
1.
*Community meeting rotation* *Discussion Notes:*
1.
A topic to discuss how we rotate
1.
Get signups who would be interested to run meeting, then just follow
based on list order in wiki
2.
Identify next week’s community sync champion
1.
*New contributors PR queue.* *Discussion Notes:*
We quickly looked at the PR queue. And discussed about
dependabot pr.
Attila pinging specific folks for review help.
1.
*Any new design proposals ?*
* Discussion Notes:*
Ethan presented a Container reconciliation proposal.
There was some good Q&A.
We would encourage everyone to participate and make it more interactive
than slide presentations.
Thank you Ethan Rose <er...@cloudera.com> and Ritesh Shukla
<rit...@cloudera.com>
1.
*Docs update?* *Discussion Notes:*
Did not get time to discuss.
Another thought shared by Ritesh regarding meeting summaries:
One quick thought was to look at APAC sync summaries and bring up if there
are any interesting notes there.
*Plan of Actions from the meeting:*1. Ritesh to start a discussion thread
about #2 for moving technical discussions from slack to github discussions.
2. Duog to start a discussion thread about 1.4.1 release (#1)
3. Ethan to start a github discussion for next community sync champion ( #3)
4. Ethan to share PR with Container reconciliation design.
Regards,
Uma
