Re the possibility of moving this meeting an hour earlier: some of the
usual attendees have other conflicts at that time. For now, we plan to
keep the current time. But I think it would be worthwhile to gather
more information about whether the current meeting time is an obstacle
for others, and what other times might work better. I will look into
creating a survey to collect this information.

Ian

On Wed, Feb 14, 2024 at 11:13 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote:
>
> Hi Ian,
>
> Thanks ! I will join the Iceberg Community Meeting today as I have some WIP.
>
> Regards
> JB
>
> On Wed, Feb 14, 2024 at 5:07 PM Ian Cook <ianmc...@apache.org> wrote:
> >
> > Thanks JB. I'll start by asking in today's meeting whether the usual
> > attendees are available in the hour preceding the current meeting
> > time.
> >
> > Ian
> >
> > On Wed, Feb 14, 2024 at 4:45 AM Jean-Baptiste Onofré <j...@nanthrax.net> 
> > wrote:
> > >
> > > Hi Ian
> > >
> > > Thanks for sharing.
> > >
> > > By the way, we have a Community Meeting time conflict between Apache
> > > Iceberg and Apache Arrow.
> > >
> > > Do you think it would be possible (in the future) to have the Arrow
> > > Community Meeting one hour earlier or later ?
> > > If not possible, not a problem, I will alternatively attend the Arrow
> > > Community Meeting and the Iceberg Community Meeting.
> > >
> > > Thanks !
> > > Regards
> > > JB
> > >
> > > On Wed, Feb 14, 2024 at 2:39 AM Ian Cook <ianmc...@apache.org> wrote:
> > > >
> > > > Our next biweekly Arrow community meeting is tomorrow at 17:00 UTC / 
> > > > 12:00 EST.
> > > >
> > > > Zoom meeting URL:
> > > > https://zoom.us/j/87649033008?pwd=SitsRHluQStlREM0TjJVYkRibVZsUT09
> > > > Meeting ID: 876 4903 3008
> > > > Passcode: 958092
> > > >
> > > > Meeting notes will be captured in this Google Doc:
> > > > https://docs.google.com/document/d/1xrji8fc6_24TVmKiHJB4ECX1Zy2sy2eRbBjpVJMnPmk/
> > > > If you plan to attend this meeting, you are welcome to edit the
> > > > document to add the topics that you would like to discuss.
> > > >
> > > > Thanks,
> > > > Ian

Reply via email to