From dev-return-4157-archive-asf-public=cust-asf.ponee.io@hudi.apache.org Fri Jul 2 03:41:06 2021 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-he-de.apache.org (mxout1-he-de.apache.org [95.216.194.37]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id DB79418064A for ; Fri, 2 Jul 2021 05:41:06 +0200 (CEST) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-he-de.apache.org (ASF Mail Server at mxout1-he-de.apache.org) with SMTP id 09E9E62176 for ; Fri, 2 Jul 2021 03:41:05 +0000 (UTC) Received: (qmail 19904 invoked by uid 500); 2 Jul 2021 03:41:04 -0000 Mailing-List: contact dev-help@hudi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hudi.apache.org Delivered-To: mailing list dev@hudi.apache.org Received: (qmail 19882 invoked by uid 99); 2 Jul 2021 03:41:04 -0000 Received: from ec2-52-204-25-47.compute-1.amazonaws.com (HELO mailrelay1-ec2-va.apache.org) (52.204.25.47) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jul 2021 03:41:04 +0000 Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) by mailrelay1-ec2-va.apache.org (ASF Mail Server at mailrelay1-ec2-va.apache.org) with ESMTPSA id 5072D3E977 for ; Fri, 2 Jul 2021 03:41:04 +0000 (UTC) Received: by mail-lf1-f50.google.com with SMTP id d16so15642852lfn.3 for ; Thu, 01 Jul 2021 20:41:04 -0700 (PDT) X-Gm-Message-State: AOAM5302fBA9MxTG9ANgcbvFtOdN2Yhhvbm1Vzq8xcpiD7IndH/wXkst 42SBIv3OnyTUq7K8Thmh9tKp4O6rmfjoVXUGj7U= X-Google-Smtp-Source: ABdhPJy8XkttuIpd3hTnBAF+Xjg0UcLOiBVud7pC3WmY7A2u6ijwzI0wqINm6L0rtQEMytWz5TfC5wz8H6QP02gh2RE= X-Received: by 2002:a19:c50c:: with SMTP id w12mr2120633lfe.397.1625197263405; Thu, 01 Jul 2021 20:41:03 -0700 (PDT) MIME-Version: 1.0 From: Vinoth Chandar Date: Thu, 1 Jul 2021 20:40:51 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: [DISCUSS] Consolidate all dev collaboration to Github To: dev Content-Type: multipart/alternative; boundary="0000000000009349c405c61bb9ff" --0000000000009349c405c61bb9ff Content-Type: text/plain; charset="UTF-8" Hi all, When we incubated Hudi, we made some initial choices around collaboration tools of choice. I am wondering if there are still optimal, given the scale of the community at this point. Specifically, two points. A) Our issue tracker is JIRA, while we just use Github Issues for support triage. While JIRA is pretty advanced and gives us the ability to track releases, versions and kanban boards, there are few practical operational problems. - Developers often open bug fixes/PR which all need to be continuously tagged against a release version (fix version) - Referencing JIRAs from Pull Requests is great (we cannot do things like `fixes #1234` to close issues when PR lands, not an easy way to click and get to the JIRA) - Many more developers have a github account, to contribute to Hudi though, they need an additional sign-up on jira. So wondering if we should just use one thing - Github Issues, and build scripts/hubot or something to get the missing project management from boards. B) Our design docs are on cWiki. Even though we link it off the site, from my experience, many do not discover them. For large PRs, we need to manually enforce that design and code are in sync before we land. If we can, I would love to make RFC being in good shape a pre-requisite for landing the PR. Once again, separate signup is needed to write design docs or comment on them. So, wondering if we can move our process docs etc into Github Wiki and RFCs to the master branch in a rfc folder, and we just use github PRs to raise RFCs and discuss them. This all also makes it easy for us to measure community activity and keep streamlining our processes. personally, these different channels are overwhelming to me at-least :) Love to hear thoughts. Please specify if you are for,against each of A and B. Thanks Vinoth --0000000000009349c405c61bb9ff--