From dev-return-4159-archive-asf-public=cust-asf.ponee.io@hudi.apache.org Fri Jul 2 19:54:19 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-ec2-va.apache.org (mxout1-ec2-va.apache.org [3.227.148.255]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id 95AD6180660 for ; Fri, 2 Jul 2021 21:54:19 +0200 (CEST) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-ec2-va.apache.org (ASF Mail Server at mxout1-ec2-va.apache.org) with SMTP id 165C542EEB for ; Fri, 2 Jul 2021 19:54:14 +0000 (UTC) Received: (qmail 22902 invoked by uid 500); 2 Jul 2021 19:54:13 -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 22890 invoked by uid 99); 2 Jul 2021 19:54:13 -0000 Received: from spamproc1-he-de.apache.org (HELO spamproc1-he-de.apache.org) (116.203.196.100) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jul 2021 19:54:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamproc1-he-de.apache.org (ASF Mail Server at spamproc1-he-de.apache.org) with ESMTP id 52AD31FF48E for ; Fri, 2 Jul 2021 19:54:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamproc1-he-de.apache.org X-Spam-Flag: NO X-Spam-Score: -0.002 X-Spam-Level: X-Spam-Status: No, score=-0.002 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=0.2, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamproc1-he-de.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-ec2-va.apache.org ([116.203.227.195]) by localhost (spamproc1-he-de.apache.org [116.203.196.100]) (amavisd-new, port 10024) with ESMTP id jeT-oe7UwrPu for ; Fri, 2 Jul 2021 19:54:11 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.208.172; helo=mail-lj1-f172.google.com; envelope-from=xu.shiyan.raymond@gmail.com; receiver= Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id 392A2BC489 for ; Fri, 2 Jul 2021 19:54:11 +0000 (UTC) Received: by mail-lj1-f172.google.com with SMTP id r16so14804195ljk.9 for ; Fri, 02 Jul 2021 12:54:11 -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; bh=nrxAZ5h96w21/SHewtPhLhHJjD3Wj8/WGS+2OVAUsM8=; b=XqIp3uLHCchi/a4lFQthxXhYpnIF0YisyTSO+mnFFcjpYp6QF4KNlVQOKt3wB4YCWc Nzh+VKh072HdgicTtLzW9FBniTbDg2PiXChgmyWvpddfU84XaC4GdsGzNKoDi6+Wottn 58o+nkp+NP4/NS2CsqLfMbUnp+sW8ex7k7vYCfdVAMGFKWmSLmxz6KhFl200Usx7sqfX F6j8PX65dhwh2Hd/jsTSM4CJF79dhJzCqT99rmn74Jh6M9szGeKI6PqB/1ADPaa2k6vR xL6BogHNUjg4bs00K4Pma2A7Ck0UiwJuFRnDSfY1F6F0CbLBGmEHcUC2GQ0JKFTHIFAo OM4w== 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; bh=nrxAZ5h96w21/SHewtPhLhHJjD3Wj8/WGS+2OVAUsM8=; b=TPOHmhp5zGb3fzqO+o9wI3twoGWYvQuujxsuJLR+JLPB1fTPl8tNzjPeOm7hyksrQb ydbJkPD8vosu9NIGsomvOFccA6jREfW+9gHanFCJTOgZUgs9O3l/5605daitgRs7OYsg GUzdq8YJpP3vI7giKAcjKQdrHkGR+rkLbXk3NSMaBq4c0VJgCcON2z99S+PRUzflxLvY +YLTDuaBwcoa7KbdLVg/2LqbH9XN56seUBGfMi8wQEG1Y+8voKbpBgkOr38RJZlrRPEt kUlEgJJ7iBfJj3hqBgfYQ3qwquefcOXezX0NSGyV+JqNTVd1yHP9un1CHW3x1jaYGj6U Dkxg== X-Gm-Message-State: AOAM533tKkIxuPkM7F40jxJIEUfWfGWEbjIFBYiGZRnMraPcN1/oC/yQ 4VpeYJBzCPDK3UOH2zgii4p5xgLy7rCL7r54maW5QSfJ2g== X-Google-Smtp-Source: ABdhPJyL7qIKhP/8B86VU4xcNF07vMg2S7EUR9cgqPU8y3LMn9SrJ0rBFgSQC4fWERWu2Mzb+9g8xCu7GiXHO4HOhgo= X-Received: by 2002:a2e:8584:: with SMTP id b4mr855146lji.277.1625255649793; Fri, 02 Jul 2021 12:54:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Raymond Xu Date: Fri, 2 Jul 2021 12:53:58 -0700 Message-ID: Subject: Re: [DISCUSS] Consolidate all dev collaboration to Github To: dev@hudi.apache.org Content-Type: multipart/alternative; boundary="000000000000acd99205c6295199" --000000000000acd99205c6295199 Content-Type: text/plain; charset="UTF-8" +1 for both A and B Also a related suggestion: we can put the release notes and new feature highlights in the release notes section in GitHub releases instead of separately writing them in the asf-site On Fri, Jul 2, 2021 at 11:25 AM Prashant Wason wrote: > +1 for complete Github migration. JIRA is too cumbersome and painful to > use. > > Github PRs and wiki also improve visibility of the project and I think may > increase community feedback and participation as its simpler to use. > > Prashant > > > On Thu, Jul 1, 2021 at 8:41 PM Vinoth Chandar wrote: > > > 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 > > > --000000000000acd99205c6295199--