Seems that there is no objection about this meeting, but we have different options about timing. Should we start a poll for timing?
On Fri, Oct 11, 2024 at 11:27 PM Sung Yun <sun...@apache.org> wrote: > Thank you for starting this thread Xuanwo, I'm +1 for a Iceberg Rust > meeting. > > Regarding the meeting time, I believe the Iceberg Catalog Community sync > happens two consecutive weeks, at the same time as the Iceberg community > sync, when there isn't the tri-weekly Iceberg meeting. > > For example, if the Iceberg Sync Meeting is scheduled for Thursday, > October 24, 2024, from 00:00 to 01:00 GMT+8, there is a Catalog Community > Sync Meeting scheduled for Thursday, October 17, 2024, from 00:00 to 01:00 > GMT+8 and for Thursday, October 9, 2024, from 00:00 to 01:00 GMT+8. > > Another option to consider to avoid conflict is to host the Iceberg Rust > sync on a different day of the week. For example, PyIceberg sync meets on > the last Tuesday of each month. > > Regardless, I'm looking forward to attending the meeting and connecting > with the community! > > Sung > > On 2024/10/11 13:31:59 Xuanwo wrote: > > > For reference, here's the doc we've been using for the pyiceberg sync > https://docs.google.com/document/d/1oMKodaZJrOJjPfc8PDVAoTdl02eGQKHlhwuggiw7s9U > > > > Thank you, Kevin. This document is excellent, and I'll use it as a > template. > > > > > I think we have meeting records for catalog meetings and community > sync, so we should also record this? > > > > For the record, I'm referring to the video recording, which I don't have > a setup for like the Iceberg Sync Meeting does. I plan to maintain a Google > document similar to the Iceberg Sync Meeting and Iceberg Python Sync > Meetings. > > > > > For time, I would suggest moving it one hour ahead, e.g. 23:00 to > 00:00 GTM+8, so that it's a little more friendly to people in asia? > > > > This time looks good to me. > > > > > As for the time, I think we don't need to use the same time as Iceberg > Sync Meeting, and can choose a better time according to the Iceberg Rust > developers? (Perhaps we can have a poll) > > > > Hi, xxchan. > > > > I propose a time close to the Iceberg Sync Meeting to ensure most > community members can join. I'm open to other options. Would you like to > suggest one? > > > > On Fri, Oct 11, 2024, at 15:56, xxchan wrote: > > > Thank Xuanwo for raising this. I'm also interested and excited to > catch up and better participate in the community. > > > > > > As for the time, I think we don't need to use the same time as Iceberg > Sync Meeting, and can choose a better time according to the Iceberg Rust > developers? (Perhaps we can have a poll) > > > > > > On Fri, Oct 11, 2024 at 1:41 PM Christian Thiel < > christ...@hansetag.com.invalid> wrote: > > >> +1 for rust sync. Thanks for the proposal Xuanwo. There are many open > topics and alignment in the sync can help to clarify scopes and > dependencies to move forward with iceberg-rust even faster. > > >> Time is good for me. > > >> > > >> > > >> *Von:* Kevin Liu <kevin.jq....@gmail.com> > > >> *Gesendet:* Wednesday, October 9, 2024 4:47:57 PM > > >> *An:* dev@iceberg.apache.org <dev@iceberg.apache.org> > > >> *Betreff:* Re: [DISCUSS] Iceberg Rust Sync Meeting > > >> > > >> +1 on sync meeting for iceberg rust. I want to get involved and catch > up on the recent developments. For reference, here's the doc we've been > using for the pyiceberg sync > https://docs.google.com/document/d/1oMKodaZJrOJjPfc8PDVAoTdl02eGQKHlhwuggiw7s9U > > >> > > >> Best, > > >> Kevin > > >> > > >> On Wed, Oct 9, 2024 at 5:30 AM Xuanwo <xua...@apache.org> wrote: > > >>> Hi, > > >>> > > >>> I'm starting this thread to explore the idea of hosting an Iceberg > Rust Sync Meeting. In this meeting, we will discuss recent major changes, > pending PR reviews, and features in development. It will offer a space for > Iceberg Rust contributors to connect and become familiar with each other, > helping us identify and remove contribution barriers to the best of our > ability. > > >>> > > >>> Details about this meeeting: > > >>> > > >>> I suggest hosting our meeting at the same time of day, but one week > earlier than the Iceberg Sync Meeting. For example, if the Iceberg Sync > Meeting is scheduled for Thursday, October 24, 2024, from 00:00 to 01:00 > GMT+8, the Iceberg Rust Sync Meeting would take place one week before, on > Thursday, October 17, 2024, from 00:00 to 01:00 GMT+8. > > >>> > > >>> I also suggest using the same Google Meet code (if possible) so we > don't get confused. > > >>> > > >>> These meetings will not be recorded, but I will take notes in a > Google Doc, similar to what we do in the Iceberg Sync Meeting. > > >>> > > >>> What are your thoughts? I'm open to other options as well. > > >>> > > >>> Xuanwo > > >>> > > >>> https://xuanwo.io/ > > > > Xuanwo > > > > https://xuanwo.io/ >
