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 >
