From yarn-dev-return-33155-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Jun 7 23:39:03 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 2428E18067E for ; Sat, 8 Jun 2019 01:39:03 +0200 (CEST) Received: (qmail 34755 invoked by uid 500); 7 Jun 2019 23:38:55 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 34697 invoked by uid 99); 7 Jun 2019 23:38:55 -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, 07 Jun 2019 23:38:55 +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 6319EC1D67; Fri, 7 Jun 2019 23:38:54 +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=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 igMNH58hptlf; Fri, 7 Jun 2019 23:38:52 +0000 (UTC) Received: from mail-wm1-f41.google.com (mail-wm1-f41.google.com [209.85.128.41]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 38AE45F175; Fri, 7 Jun 2019 23:38:52 +0000 (UTC) Received: by mail-wm1-f41.google.com with SMTP id s3so3526834wms.2; Fri, 07 Jun 2019 16:38:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=C5WLfuLKcJNmlhNGZ2cgXVQsQGVJTI2aRb04QL9t+/M=; b=RyhiQQB+8Cm1rt98h13TmFUVk5cVTM20qQueq0Oy+kQBssnad5tEnyNBwBRoG7JD6E iVAZQMSaAtZsETE7joHW/9JW/RqTudylUMtz+75TN7BEYojRU0cqR/C1zcpgx2e+0Qfu a4oEQjtgwNmrZx/KQDaUQxalQUJ6z+m0WjbJ4tYUrjsY5CH+S2c93j87tKd94/NK4YwB bo80pVy5q7GG5vcK4dQhelwQKwAeFPgLI8Ko1+Fq1CCgdvwE4NKxeTYgQXUerpf3uU1R 8+oxYNkvprKmhlseKQnFglyVoYD942VSGIdhK6LcXQE6O+rGhvFq1Z3LbUE3w3Rl2CfY gkDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=C5WLfuLKcJNmlhNGZ2cgXVQsQGVJTI2aRb04QL9t+/M=; b=rP0XHYyQVwf6sD444wEc8lsE08HlF8rX6YrWdco/rHaSm4eifE8+3KLUHnilhxnZaN AfLH3qFi9dZq+ZITDVXn1biQ+pNMAuyco2U6i0J1TVuR4Q7/DGGUTGULxelFvNRjNOip VQG0pQNyBsF3uMAaEyQC2J7DAYz3HvXD/NZeP6Gx9E/OCmoxnq5EwfvNukicwHBF2azO KjNhmm94/LVqI63zawyOqkQC5JxzEUY0W8AzLPamJLMprFazjO/PXQJE8aYhoI91VWQN OVT5oqyeeL2xfdMsijyJxPFH6ijDKxWF1b5iOW62AIZ/9AfTX+D/3tHGREKyWlZP1HiI 5dJg== X-Gm-Message-State: APjAAAWRS39PANcF6PbnyyGIpK0Gn+ZXGL7jhtxuKeGnz0b5gt3hxYsx voKqLRCDY/V0fVHdMaF0DziuyV0EmiYzy9IZTzdbJR5JJBjzFg== X-Google-Smtp-Source: APXvYqy15SdHJKu5nLEQdGzlFK9U2MneNoyEhv15CbEh9/ykMu7TfD4CsLVgk7q96o/rKo+R1Wsvp1DI2yVtIxEQJag= X-Received: by 2002:a1c:1bd0:: with SMTP id b199mr4986554wmb.128.1559950730840; Fri, 07 Jun 2019 16:38:50 -0700 (PDT) MIME-Version: 1.0 From: Wangda Tan Date: Fri, 7 Jun 2019 16:38:24 -0700 Message-ID: Subject: [DISCUSS] A unified and open Hadoop community sync up schedule? To: yarn-dev@hadoop.apache.org, Hdfs-dev , Hadoop Common , mapreduce-dev@hadoop.apache.org, submarine-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary="0000000000002dcfcf058ac45528" --0000000000002dcfcf058ac45528 Content-Type: text/plain; charset="UTF-8" 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 . 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 Thanks, Wangda Tan --0000000000002dcfcf058ac45528--