zoom also lets you assign alternative hosts. > On Jun 10, 2020, at 12:26 AM, Elek, Marton <[email protected]> wrote: > > > Both work for me. The current one is here: > > Mukul suggested to use the same as on Monday (for the sake of the simplicity) > but It seems that I am the host in the Zoom. > > Would be better if you (or somebody else) can be the host on Friday (and do > the recording + the meeting minutes). > > I think only the hosts can start the recordings... > > I will publish the existing Zoom, if no objection. > > Marton > > On 6/8/20 7:18 PM, Xiaoyu Yao wrote: >> Both work for me. The current one is here: >> https://cloudera.zoom.us/j/5780476042 >> <https://www.google.com/url?q=https%3A%2F%2Fcloudera.zoom.us%2Fj%2F5780476042> >> Thanks, >> Xiaoyu >> On Mon, Jun 8, 2020 at 7:02 AM Elek, Marton <[email protected]> wrote: >>> Sounds good to me. Is there any dedicated Zoom link, which can be shared >>> or shall we use the one from Monday? >>> >>> Thanks, >>> Marton >>> >>> >>> On 6/5/20 4:25 PM, Mukul Kumar Singh wrote: >>>> +1. >>>> >>>> Thanks, >>>> >>>> Mukul >>>> >>>> On 05/06/20 11:56 am, Jitendra Pandey wrote: >>>>>> Currently there is a meeting on Friday 12:15PM Beijing / 9:45AM India, >>>>>> Thursday 9:15 PM PST between Tencent and Cloudera >>>>> >>>>> +1 to merge the community meeting with this one, as suggested by Sammi. >>>>> >>>>> On Thu, Jun 4, 2020 at 7:58 PM Sammi Chen <[email protected] >>>>> <mailto:[email protected]>> wrote: >>>>> >>>>> Hi Marton, >>>>> >>>>> Thanks for initiate the survery and collect the result. >>>>> >>>>> Currently there is a meeting on Friday 12:15PM Beijing / 9:45AM >>>>> India, >>>>> Thursday 9:15 PM PST between Tencent and Cloudera. If the >>>>> community is >>>>> going to start a new sync meeting at the second half of the week, >>>>> I'd >>>>> like to propose to merge these two meetings into one. >>>>> >>>>> @Xiaoyu Yao <[email protected] <mailto:[email protected]>> @Mukul >>>>> Kumar Singh >>>>> <[email protected] <mailto:[email protected]>> >>>>> Would like to hear your thoughts on this. >>>>> >>>>> Thanks, >>>>> Sammi >>>>> >>>>> >>>>> On Thu, Jun 4, 2020 at 6:45 PM Elek, Marton <[email protected] >>>>> <mailto:[email protected]>> wrote: >>>>> >>>>> > >>>>> > A few weeks ago we started a new Survey to make our Community >>>>> Sync more >>>>> > inclusive (for more time zones). >>>>> > >>>>> > Thank you for all the answers (22), I think it helps a lot to >>>>> make our >>>>> > Sync more effective and more inclusive. >>>>> > >>>>> > The raw results are available from here: >>>>> > >>>>> > https://home.apache.org/~elek/ozone-survey-results.csv >>>>> > >>>>> > But in this mail I will give a quick summary with the possible >>>>> action >>>>> > items. >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > 1. QUESTION: Do you read the meeting minutes from the ozone-dev >>>>> mailing >>>>> > list? Do they help for you? >>>>> > >>>>> > ANSWERS: >>>>> > >>>>> > The answer was a strong yes. (82%). >>>>> > >>>>> > ACTION ITEMS: >>>>> > >>>>> > We should continue to write meeting minutes and publish it on the >>>>> > mailing list. >>>>> > >>>>> > As I am not always available (Summer is coming) I will ask >>>>> volunteers to >>>>> > write it when I can't do it. >>>>> > >>>>> > Based on the suggestion below, I will start to archive the >>>>> minutes on >>>>> > the wiki (as Anu did). But I prefer to include the full text in >>> the >>>>> > mailing lists too (as it's also archived, with different method. >>>>> > >>>>> > NOTABLE COMMENTS: >>>>> > >>>>> > * Maybe we should notify the meeting though multi-way, >>> mail-list, >>>>> > slack, wechat, and any other way. >>>>> > >>>>> > * It would be really great if you could summarize weekly >>>>> meeting notes >>>>> > in wiki like >>>>> > >>>>> >>>>> >>> https://cwiki.apache.org/confluence/display/HADOOP/2020-01-07+Meeting+notes >>>>> >>>>> > . >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > 2. QUESTION: Do you prefer recordings of the meetings? >>>>> > >>>>> > ANSWERS: >>>>> > >>>>> > 38 % : yes >>>>> > 33 % : yes, with limited retention >>>>> > >>>>> > ACTION ITEMS: >>>>> > >>>>> > As it's 71 % for recording, I think we should start to record >>>>> it, share >>>>> > it, but we can delete the recordings after 1 month >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > 3. QUESTION: What is your preferred scheduling scheme? >>>>> > >>>>> > ANSWERS: >>>>> > >>>>> > 41 %: One call a week, same time >>>>> > 36 %: One call a week / alternating times >>>>> > >>>>> > ACTION ITEMS: >>>>> > >>>>> > Here, I don't know what should we do. Both can work, but we >>>>> agreed that >>>>> > the existing one should be kept. There is no good decision here >>>>> as far >>>>> > as I see. >>>>> > >>>>> > I will propose to start a new meeting at EMEA/APAC friendly time >>>>> which >>>>> > can work for PST (PST late night but before midnight). >>>>> > >>>>> > We will see how does it work and can transform some of the >>>>> events to >>>>> > more specific design discussion. >>>>> > >>>>> > >>>>> > NOTABLE COMMENTS: >>>>> > >>>>> > * its better to talk English slowly and clearly, for some body >>>>> don't >>>>> > good at the English with accent. Its better to have translator. >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > 4. QUESTIONS What is your preferred workday for the call >>>>> > >>>>> > ANSWERS: beginning of the week is better (Monday 72% ---> Friday >>>>> 18%) >>>>> > >>>>> > >>>>> > 5. QUESTION: Which time is best for you (in your local time, >>>>> defined in >>>>> > the previous question) >>>>> > >>>>> > >>>>> > ANSWERS: >>>>> > >>>>> > I analyzed it with google spreadsheet, but but time slots are the >>>>> > following: >>>>> > >>>>> > A) existing slot >>>>> > >>>>> > GMT/Belfast: 16 >>>>> > Budapest (summer): 18 >>>>> > Beijing: 24 >>>>> > New York (summer): 12 >>>>> > Seattle/California (summer): 9 >>>>> > India: 21:30 >>>>> > >>>>> > feedback categories: >>>>> > >>>>> > Good + Acceptable: 11 (8 + 3) >>>>> > Impossible: 7 >>>>> > >>>>> > B) additional slot >>>>> > >>>>> > GMT/Belfast: 8:30 >>>>> > Budapest (summer): 6:30 >>>>> > Beijing: 12:30 >>>>> > New York (summer): 0:30 >>>>> > Seattle/California (summer): 21:30 >>>>> > India: 10:00 >>>>> > >>>>> > >>>>> > Good + Acceptable: 12 (9 + 3) >>>>> > Impossible: 6 >>>>> > >>>>> > (Note, It's a 2-2:30 hours slot the time can be moved, but later >>> is >>>>> > harder for Europe (6 am), later is harder for Pacific (22 = 10pm) >>>>> > >>>>> > >>>>> > ACTION ITEM: >>>>> > >>>>> > I propose to start a new Sync at 8:30 am GMT. Based on the vote, >>>>> > Wednesday seems to be a good choice, but as far as I know there >>>>> is an >>>>> > unofficial sync between a few contributors at Friday which also >>>>> can be >>>>> > moved later. >>>>> > >>>>> > I think we can start it weekly (harder to switch to alternating >>>>> times >>>>> > IMHO) but with more focused: >>>>> > >>>>> > * having an agenda in advance! >>>>> > * With agenda we can spend more time on design discussions >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > 6. ADDITIONAL FEEDBACK: >>>>> > >>>>> > >>>>> > * A way to propose topics ahead of time, or to sign up for a >>>>> time slot >>>>> > to ask for inputs on a topic >>>>> > >>>>> > * As we have only hundred contributor now, we should do >>>>> something for >>>>> > getting more contributor, for example, more talk, more meetup >>>>> online or >>>>> > offline, friendly to contribute, new contributor guide, more >>>>> concept >>>>> > documents, do not cherry pick commits from a contributor...its >>>>> honor for >>>>> > them about the number of commit. As community over code, we should >>>>> > encourage contributor to do more contribute. Each release, >>>>> thanks the >>>>> > contributor of contribute in current release. Mostly important, >>>>> let more >>>>> > company join ozone development. So, paste the sides, youtube link, >>>>> > blogs, events into homepage of Ozone. Hope our community be more >>>>> strong. >>>>> > >>>>> > * We could send out agenda before the weekly sync up to the >>>>> community. >>>>> > >>>>> > * It would be great if there would be even a vague agenda for >>>>> this >>>>> > calls. Just only with the things we already know the last >>>>> workday before >>>>> > the meeting... >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > Please note, all of them are filtered by my interpretation. >>>>> Please add >>>>> > your opinion if it's different. >>>>> > >>>>> > Thanks a lot, >>>>> > Marton >>>>> > >>>>> > >>>>> >>> --------------------------------------------------------------------- >>>>> > To unsubscribe, e-mail: [email protected] >>>>> <mailto:[email protected]> >>>>> > For additional commands, e-mail: >>>>> [email protected] >>>>> <mailto:[email protected]> >>>>> > >>>>> > >>>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
