From dev-return-8540-archive-asf-public=cust-asf.ponee.io@airflow.apache.org Fri May 24 22:17:49 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 E4FF7180671 for ; Sat, 25 May 2019 00:17:48 +0200 (CEST) Received: (qmail 94736 invoked by uid 500); 24 May 2019 22:17:46 -0000 Mailing-List: contact dev-help@airflow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.apache.org Delivered-To: mailing list dev@airflow.apache.org Received: (qmail 94723 invoked by uid 99); 24 May 2019 22:17:46 -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, 24 May 2019 22:17:46 +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 0177BC1038 for ; Fri, 24 May 2019 22:17:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.8 X-Spam-Level: * X-Spam-Status: No, score=1.8 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] 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 rjFksyyqgBkk for ; Fri, 24 May 2019 22:17:44 +0000 (UTC) Received: from mail-vs1-f52.google.com (mail-vs1-f52.google.com [209.85.217.52]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 2FB466127B for ; Fri, 24 May 2019 22:17:44 +0000 (UTC) Received: by mail-vs1-f52.google.com with SMTP id q64so6905159vsd.1 for ; Fri, 24 May 2019 15:17:44 -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=9rcxwyd+o7FUZUVQCsW/mNeqte3flEHSCVfTgd5d/Hw=; b=D705jHxJg80yt27koYtSgdqviZeIkCacCjUNJQYQmyMqESHvnHFW7oP6Vr312jPMeX iOvfnChOhoiD80yppiJ55p+UMxQ4u1Lu2lC3k8ioA2V4N+YdgR1TWB5ip2gME2L/QE1M dqPhJRtXeT6l4f432dWDtqW42DwJNzS0cKn1juW1T/hNGOntlp+p/s+rXeFdBSueXxkr 42Z0SQJJxfVsb2Kp6WEjrTBUtS3YZvwQcI2lqs6Wg4f2/+GV7I1K0cafwVVuN0IV1Orj 8f0la+4FJqt/TOFRDBXd53hZElbyQzA4JIYKt2VCgfLjaZG+N1at95bO6BQJUdhE21BT sBVg== 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=9rcxwyd+o7FUZUVQCsW/mNeqte3flEHSCVfTgd5d/Hw=; b=LhcC9tXw8+aPEZqUPB2MMnCoHoPhdiOWgpzcPFobmjafIprsuTFuA070nyDq+uLV+H BSJTi4NfCxXQlRcHm9tSqcRtViuwZsBTTZA3EgkyF4Ut4RLL7YDxhh3UxZNWy/73DnQY 0K7cQcsB2+FKpIjCW3YcAaHcW1ZH4o35O7Els1bdYl601rL3FlAmN2nXYjPSABAvDLDw FXAmgpxe+lDWVcOuMmcCwtDn4BhA0wK5J283pZpoQEORkNTFGbAc0rnugTFsrfNt1Bwz f1CmHlPA3NGv7YpuQT9ojtKuaGJKWbZZwJ/J3V1AxhlUQAFa5gTByH49FjPEIKFl8C/Z 998Q== X-Gm-Message-State: APjAAAXuRmBry5FOf70ZAfbLvibwIYydpwb6dyY0ov9wUGGlVD8OyvKq huDy2kJcuH+tpYv0rxe+DKolGSXzxFhdFyMg4yKEE1EvUX8= X-Google-Smtp-Source: APXvYqxrDf1y9VvluAgu2SP+mYhVNWJZhivc22QFn5UiKdrQKNJM+hzqPDCpdE+XI7dofDJDIFAfWtYx7/L5jkuOFZA= X-Received: by 2002:a67:fe4e:: with SMTP id m14mr10671355vsr.71.1558736257828; Fri, 24 May 2019 15:17:37 -0700 (PDT) MIME-Version: 1.0 From: Sergio Kef Date: Sat, 25 May 2019 00:17:11 +0200 Message-ID: Subject: Proposal: Restructure slack To: dev@airflow.apache.org Content-Type: multipart/alternative; boundary="000000000000f24f0e0589a990e5" --000000000000f24f0e0589a990e5 Content-Type: text/plain; charset="UTF-8" Slack is a channel that could support a lot more our community. I've noticed that as a developer I get a bit overwhelmed by the amount of messages there, every time I join. This is a "good" problem, shows engaging community. What we miss though is the opportunity to catch up quickly what's going on, if we missed some days/weeks or even if it's our first time there. So I propose a small restructure of the channels to make it easier follow and catch up. * announcements (as is) - new releases - community announcements * general - events (meetings, webinars, conferences, etc) - material (tutorials, blog posts, etc) * contribute - contributors' questions (getting started, ci, testing, etc) - future ideas & more (eg some premature AIPs) - call for help on bugs/fixes/PRs * how-to (similar to current troubleshooting) - user issues - guidance on ETLs Of course the list is open for suggestions. Let me know what you think. Sergio. --000000000000f24f0e0589a990e5--