From common-dev-return-102349-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Jun 14 23:03:26 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id BAB4718062F for ; Sat, 15 Jun 2019 01:03:25 +0200 (CEST) Received: (qmail 69674 invoked by uid 500); 14 Jun 2019 23:03:23 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 69612 invoked by uid 99); 14 Jun 2019 23:03:23 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jun 2019 23:03:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 9428EC65F5; Fri, 14 Jun 2019 23:03:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.811 X-Spam-Level: * X-Spam-Status: No, score=1.811 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, GB_FROM_NAME_FREEMAIL=0.01, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 3xdec0rFyKbJ; Fri, 14 Jun 2019 23:03:20 +0000 (UTC) Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com [209.85.208.171]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 0774F5F52B; Fri, 14 Jun 2019 23:03:20 +0000 (UTC) Received: by mail-lj1-f171.google.com with SMTP id s21so3910906lji.8; Fri, 14 Jun 2019 16:03:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2RtIWzwiolCXHup6tSXNrcY5loMJW6+ICx6w5WUSewA=; b=o5b4OHHBNhegaxITMr1nG1n2CO06X/b4vw4bSL1SI4KxJ/mMN0Rc+7REfnYYNQXoog X/wDfmABgN1Yv7cEjUb7NBl2JisxSo5PHTyIGcY97bb8K7MGrE+tzDgcr6hPThpVVb7p 8hg5n0O3FHYDIfyNYTsXbcdb5yeAngx0cdkbG6Z/eofuwRYsSK+SP3hX+7dIV+y5Mvvx hbJBmWQVAQnbZ3CPGKtvPDhpet1cH70u1wZzVgPwR2NLbEjLT/7/Md07i8BJNioUSNFL MmaKMfOGJl4kX/3cCq0qCODCMLUz+nCEL24jXl1aojojk6yMDc0X7CiSKUZmibzKrcZ0 9CUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2RtIWzwiolCXHup6tSXNrcY5loMJW6+ICx6w5WUSewA=; b=A0PkABXwOvIeUDtiWBEiIRse1Vz8HhqI2zWTlP6hp94+Y0bMv+ZMV+QuuhYI+4+TeC jz6WzdsHhdajDvlgf8Gt33XUXgbwk3/sMFXhTTryoP0od8S/Jb+KardMrMPKsPtDA/0P Mj+5Ko48f1dHRjuBA3SSqvi8rpU+FNk98VcG6mSMKZlH140XTHZP2qp+DiFi/iEh8F2f ieqyXUBL6p8bEOvyQL376J1MXZAz5deL6R3VtoTJxJn4nYsvAixN5d7l0QeO/A8Ut96x TwzyPrYEvS0zBo0xy7SIhezPJtT1JWZsaoFuBH3bd9SDow6iI7mnaI0FCzOqn4Ws4Hsy S52g== X-Gm-Message-State: APjAAAXBzvchuE81fh9gP0eQFYwhSvrXgBTEL04roPZu6y6iYFPEiLvQ ZKAh1JvxEBJptzyMvxjg28TTIhElhfUvkrvzZt0= X-Google-Smtp-Source: APXvYqx7JSf69iQp7k5RwwzkaFY0153SFpYdhcgztLuA1fQ6vlpRi3qhDB+3+mOw/xEStlzccn2Krwj3xykEiIPJDa8= X-Received: by 2002:a2e:6e0e:: with SMTP id j14mr5109494ljc.85.1560553398500; Fri, 14 Jun 2019 16:03:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Wangda Tan Date: Fri, 14 Jun 2019 16:02:51 -0700 Message-ID: Subject: Re: [DISCUSS] A unified and open Hadoop community sync up schedule? To: Anu Engineer Cc: Yufei Gu , yarn-dev@hadoop.apache.org, Hdfs-dev , Hadoop Common , mapreduce-dev@hadoop.apache.org, submarine-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary="000000000000f88455058b50a6ca" --000000000000f88455058b50a6ca Content-Type: text/plain; charset="UTF-8" And please let me know if you can help with coordinate logistics stuff, cross-checking, etc. Let's spend some time next week to get it finalized. Thanks, Wangda On Fri, Jun 14, 2019 at 4:00 PM Wangda Tan wrote: > Hi Folks, > > Yufei: Agree with all your opinions. > > Anu: it might be more efficient to use Google doc to track meeting minutes > and we can put them together. > > I just put the proposal to > https://calendar.google.com/calendar/b/3?cid=aGFkb29wLmNvbW11bml0eS5zeW5jLnVwQGdtYWlsLmNvbQ, > you can check if the proposal time works or not. If you agree, we can go > ahead to add meeting link, google doc, etc. > > If you want to have edit permissions, please drop a private email to me so > I will add you. > > We still need more hosts, in each track, ideally we should have at least 3 > hosts per track just like HDFS blocks :), please volunteer, so we can have > enough members to run the meeting. > > Let's shoot by end of the next week, let's get all logistics done and > starting community sync up series from the week of Jun 25th. > > Thanks, > Wangda > > Thanks, > Wangda > > > > On Tue, Jun 11, 2019 at 10:23 AM Anu Engineer > wrote: > >> For Ozone, we have started using the Wiki itself as the agenda and after >> the meeting is over, we convert it into the meeting notes. >> Here is an example, the project owner can edit and maintain it, it is >> like 10 mins work - and allows anyone to add stuff into the agenda too. >> >> >> https://cwiki.apache.org/confluence/display/HADOOP/2019-06-10+Meeting+notes >> >> --Anu >> >> On Tue, Jun 11, 2019 at 10:20 AM Yufei Gu wrote: >> >>> +1 for this idea. Thanks Wangda for bringing this up. >>> >>> Some comments to share: >>> >>> - Agenda needed to be posted ahead of meeting and welcome any >>> interested >>> party to contribute to topics. >>> - We should encourage more people to attend. That's whole point of the >>> meeting. >>> - Hopefully, this can mitigate the situation that some patches are >>> waiting for review for ever, which turns away new contributors. >>> - 30m per session sounds a little bit short, we can try it out and see >>> if extension is needed. >>> >>> Best, >>> >>> Yufei >>> >>> `This is not a contribution` >>> >>> >>> On Fri, Jun 7, 2019 at 4:39 PM Wangda Tan wrote: >>> >>> > Hi Hadoop-devs, >>> > >>> > Previous we have regular YARN community sync up (1 hr, biweekly, but >>> not >>> > open to public). Recently because of changes in our schedules, Less >>> folks >>> > showed up in the sync up for the last several months. >>> > >>> > I saw the K8s community did a pretty good job to run their sig >>> meetings, >>> > there's regular meetings for different topics, notes, agenda, etc. >>> Such as >>> > >>> > >>> https://docs.google.com/document/d/13mwye7nvrmV11q9_Eg77z-1w3X7Q1GTbslpml4J7F3A/edit >>> > >>> > >>> > For Hadoop community, there are less such regular meetings open to the >>> > public except for Ozone project and offline meetups or >>> Bird-of-Features in >>> > Hadoop/DataWorks Summit. Recently we have a few folks joined DataWorks >>> > Summit at Washington DC and Barcelona, and lots (50+) of folks join the >>> > Ozone/Hadoop/YARN BoF, ask (good) questions and roadmaps. I think it is >>> > important to open such conversations to the public and let more >>> > folk/companies join. >>> > >>> > Discussed a small group of community members and wrote a short proposal >>> > about the form, time and topic of the community sync up, thanks for >>> > everybody who have contributed to the proposal! Please feel free to add >>> > your thoughts to the Proposal Google doc >>> > < >>> > >>> https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# >>> > > >>> > . >>> > >>> > Especially for the following parts: >>> > - If you have interests to run any of the community sync-ups, please >>> put >>> > your name to the table inside the proposal. We need more volunteers to >>> help >>> > run the sync-ups in different timezones. >>> > - Please add suggestions to the time, frequency and themes and feel >>> free to >>> > share your thoughts if we should do sync ups for other topics which >>> are not >>> > covered by the proposal. >>> > >>> > Link to the Proposal Google doc >>> > < >>> > >>> https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# >>> > > >>> > >>> > Thanks, >>> > Wangda Tan >>> > >>> >> --000000000000f88455058b50a6ca--