From dev-return-4183-archive-asf-public=cust-asf.ponee.io@hudi.apache.org Fri Jul 16 02:35:07 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 1AB0D180661 for ; Fri, 16 Jul 2021 04:35:07 +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 E259462917 for ; Fri, 16 Jul 2021 02:35:05 +0000 (UTC) Received: (qmail 87593 invoked by uid 500); 16 Jul 2021 02:35:05 -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 87581 invoked by uid 99); 16 Jul 2021 02:35:04 -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, 16 Jul 2021 02:35:04 +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 E65EB1FF489 for ; Fri, 16 Jul 2021 02:35:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamproc1-he-de.apache.org X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 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_H3=0.001, RCVD_IN_MSPIKE_WL=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 5RiFoqQ0csiz for ; Fri, 16 Jul 2021 02:35:01 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.160.178; helo=mail-qt1-f178.google.com; envelope-from=n.siva.b@gmail.com; receiver= Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id 30178BC4A5 for ; Fri, 16 Jul 2021 02:35:01 +0000 (UTC) Received: by mail-qt1-f178.google.com with SMTP id c9so6057672qte.6 for ; Thu, 15 Jul 2021 19:35:01 -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=0p4+pDyIGtR5AiUViqQQ93fX6JpN1UnQXSHfgJ5J7uc=; b=XAw2OcXm7HT8qyqCD+MMMNTO7qUfq+PPZcGxv3AfBOvuEll7qTXIPo22wUMyHgli/b 3oPoK8R50BWhgeeHL4yhoLbmAdmY4ZGjR8u/lH1yEMNf825KXA3DAZncaRhGDLhGAp4Q UF2Xx/6j/bJXVXIkM8js1S1V97erPrVu1DnLyTqmfI4z8UHtFOU5E/QUOF01afQkL6ML fZA6SzBiqKa+fjNhGUdUXBZ2EJ93cpr5xFUi2YpergBp/w7cK193ToanbQ72W/3KSAH+ y1dYC8PO7Q32nvd1xgISMoDNgFbnCxQuI97Vj15Sxbf8xyYJRcWpC3MtIq9mJLcg1TSI JzLA== 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=0p4+pDyIGtR5AiUViqQQ93fX6JpN1UnQXSHfgJ5J7uc=; b=uIdMy117bSXg64Z1zVQ/SMiaNERoLG6LwTpRLJf/RkCWpOwcWntY1qjWkR9KyL2t+i wNAy7RsqKV1Rg45AwYweEc8s2JmRInl5cS57w3+ctntjEoHRMbWVodYGlldg72z6bC9C jIyzfJjm+T6CkxqRKpOqZCroTL6i0+WUPg7Xd3zEwUDRwLY1JOHkFivH7dPQ/YdPzheq pkJuseyqtSE3AtJ8YNezacSgdRpHpRbtJhatiyYdPv87kunmBrVmOkObdodpRghGxscb DFDwDFllkylikekLEZxO75+NDY1CjNsPjmG8JNdoFE1WY9tAx2FkkzLHJybs/l0leGYI Dmrg== X-Gm-Message-State: AOAM532QliGZzgR/yXOjrjJ3226dK5QJJQdQ0GDF0THFR3NJFu9gdd5O 3m7SByNQlrd6MIECxY+F6PBGB7rdjoUt7sveCyJN5CgX X-Google-Smtp-Source: ABdhPJyeTHbUObyUAghIyl691b9Et4xFw25VugRXZaoOL93yvyDcRppza/+fLi7E3MGe25vgxK8Wdxj8Of/nYXLd2+g= X-Received: by 2002:ac8:6708:: with SMTP id e8mr6777865qtp.166.1626402900491; Thu, 15 Jul 2021 19:35:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sivabalan Date: Thu, 15 Jul 2021 22:34:49 -0400 Message-ID: Subject: Re: [DISCUSS] Consolidate all dev collaboration to Github To: dev@hudi.apache.org Content-Type: multipart/alternative; boundary="00000000000025419905c7346ffa" --00000000000025419905c7346ffa Content-Type: text/plain; charset="UTF-8" +1 on B. Not sure on A though. I understand the intent to have all in one place. but not very sure if we can get all functionality (version, type, component, status, parent- child relation), etc ported over to github. I assume labels are the only option we have to achieve these. Probably, we should also document the labels in detail so that anyone looking to take a look at untriaged issues should know how/where to look at. If we plan to use GH issues for all, I am sure there will be a lot of proliferation of issues. On Fri, Jul 9, 2021 at 12:29 PM Vinoth Chandar wrote: > Based on this, I will start consolidating more of the cWiki content to > github wiki and master branch? > > JIRA vs GH Issue still probably needs more feedback. I do see the tradeoffs > there. > > On Fri, Jul 9, 2021 at 2:39 AM wei li wrote: > > > +1 > > > > On 2021/07/02 03:40:51, 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 > > > > > > -- Regards, -Sivabalan --00000000000025419905c7346ffa--