+1 for sync meeting for iceberg rust.

These meetings will not be recorded.


I think we have meeting records for catalog meetings and community sync, so
we should also record this?

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?

On Wed, Oct 9, 2024 at 10:50 PM Kevin Liu <kevin.jq....@gmail.com> wrote:

> +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/
>>
>

Reply via email to