From dev-return-8473-archive-asf-public=cust-asf.ponee.io@airflow.apache.org Fri May 10 21:10:54 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 389F918061A for ; Fri, 10 May 2019 23:10:54 +0200 (CEST) Received: (qmail 362 invoked by uid 500); 10 May 2019 21:10:50 -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 317 invoked by uid 99); 10 May 2019 21:10:48 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 May 2019 21:10:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 74885180F2F for ; Fri, 10 May 2019 21:10:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -13.699 X-Spam-Level: X-Spam-Status: No, score=-13.699 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=google.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id mAQrpu3wGUSt for ; Fri, 10 May 2019 21:10:45 +0000 (UTC) Received: from mail-pg1-f170.google.com (mail-pg1-f170.google.com [209.85.215.170]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 4E2885FB4B for ; Fri, 10 May 2019 21:10:44 +0000 (UTC) Received: by mail-pg1-f170.google.com with SMTP id t22so3563117pgi.10 for ; Fri, 10 May 2019 14:10:44 -0700 (PDT) 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:cc; bh=QwJ8bNTnvTp3lOWSMjAcUHRDIF6OylhB3BdfzPDk1Og=; b=OB3S2ggD3YRhUmISo5vKlcvZfkJ8KLjte/1upSAoNpultzMZsNQ7lUOVFGYfX0NE9v 90GINdtAkr6rdgVUJztrEIS+19XoW+aSPNUqoxzSIsKkcpFvLyZC2MXoJtRhJIl9NyKb n3F6VQ9CxyxCHIUFhwSOA8smWeZKZJDJm31AMi/gZvc1O9GHlQ7GKZ4vhYChieT5jlvJ MqfPW41ZHxm9yR+zUtxoRUuGYN25cH058/9ZMUXFLczc/EWmf5m0DZJpYci4IoojOvd5 ZBvfQpUnF93YSs1FIUwSAZkmHfpzfINwpNeYRgS8FLXeDkc7g61K3/LllUBRNbZxqeM7 C0lg== X-Gm-Message-State: APjAAAWPTBzdy6MT9PSXg8zJuDiefI00ltdI8hqxV5kqLXMRuRperT2f a2UdvqLdT2aN/kralIXXzis/zwU7Rrs9kfiO4JN/coEboQI= X-Google-Smtp-Source: APXvYqzcMhRWta5B9aTIjDJwodobCZ20/IyNh1gJ9fYxvxddYTRZDLNPbY4mQD24RcMHgh4+ZiWiqCuvJmBfQ9wzLr8= X-Received: by 2002:a62:6807:: with SMTP id d7mr16806226pfc.75.1557522642167; Fri, 10 May 2019 14:10:42 -0700 (PDT) MIME-Version: 1.0 References: <92B21A4B-9BEB-48CB-8E6A-522A31472DAC@apache.org> In-Reply-To: From: Aizhamal Nurmamat kyzy Date: Fri, 10 May 2019 14:10:06 -0700 Message-ID: Subject: Re: [Proposal] Component changes for Apache Airflow To: dev@airflow.apache.org Cc: Siddharth Anand , airflowuser Content-Type: multipart/alternative; boundary="000000000000d141b305888eff36" --000000000000d141b305888eff36 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you for Jira powers, Fokko :) I am aiming to get it done by Monday. Regards, Aizhamal *From: *Driesprong, Fokko *Date: *Fri, May 10, 2019 at 4:05 AM *To: * *Cc: *Siddharth Anand, airflowuser Hi Aizhamal, > > Great suggestions. The Jira needs some love. I've added you to the > administrator group. Let me know if there are any issues. > > Cheers, Fokko > > Op ma 6 mei 2019 om 20:28 schreef Aizhamal Nurmamat kyzy > : > > > Hello all, > > > > If it's okay by everyone, I would like to start performing the changes > > outlined in the doc. +Siddharth Anand could you > grant > > me the pertinent privileges to Airflow JIRA? Once you grant me those, I > > will also have Bulk Change permission[1] to make those changes faster. > > > > I will perform the changes, and notify this thread once it's done. > > > > Thank you, > > Aizhamal > > > > [1] https://issues.apache.org/jira/browse/INFRA-18338 > > > > *From: *Jarek Potiuk > > *Date: *Fri, May 3, 2019 at 5:31 AM > > *To: * > > *Cc: *airflowuser > > > > +1 on mandatory component. +1 on mandatory version. I like the proposed > > > cleanup suggestions. > > > > > > According to this discussion: > > > > > > > > > https://community.atlassian.com/t5/Jira-Core-questions/Project-based-labe= ls-in-Jira/qaq-p/101203 > > > we > > > can disable labels field and create our own per-project custom field > with > > > custom values defined. > > > > > > J. > > > > > > > > > On Fri, May 3, 2019 at 12:04 AM Aizhamal Nurmamat kyzy > > > wrote: > > > > > > > +1 on Ash's points. > > > > > > > > is it possible to disable labels to begin with? > > > > > I see no great benefit in having components with labels. > > > > > We can do just fine with only components. > > > > > > > > > I think we need to keep the labels for searchability and findabilit= y: > > eg. > > > > user creates an issue with 'redshift' label within 'aws-operators', > and > > > we > > > > want to allow everyone to look those issues up if they care only > about > > > > redshift. Also GSoC, GSoD, and other things that don't necessarily > map > > to > > > > components. > > > > > > > > I also think that the "version" field should be mandatory. > > > > > It's important to know against which airflow version the ticket i= s > > > > > reported. > > > > > > > > > +1 here. Users must know the version when they file a bug, and if > those > > > > bugs get fixed with newer versions, it would allow us to go back an= d > > > close > > > > those issues more efficiently. Any other thoughts? > > > > > > > > Best, > > > > Aizhamal > > > > > > > > > > > > > > > > > > > > > > > > > > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 O= riginal Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2= =80=90 > > > > > On Wednesday, May 1, 2019 12:17 PM, Ash Berlin-Taylor < > > ash@apache.org> > > > > > wrote: > > > > > > > > > > > This sounds like a fantastic idea. > > > > > > > > > > > > I would add to the list: > > > > > > > > > > > > - Remove labels that should be components (we have a gcp labe= l > > and > > > a > > > > > gcp component for instance) - having duplication in them is > confusing > > > > > > - Possibly use a label to indicate when an issue has already > been > > > > > triaged (to avoid duplicated effort) > > > > > > > > > > > > We can delete components, but labels are Jira wide so apply > > > across > > > > > every ASF project so we can't do much about what appears in the > > > > > auto-complete. This would be the place where a Triager's Guide > would > > > come > > > > > in to play. > > > > > > > > > > > > -ash > > > > > > > > > > > > > > > > > > > On 1 May 2019, at 00:26, Aizhamal Nurmamat kyzy > > > > > aizhamal@google.com.INVALID wrote: > > > > > > > Hello everyone, > > > > > > > I would like to propose a few changes for the Apache Airflow > > JIRA. > > > > The > > > > > > > reason behind this proposal is that the set of components is > > > > > disorganized, > > > > > > > and it could use some improvements to track the status of the > > > project > > > > > and > > > > > > > improve the Jira triage. > > > > > > > I outlined all the proposed changes (and reasons behind) in > this > > > > > document > > > > > > > [1]. Please take a look and comment if you have any > suggestions. > > I > > > > also > > > > > > > created a public dashboard to to be able to look into some > > > statistics > > > > > > > around JIRA issues [2]. > > > > > > > The high level overview of changes is: > > > > > > > > > > > > > > - > > > > > > > > > > > > > > Clean up components that are typos, duplicates or overly > specific > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > > > > > Make component a required field when filing an issue in JIRA > > > > > > > > > > > > > > ------------------------------------------------------------- > > > > > > > > > > > > > > Give a component to all issues that don=E2=80=99t have one at= the > moment > > > > > > > > > > > > > > > ----------------------------------------------------------------- > > > > > > > > > > > > > > Ensure that no new components are created unless it=E2=80=99s= discussed > > by > > > > the > > > > > > > community > > > > > > > For further details, please take a look at the doc[1], and > share > > > your > > > > > > > thoughts on it. > > > > > > > Thank you, > > > > > > > Aizhamal > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > > > https://docs.google.com/document/d/1gticSJ7LgD15XHgQhEP78-Ky38Er_NnMlarIv= SQ8NYM/edit?usp=3Dsharing > > > > > > > [2] > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=3D12333= 933 > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Jarek Potiuk > > > Polidea | Principal Software Engineer > > > > > > M: +48 660 796 129 <+48660796129> > > > E: jarek.potiuk@polidea.com > > > > > > --000000000000d141b305888eff36--