From common-dev-return-102385-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Jun 19 15:44:23 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 B00AD18060F for ; Wed, 19 Jun 2019 17:44:22 +0200 (CEST) Received: (qmail 97353 invoked by uid 500); 19 Jun 2019 15:44:17 -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 97324 invoked by uid 99); 19 Jun 2019 15:44:17 -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; Wed, 19 Jun 2019 15:44:17 +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 A3FCEC1789 for ; Wed, 19 Jun 2019 15:44:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.801 X-Spam-Level: * X-Spam-Status: No, score=1.801 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, 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=verizonmedia.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 LIGudAU8Qeu0 for ; Wed, 19 Jun 2019 15:44:14 +0000 (UTC) Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id B8B0D5F5A9 for ; Wed, 19 Jun 2019 15:44:13 +0000 (UTC) Received: by mail-io1-f47.google.com with SMTP id j6so9577971ioa.5 for ; Wed, 19 Jun 2019 08:44:13 -0700 (PDT) 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=jIZrpCUfUAViPjm3stgrnx4of5HnhnMaNlcBnBC0obE=; b=DgmTcAklIdfdPf4GpwoRjP/xLbyVNXARP6hYQA89Dlt6aQu7XKLeOMMG+DeVhn2F/i dTWijiDpRthE2hvRXMOHYAUG7VEhpd2gHEa4ckPkvcv4VU0pELgV7q33ypXfCUeXaFk3 MbKdXT2fzVCjTpa/ima4OKni6hOYdpzqdo/OCTURBnqxUSL/1Kzqe6YDXSFHPex/wNY4 mePJvFR+N//PT/VAJOVbmTZTYDqFiBC9e2L3rLRsKOBOK+fA9vxl+8TxqGpgi5Df8toh 6gttp0IOJirDthD43l21hJqqyQFRUYIZSh8Evn9WKohapRtIMEg7JllNGWisV1fqsksy ucjw== X-Gm-Message-State: APjAAAUNrlft1hXnOwh/SqXeUyo0FICbSjk2xHXjyGRCOzVq3XIVX1Ig IO4xHxhvUc0/DwuI1yxB6EsosLsEv9Phlx8gn14fVg== X-Google-Smtp-Source: APXvYqzACv6qArQ9+Wk7sxNK7uc6r0yUvl2mFPLvkdiyDwO3dgGpy+ZLGb265FKdLdjXpj1Yj3lFwi2kUT38qhuPVgk= X-Received: by 2002:a02:5185:: with SMTP id s127mr11142729jaa.44.1560959053025; Wed, 19 Jun 2019 08:44:13 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Eric Badger Date: Wed, 19 Jun 2019 10:44:02 -0500 Message-ID: Subject: Re: [DISCUSS] A unified and open Hadoop community sync up schedule? To: Wangda Tan Cc: submarine-dev@hadoop.apache.org, Wei-Chiu Chuang , Anu Engineer , Yufei Gu , yarn-dev@hadoop.apache.org, Hdfs-dev , Hadoop Common , mapreduce-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary="000000000000dd7622058baf196d" --000000000000dd7622058baf196d Content-Type: text/plain; charset="UTF-8" Is there a YARN call today (in 16 minutes)? I saw it on the calendar until a few minutes ago. Eric On Tue, Jun 18, 2019 at 11:18 PM Wangda Tan wrote: > Thanks @Wei-Chiu Chuang . updated gdoc > > On Tue, Jun 18, 2019 at 7:35 PM Wei-Chiu Chuang > wrote: > > > Thanks Wangda, > > > > I just like to make a correction -- the .ics calendar file says the first > > Wednesday for HDFS/cloud connector is in Mandarin whereas on the gdoc is > to > > host it on the third Wednesday. > > > > On Tue, Jun 18, 2019 at 5:29 PM Wangda Tan wrote: > > > > > Hi Folks, > > > > > > I just updated doc: > > > > > > > > > https://docs.google.com/document/d/1GfNpYKhNUERAEH7m3yx6OfleoF3MqoQk3nJ7xqHD9nY/edit# > > > with > > > dial-in information, notes, etc. > > > > > > Here's a calendar to subscribe: > > > > > > > > > https://calendar.google.com/calendar/ical/hadoop.community.sync.up%40gmail.com/public/basic.ics > > > > > > I'm thinking to give it a try from next week, any suggestions? > > > > > > Thanks, > > > Wangda > > > > > > On Fri, Jun 14, 2019 at 4:02 PM Wangda Tan > wrote: > > > > > > > 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 < > aengineer@cloudera.com > > > > > > >> 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 > > > >>>> > > > > >>>> > > > >>> > > > > > > --000000000000dd7622058baf196d--