Il giorno dom 17 feb 2019, 01:06 Sijie Guo <guosi...@gmail.com> ha scritto:

> > Other proposal is to setup
> > two meetings in a month, one is convenient for US
> > and other is convenient for Asia/Europe.
>
> I think that is a good proposal.
>
> We can do one at 8 am PST (Thursday) as before and one at 4 pm PST
> (Thursday).
> Let me know how do you guys think.
>
> Also I would suggest using zoom instead of google hangouts. Zoom has better
> meeting quality
> and be able to record meetings. If that's good to everyone, I can set one
> up.
>


Sounds good.
Can you update the original invitation and the website?

Enrico


> Thanks,
> Sijie
>
> On Tue, Feb 12, 2019 at 1:11 AM Enrico Olivelli <eolive...@gmail.com>
> wrote:
>
> > Good.
> >
> > So we can 'meet' next week at 8 a.m. PST.
> >
> >
> > The idea of weekly triage meeting works for me.
> >
> > Enrico
> >
> >
> >
> >
> > Il giorno lun 11 feb 2019, 08:29 Venkateswara Rao Jujjuri <
> > jujj...@gmail.com>
> > ha scritto:
> >
> > > Having one standard time is good. But there needs to be participation
> > too,
> > > otherwise it won't be successful.
> > > So lets find a good time that everyone can join. Other proposal is to
> > setup
> > > two meetings in a month, one is convenient for US
> > > and other is convenient for Asia/Europe. Personally I am fine to take
> > call
> > > in the night if it is not between 6-9PM PST.
> > > In the morning I am fine to take early calls even at 7 AM. I am just
> > > stating my availability, and the goal should be larger participation
> IMO.
> > >
> > > JV
> > >
> > > On Sun, Feb 10, 2019 at 9:14 PM Sijie Guo <guosi...@gmail.com> wrote:
> > >
> > > > I think it is very difficult to find a good time slot for US, Europe
> > and
> > > > Asia.
> > > >
> > > > I would propose followings:
> > > >
> > > > - keep the regular community meetings at 8AM PST and make sure all
> > > meeting
> > > > notes are updated and shared via mailing lists. Release manager
> should
> > > > drive the community meeting.
> > > > - additionally, if there are topics required ad-hoc calls, we can set
> > up
> > > > ad-hoc calls for the people required to be involved in the call. Also
> > > make
> > > > sure all meeting notes are shared to the community.
> > > > - lastly, Ivan and me have been doing bug triages for Pulsar. We
> might
> > be
> > > > starting doing same things for BookKeeper. It will be running weekly.
> > We
> > > > will document the bug triage process and share the meeting details.
> > > > Everyone are recommended to join the triage as well.
> > > >
> > > > Let me know your thoughts.
> > > >
> > > > - Sijie
> > > >
> > > > On Fri, Feb 8, 2019 at 4:10 PM Enrico Olivelli <eolive...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi folks,
> > > > > I think it is time to resume Community Meetings in 2019.
> > > > >
> > > > > Currently we are running the meeting at 8 AM PST, every two weeks.
> > > > >
> > > > > We can decide to change the date, if we find it uncomfortable.
> > > > >
> > > > > Jia and I were proposing to have a variable time for the call,
> > > > > depending on the needs or depending from the person who "calls"
> for a
> > > > > specific topic.
> > > > >
> > > > > I see that that time is not good for Jia and people from China.
> > > > >
> > > > > The goals of the community meetings are:
> > > > > - Let community members 'meet' each other
> > > > > - Discuss proposals
> > > > > - Discuss about problems
> > > > > - Share our projects/usages of BookKeeper/DL
> > > > >
> > > > > Every decision in ASF must be taken on ML, but we are humans and
> > > > > humans "like" to talk and I find this meetings an important way of
> > > > > "making community"
> > > > >
> > > > > Best regards
> > > > >
> > > > > Enrico
> > > > >
> > > >
> > >
> > >
> > > --
> > > Jvrao
> > > ---
> > > First they ignore you, then they laugh at you, then they fight you,
> then
> > > you win. - Mahatma Gandhi
> > >
> >
>

Reply via email to