+1 on these suggestions.

For the Hudi syncs, we used Google Meet, but some attendees from China were
unable to join correctly. Then we switched to Zoom. We can give Teams a
shot, go from there.

On Timing - I can make Mar 11 work. I have found PST 8AM ish or so,
friendly to most time zones. Any thoughts?

Ashvin - I can help with the site changes to make a new community sync
page. lmk!

Thanks
Vinoth

On Mon, Mar 4, 2024 at 10:53 AM Ashvin A <ash...@apache.org> wrote:

> Hi JB,
> I should be able to create an "open" Teams link for this meeting instance.
> I am more familiar with Teams. Interested contributors can connect through
> the browser. As the meeting coordinator, I will be responsible for
> admitting the attendees. Teams will generate a recording and a transcript,
> which I can share / upload afterwards. If needed, we can switch to other
> platforms for future meetings.
>
> Hi Stamatis,
> Thanks for the confirmation for Mar 11. I will wait for a day for others to
> revert back with a preferred time before creating the invite.
>
> Everyone,
> Please respond if you have any suggestions for the structure of the meeting
> and the agenda.
>
> Best,
> Ashvin
>
>
> On Mon, Mar 4, 2024 at 4:29 AM Stamatis Zampetakis <zabe...@gmail.com>
> wrote:
>
> > Hello,
> >
> > I am mostly available between 9:00 and 17:00 on March 11 CET. Outside
> > this interval chances for conflicts with personal & professional life
> > are pretty high so not sure if I will be able to join.
> >
> > Best,
> > Stamatis
> >
> > On Sat, Mar 2, 2024 at 8:33 AM Jean-Baptiste Onofré <j...@nanthrax.net>
> > wrote:
> > >
> > > Hi Ashvin
> > >
> > > In other projects (like Arrow or Iceberg for instance), we use Google
> > > Meet or Zoom.
> > > Any platform is OK as soon as it's "open enough".
> > >
> > > I propose to share the calendar invite on the mailing list and on the
> > > website (similar to
> > > https://iceberg.apache.org/community/#iceberg-community-events or
> > > https://arrow.apache.org/community/#Meetings).
> > >
> > > March 11 is OK for me.
> > >
> > > Regards
> > > JB
> > >
> > > On Fri, Mar 1, 2024 at 10:36 PM Ashvin A <ash...@apache.org> wrote:
> > > >
> > > > Hi Vinoth, JB,
> > > >
> > > >
> > > > +1 to a monthly sync meeting and sharing notes on the mailing lists.
> > > >
> > > > I believe it would be incredibly valuable, especially in the initial
> > days
> > > > of the project, to help kickstart the project and answer any
> questions
> > > > related to the project and the process which is new to some of us.
> > > >
> > > >
> > > > 1. Is there a preferred platform for hosting the meeting? For e.g. I
> > could
> > > > create a Microsoft Teams invite which anyone can join and later share
> > the
> > > > recording and notes.
> > > >
> > > > 2. Shall we target the week of Mar-11 for our first meeting?
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Ashvin
> > > >
> > > >
> > > >
> > > > On Thu, Feb 29, 2024 at 5:22 AM Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > > > wrote:
> > > >
> > > > > Hi Vinoth
> > > > >
> > > > > I agree as soon as:
> > > > > 1. The agenda is shared on the mailing list before the meeting
> > > > > 2. Meeting notes are shared on the mailing list soon after the
> > meeting
> > > > >
> > > > > In order to build a vibrant community, we have to include anyone. A
> > > > > meeting is not always convenient for everyone because it's not on
> the
> > > > > right timezone, some people are not comfortable in English at a
> > > > > meeting, etc.
> > > > >
> > > > > So, monthly meetings are fine as soon as we have notes shared on
> the
> > > > > mailing list. As we say at Apache: "if it doesn't happen on the
> > > > > mailing list, it never happened".
> > > > >
> > > > > Thanks,
> > > > > Regards
> > > > > JB
> > > > >
> > > > > On Thu, Feb 29, 2024 at 12:59 AM Vinoth Chandar <vin...@apache.org
> >
> > wrote:
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > How does everyone feel about a monthly sync to discuss goals,
> > plans and
> > > > > > roadmaps
> > > > > >
> > > > > > Thanks
> > > > > > Vinoth
> > > > >
> >
>

Reply via email to