You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID> on 2019/04/30 23:26:31 UTC
[Proposal] Component changes for Apache Airflow
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’t have one at the moment
-
Ensure that no new components are created unless it’s 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_NnMlarIvSQ8NYM/edit?usp=sharing
[2]
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@apache.org>.
Please, disregard the link in my previous email that was added accidentally
:/
On Tue, Mar 3, 2020, 10:27 AM Aizhamal Nurmamat kyzy <ai...@apache.org>
wrote:
> Thank you for spotting it, Jiajie! We should definitely combine them, and
> remove duplicates.
>
> My guess is that the new components were added accidentally by committers
> / pmc members in the bug-creating screen. It seems one can create a
> component by pressing enter twice on the new component.
>
> If possible, we should adopt the following processes:
> 1) To create a new component, we'll ask people to request them in dev@
> <https://www.google.com/url?q=https://moma.corp.google.com/person/dev&sa=D&source=hangouts&ust=1583346187841000&usg=AFQjCNH821B7rN08r_gvPLpngTYliYhZFA> and
> have pmc votes
> 2) Remove the ability to create them from the bug-creating screen
>
>
>
>
> On Tue, Mar 3, 2020 at 8:49 AM Jiajie Zhong <zh...@hotmail.com>
> wrote:
>
>> Hey guys, sad to said that we have some similar component in JIRA now,
>> such as `db` vs `database`, or `test` vs `flaky_test`, or `executor` vs
>> `executor-kubernetes`.
>>
>> Should we combine them, and limit fix the component to avoid regression?
>>
>> Best Wish
>> — Jiajie
>>
>>
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@apache.org>.
Agree, we need to adopt more careful and thoughtful processes among PMC
around creating new components.
When the new component is created, it is also worth sharing its description
with the rest of the community on the dev list, so more of us are aware of
it and we can label issues more accurately.
On Tue, Mar 10, 2020 at 5:32 AM Jarek Potiuk <Ja...@polidea.com>
wrote:
> Agree. I think I created some of them without realising they are created
> automatically. Being more careful should be enough. We can always do such
> cleanups periodically. I think being able to add components as we need them
> is important - as we might have new components added (for example soon we
> will have backend credentials likely - they deserve their own component)
>
> J.
>
>
> On Tue, Mar 10, 2020 at 1:23 PM Ash Berlin-Taylor <as...@apache.org> wrote:
>
> > Not really a fan of removing admin as that limits other operations we can
> > do elsewhere -- it's not the end of the world if we get new components
> > created. We should just ask the PMC members to be careful/thoughtful when
> > they create components.
> >
> > And `executor` vs `executor-kubernetes` makes sense for instance -- the
> > Kube executor is it's own "beast" (not to mention there are 50+ tickets
> > assigned to that, so it's not a one off.)
> > -ash
> > On Mar 10 2020, at 12:00 am, Aizhamal Nurmamat kyzy <aizhamal@apache.org
> >
> > wrote:
> > > Seems the new components were created by the folks who had Project
> Admin
> > permissions: in our case all of the PMC have that permission [1]. One
> > solution is to remove PMC from project admins and establish a process of
> > "requesting creation of new components" in the dev list. I think it is
> > necessary, because it will be only harder to keep track of PMCs creating
> > new components on the go. WDYT? Any other alternatives? [1]
> >
> https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-restrict-users-ability-to-create-new-Components-while/qaq-p/993348
> > On Tue, Mar 3, 2020 at 5:49 PM Jiajie Zhong wrote: > I'm not quick
> familiar
> > with JIRA, but after we remove the ability to > create them from the
> > bug-creating screen, > > Do we could avoid someone create components by
> > accident? > > > Best Wish > — Jiajie
> >
> >
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48%20660%20796%20129> <+48660796129
> <+48%20660%20796%20129>>
> [image: Polidea] <https://www.polidea.com/>
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Jarek Potiuk <Ja...@polidea.com>.
Agree. I think I created some of them without realising they are created
automatically. Being more careful should be enough. We can always do such
cleanups periodically. I think being able to add components as we need them
is important - as we might have new components added (for example soon we
will have backend credentials likely - they deserve their own component)
J.
On Tue, Mar 10, 2020 at 1:23 PM Ash Berlin-Taylor <as...@apache.org> wrote:
> Not really a fan of removing admin as that limits other operations we can
> do elsewhere -- it's not the end of the world if we get new components
> created. We should just ask the PMC members to be careful/thoughtful when
> they create components.
>
> And `executor` vs `executor-kubernetes` makes sense for instance -- the
> Kube executor is it's own "beast" (not to mention there are 50+ tickets
> assigned to that, so it's not a one off.)
> -ash
> On Mar 10 2020, at 12:00 am, Aizhamal Nurmamat kyzy <ai...@apache.org>
> wrote:
> > Seems the new components were created by the folks who had Project Admin
> permissions: in our case all of the PMC have that permission [1]. One
> solution is to remove PMC from project admins and establish a process of
> "requesting creation of new components" in the dev list. I think it is
> necessary, because it will be only harder to keep track of PMCs creating
> new components on the go. WDYT? Any other alternatives? [1]
> https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-restrict-users-ability-to-create-new-Components-while/qaq-p/993348
> On Tue, Mar 3, 2020 at 5:49 PM Jiajie Zhong wrote: > I'm not quick familiar
> with JIRA, but after we remove the ability to > create them from the
> bug-creating screen, > > Do we could avoid someone create components by
> accident? > > > Best Wish > — Jiajie
>
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: [Proposal] Component changes for Apache Airflow
Posted by Ash Berlin-Taylor <as...@apache.org>.
Not really a fan of removing admin as that limits other operations we can do elsewhere -- it's not the end of the world if we get new components created. We should just ask the PMC members to be careful/thoughtful when they create components.
And `executor` vs `executor-kubernetes` makes sense for instance -- the Kube executor is it's own "beast" (not to mention there are 50+ tickets assigned to that, so it's not a one off.)
-ash
On Mar 10 2020, at 12:00 am, Aizhamal Nurmamat kyzy <ai...@apache.org> wrote:
> Seems the new components were created by the folks who had Project Admin permissions: in our case all of the PMC have that permission [1]. One solution is to remove PMC from project admins and establish a process of "requesting creation of new components" in the dev list. I think it is necessary, because it will be only harder to keep track of PMCs creating new components on the go. WDYT? Any other alternatives? [1] https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-restrict-users-ability-to-create-new-Components-while/qaq-p/993348 On Tue, Mar 3, 2020 at 5:49 PM Jiajie Zhong wrote: > I'm not quick familiar with JIRA, but after we remove the ability to > create them from the bug-creating screen, > > Do we could avoid someone create components by accident? > > > Best Wish > — Jiajie
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@apache.org>.
Seems the new components were created by the folks who had Project Admin
permissions: in our case all of the PMC have that permission [1].
One solution is to remove PMC from project admins and establish a process
of "requesting creation of new components" in the dev list. I think it is
necessary, because it will be only harder to keep track of PMCs creating
new components on the go.
WDYT? Any other alternatives?
[1]
https://community.atlassian.com/t5/Jira-Software-questions/How-can-I-restrict-users-ability-to-create-new-Components-while/qaq-p/993348
On Tue, Mar 3, 2020 at 5:49 PM Jiajie Zhong <zh...@hotmail.com>
wrote:
> I'm not quick familiar with JIRA, but after we remove the ability to
> create them from the bug-creating screen,
>
> Do we could avoid someone create components by accident?
>
>
> Best Wish
> — Jiajie
Re: [Proposal] Component changes for Apache Airflow
Posted by Jiajie Zhong <zh...@hotmail.com>.
I'm not quick familiar with JIRA, but after we remove the ability to create them from the bug-creating screen,
Do we could avoid someone create components by accident?
Best Wish
— Jiajie
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@apache.org>.
Thank you for spotting it, Jiajie! We should definitely combine them, and
remove duplicates.
My guess is that the new components were added accidentally by committers /
pmc members in the bug-creating screen. It seems one can create a component
by pressing enter twice on the new component.
If possible, we should adopt the following processes:
1) To create a new component, we'll ask people to request them in dev@
<https://www.google.com/url?q=https://moma.corp.google.com/person/dev&sa=D&source=hangouts&ust=1583346187841000&usg=AFQjCNH821B7rN08r_gvPLpngTYliYhZFA>
and
have pmc votes
2) Remove the ability to create them from the bug-creating screen
On Tue, Mar 3, 2020 at 8:49 AM Jiajie Zhong <zh...@hotmail.com>
wrote:
> Hey guys, sad to said that we have some similar component in JIRA now,
> such as `db` vs `database`, or `test` vs `flaky_test`, or `executor` vs
> `executor-kubernetes`.
>
> Should we combine them, and limit fix the component to avoid regression?
>
> Best Wish
> — Jiajie
>
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Jiajie Zhong <zh...@hotmail.com>.
Hey guys, sad to said that we have some similar component in JIRA now, such as `db` vs `database`, or `test` vs `flaky_test`, or `executor` vs `executor-kubernetes`.
Should we combine them, and limit fix the component to avoid regression?
Best Wish
— Jiajie
Re: [Proposal] Component changes for Apache Airflow
Posted by Jarek Potiuk <Ja...@polidea.com>.
Aizhamal,
sure, but give me some time for that, I am travelling to Bay Area next week
and I have pretty busy schedule :(
On Thu, May 30, 2019 at 8:38 AM Aizhamal Nurmamat kyzy <ai...@apache.org>
wrote:
> We really need to keep this discussion going around adding prefixes to
> components.
>
> @Jarek, would you mind kicking off a new thread? I will close this thread
> as the points I wanted to discuss and things to do regarding the first
> component changes are mostly done. Separating threads will help us to focus
> on one thing at a time and also measure the progress a little bit.
>
> Thank you,
> Aizhamal
>
> On Wed, May 29, 2019 at 21:09 Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > I think there is a discussion (and some work already done) to move more
> > mature operators/hooks from the 'contrib' directory to the main directory
> > for hooks/operators so I think "contrib-" prefix might be too easily
> > confused with the *"*contrib*"* folder until this is finalised.
> >
> > I think we need a better "abstraction" name for "operators+hooks" as we
> > might also use it in the upcoming documentation update. Something that
> will
> > easily separate out "core" from the "operators+hooks" specific for
> > particular external system.
> >
> > I am afraid I will open Pandora's box :) (we all know naming is hard
> > <https://hilton.org.uk/blog/why-naming-things-is-hard>), but Maybe
> "ext"
> > might be a good prefix ("ext-gcp", "ext-kubernetes", "ext-aws"). It can
> be
> > understood as both "extension" and "external" depending whether it is
> used
> > in context of Airflow (extension) or the Operator (external system to
> > connect to)?
> >
> > J.
> >
> > On Wed, May 29, 2019 at 11:50 PM Aizhamal Nurmamat kyzy
> > <ai...@google.com.invalid> wrote:
> >
> > > Hi Daniel,
> > >
> > > The reason I had removed `kubernetes` component is that the component
> > > attracted two different kinds of issues. I would like to be able to
> > > differentiate issues related to kubernetes executor, and
> > kubernetes-related
> > > operators and hooks. I have been thinking that prefixes may be helpful
> in
> > > this case.
> > >
> > > - For operators/hooks, we can have a: `contrib-kubernetes` component.
> > > - For the Kubernetes executor, we can have a `executor-kubernetes`
> > > component.
> > >
> > > I think this prefix structure would be really helpful, as it sets a
> > > precedent for other components for executors (e.g. `executor-celery`,
> > > `executors` (for any without a particular component)); and for
> > > operators/hook (e.g. `contrib-gcp`, `contrib-aws`, ...). This allows
> > > users/contributors to file issues, and see the appropriate components
> as
> > > they type the prefix.
> > >
> > > Thoughts?
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > E: jarek.potiuk@polidea.com
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
E: jarek.potiuk@polidea.com
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@apache.org>.
We really need to keep this discussion going around adding prefixes to
components.
@Jarek, would you mind kicking off a new thread? I will close this thread
as the points I wanted to discuss and things to do regarding the first
component changes are mostly done. Separating threads will help us to focus
on one thing at a time and also measure the progress a little bit.
Thank you,
Aizhamal
On Wed, May 29, 2019 at 21:09 Jarek Potiuk <Ja...@polidea.com> wrote:
> I think there is a discussion (and some work already done) to move more
> mature operators/hooks from the 'contrib' directory to the main directory
> for hooks/operators so I think "contrib-" prefix might be too easily
> confused with the *"*contrib*"* folder until this is finalised.
>
> I think we need a better "abstraction" name for "operators+hooks" as we
> might also use it in the upcoming documentation update. Something that will
> easily separate out "core" from the "operators+hooks" specific for
> particular external system.
>
> I am afraid I will open Pandora's box :) (we all know naming is hard
> <https://hilton.org.uk/blog/why-naming-things-is-hard>), but Maybe "ext"
> might be a good prefix ("ext-gcp", "ext-kubernetes", "ext-aws"). It can be
> understood as both "extension" and "external" depending whether it is used
> in context of Airflow (extension) or the Operator (external system to
> connect to)?
>
> J.
>
> On Wed, May 29, 2019 at 11:50 PM Aizhamal Nurmamat kyzy
> <ai...@google.com.invalid> wrote:
>
> > Hi Daniel,
> >
> > The reason I had removed `kubernetes` component is that the component
> > attracted two different kinds of issues. I would like to be able to
> > differentiate issues related to kubernetes executor, and
> kubernetes-related
> > operators and hooks. I have been thinking that prefixes may be helpful in
> > this case.
> >
> > - For operators/hooks, we can have a: `contrib-kubernetes` component.
> > - For the Kubernetes executor, we can have a `executor-kubernetes`
> > component.
> >
> > I think this prefix structure would be really helpful, as it sets a
> > precedent for other components for executors (e.g. `executor-celery`,
> > `executors` (for any without a particular component)); and for
> > operators/hook (e.g. `contrib-gcp`, `contrib-aws`, ...). This allows
> > users/contributors to file issues, and see the appropriate components as
> > they type the prefix.
> >
> > Thoughts?
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> E: jarek.potiuk@polidea.com
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Jarek Potiuk <Ja...@polidea.com>.
I think there is a discussion (and some work already done) to move more
mature operators/hooks from the 'contrib' directory to the main directory
for hooks/operators so I think "contrib-" prefix might be too easily
confused with the *"*contrib*"* folder until this is finalised.
I think we need a better "abstraction" name for "operators+hooks" as we
might also use it in the upcoming documentation update. Something that will
easily separate out "core" from the "operators+hooks" specific for
particular external system.
I am afraid I will open Pandora's box :) (we all know naming is hard
<https://hilton.org.uk/blog/why-naming-things-is-hard>), but Maybe "ext"
might be a good prefix ("ext-gcp", "ext-kubernetes", "ext-aws"). It can be
understood as both "extension" and "external" depending whether it is used
in context of Airflow (extension) or the Operator (external system to
connect to)?
J.
On Wed, May 29, 2019 at 11:50 PM Aizhamal Nurmamat kyzy
<ai...@google.com.invalid> wrote:
> Hi Daniel,
>
> The reason I had removed `kubernetes` component is that the component
> attracted two different kinds of issues. I would like to be able to
> differentiate issues related to kubernetes executor, and kubernetes-related
> operators and hooks. I have been thinking that prefixes may be helpful in
> this case.
>
> - For operators/hooks, we can have a: `contrib-kubernetes` component.
> - For the Kubernetes executor, we can have a `executor-kubernetes`
> component.
>
> I think this prefix structure would be really helpful, as it sets a
> precedent for other components for executors (e.g. `executor-celery`,
> `executors` (for any without a particular component)); and for
> operators/hook (e.g. `contrib-gcp`, `contrib-aws`, ...). This allows
> users/contributors to file issues, and see the appropriate components as
> they type the prefix.
>
> Thoughts?
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
E: jarek.potiuk@polidea.com
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
Hi Daniel,
The reason I had removed `kubernetes` component is that the component
attracted two different kinds of issues. I would like to be able to
differentiate issues related to kubernetes executor, and kubernetes-related
operators and hooks. I have been thinking that prefixes may be helpful in
this case.
- For operators/hooks, we can have a: `contrib-kubernetes` component.
- For the Kubernetes executor, we can have a `executor-kubernetes`
component.
I think this prefix structure would be really helpful, as it sets a
precedent for other components for executors (e.g. `executor-celery`,
`executors` (for any without a particular component)); and for
operators/hook (e.g. `contrib-gcp`, `contrib-aws`, ...). This allows
users/contributors to file issues, and see the appropriate components as
they type the prefix.
Thoughts?
Re: [Proposal] Component changes for Apache Airflow
Posted by Daniel Imberman <di...@gmail.com>.
@Aizhamal could we also please add a component for kubernetes-based
features or would that fall under other segments?
Thank you again for setting this up!
On Tue, May 28, 2019 at 8:08 PM Aizhamal Nurmamat kyzy
<ai...@google.com.invalid> wrote:
> Thanks everyone for your support and help!
>
> I am done with most of the tasks outlined in the document. Over the next
> few weeks I will keep going through issues that have no components and try
> to add one to them.
>
> Also, I have added descriptions for the components that I know about, but
> there are still many without description. It would be great if others could
> add them directly in JIRA, or add them in the same document[1] so that PMC
> can add that to JIRA.
>
> In the future, we can continue to improve the JIRA workflow, and our
> component structure. Some ideas worth considering for later:
>
> - Adding (removing) components that are needed (not needed)
> - Have component owners
> - Adding prefixes to component names to facilitate filing new issues in the
> right components
> - Changing the JIRA workflow to better identify issues that need to be
> triaged
> - etc.
>
> I think we can close this thread now. Thanks again!
> Aizhamal
>
> [1]
>
> https://docs.google.com/document/d/1gticSJ7LgD15XHgQhEP78-Ky38Er_NnMlarIvSQ8NYM/edit?usp=sharing
>
>
> On Tue, May 28, 2019 at 4:44 PM Daniel Imberman <
> dimberman.opensource@gmail.com> wrote:
>
> > Hi Aizhamal,
> >
> > Thank you for taking this on :). I've been looking to add epics recently
> > but that's just because I didn't know that components were a thing (they
> > make much more sense here).
> >
> > +1!
> >
> > Daniel
> >
> > On Tue, May 28, 2019 at 1:06 PM Aizhamal Nurmamat kyzy
> > <ai...@google.com.invalid> wrote:
> >
> > > Yes, that should work. Thanks Jarek :)
> > >
> > > On Tue, May 28, 2019 at 12:54 PM Jarek Potiuk <
> Jarek.Potiuk@polidea.com>
> > > wrote:
> > >
> > > > We already have "unreleased versions" there and 2.0.0 is there. We
> use
> > > > 2.0.0 when we mark features as resolved in JIRA when we merge in
> > master -
> > > > so that should be perfectly OK to use it,
> > > >
> > > > On Tue, May 28, 2019 at 9:01 PM Aizhamal Nurmamat kyzy
> > > > <ai...@google.com.invalid> wrote:
> > > >
> > > > > One more thing that we missed in discussions: now that the ‘Affects
> > > > > version’ is a required field, how should we file issues that are
> > > > currently
> > > > > in master, but are not in a release? is it possible to add a future
> > > > version
> > > > > to Jira? Or ‘master’ as a version (though it may defeat the
> purpose)?
> > > > >
> > > > > On Tue, May 28, 2019 at 11:57 Jarek Potiuk <
> Jarek.Potiuk@polidea.com
> > >
> > > > > wrote:
> > > > >
> > > > > > All good ! These are required fields now. Thanks for setting this
> > up
> > > > > > Aizhamal.
> > > > > >
> > > > > > On Tue, May 28, 2019 at 8:49 PM Aizhamal Nurmamat kyzy
> > > > > > <ai...@google.com.invalid> wrote:
> > > > > >
> > > > > > > Hello everyone,
> > > > > > >
> > > > > > > `Component` & `Affects version` are required fields when filing
> > > > Airflow
> > > > > > > Jira issues now. Could you please help me test it and confirm
> > that
> > > it
> > > > > is
> > > > > > > working as desired?
> > > > > > >
> > > > > > >
> > > > > > > Thanks
> > > > > > > Aizhamal
> > > > > > >
> > > > > > > On Wed, May 22, 2019 at 11:01 PM Jarek Potiuk <
> > > > > Jarek.Potiuk@polidea.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > I think we indeed need to do some minimal and as automated as
> > > > > possible
> > > > > > > > "triage" process in place and having some JIRA automation
> > around
> > > it
> > > > > > would
> > > > > > > > be great.
> > > > > > > >
> > > > > > > > I think it's something that Ash after he returns from his
> > > holidays
> > > > > > > > mentioned that he would like to take care about - especially
> > with
> > > > the
> > > > > > > > upcoming 2.0 release. With the number of committers we have
> > now,
> > > I
> > > > > > think
> > > > > > > we
> > > > > > > > need to organise it a bit. I am happy to help with discussing
> > the
> > > > > > process
> > > > > > > > and taking part in introducing it.
> > > > > > > >
> > > > > > > > J.
> > > > > > > >
> > > > > > > > On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy
> > > > > > > > <ai...@google.com.invalid> wrote:
> > > > > > > >
> > > > > > > > > Hi Fokko,
> > > > > > > > >
> > > > > > > > > Sid gave me the admin rights yesterday, forgot to update
> > here.
> > > > > Thank
> > > > > > > you.
> > > > > > > > >
> > > > > > > > > I have edited the components themselves, but to make
> > components
> > > > the
> > > > > > > > > required filed I need to ask Infra. I created this ticket
> > [1],
> > > > > still
> > > > > > > > > waiting for it to be resolved.
> > > > > > > > >
> > > > > > > > > Wouldn't it be smarter that users won't tag
> labels/component
> > > > > > > themselves?
> > > > > > > > > > Any new ticket will get "triage" tag and once the
> community
> > > > > review
> > > > > > > the
> > > > > > > > > > request they will set the proper components/priority ?
> > > > > > > > > >
> > > > > > > > > > Users can easily tag the wrong components so it's likely
> > that
> > > > the
> > > > > > > > ordered
> > > > > > > > > > Jira we have now won't stay like this for long.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > Asking users to add the components by themselves may add
> some
> > > > noise
> > > > > > to
> > > > > > > > the
> > > > > > > > > triage process, but it should reduce the workload on
> > > maintainers,
> > > > > > > > triagers,
> > > > > > > > > and others tracking specific areas of the project. Although
> > at
> > > > the
> > > > > > > moment
> > > > > > > > > it's not possible to know for sure if an issue has been
> > triaged
> > > > or
> > > > > > not,
> > > > > > > > we
> > > > > > > > > can move to a process that clearly marks untriaged issues
> as
> > > > such,
> > > > > > and
> > > > > > > > > maintainers will be able to look at an issue, and
> add/remove
> > > any
> > > > > > > > > components/labels if necessary.
> > > > > > > > >
> > > > > > > > > At the moment there are ~400 issues without any components
> > > added.
> > > > > > I’ll
> > > > > > > go
> > > > > > > > > through them and try to give them a component; but this
> sort
> > of
> > > > > > “issue
> > > > > > > > > lake” can easily become forgotten. We also can’t
> ensure/force
> > > > > > > maintainers
> > > > > > > > > to always do triage of issues filed in this lake.
> > > > > > > > >
> > > > > > > > > Another reason to have issues filed with a component is
> > because
> > > > > there
> > > > > > > are
> > > > > > > > > parties that care and track only certain components, and
> for
> > > them
> > > > > it
> > > > > > is
> > > > > > > > > hard to discover all the issues.
> > > > > > > > >
> > > > > > > > > In other apache projects, the triage process relies on a
> Jira
> > > > > > workflow
> > > > > > > > that
> > > > > > > > > goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see
> > > possible
> > > > > > jira
> > > > > > > > > statuses [2]). This automatically marks new issues in a
> > “Triage
> > > > > > Needed”
> > > > > > > > > status. I’d like to discuss this process after we’re done
> > > making
> > > > > the
> > > > > > > > > changes proposed in this document.
> > > > > > > > >
> > > > > > > > > Let me know what you all think.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Aizhamal
> > > > > > > > >
> > > > > > > > > [1] https://issues.apache.org/jira/browse/INFRA-18410
> > > > > > > > > [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > > > > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko
> > > > > > > > > <fo...@driesprong.frl>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Aizhamal,
> > > > > > > > > > >
> > > > > > > > > > > Sorry for the late reply. You're still an administrator
> > on
> > > > the
> > > > > > > Jira.
> > > > > > > > > > Please let me know if you're missing any privileges.
> > > > > > > > > > >
> > > > > > > > > > > Cheers, Fokko
> > > > > > > > > > >
> > > > > > > > > > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat
> kyzy
> > > > > > > > > > <ai...@google.com.invalid>:
> > > > > > > > > > >
> > > > > > > > > > >> Hello everyone,
> > > > > > > > > > >> it took me longer than expected, but I finally got
> > around
> > > to
> > > > > > > making
> > > > > > > > > > these
> > > > > > > > > > >> changes. I've moved all the issues to rightful
> > components
> > > > > > (except
> > > > > > > > for
> > > > > > > > > > those
> > > > > > > > > > >> lacking any component - I'll work on those
> afterwards).
> > > > > > > > > > >> I think I am unable to make changes to the components
> > > > > themselves
> > > > > > > > > > (renames /
> > > > > > > > > > >> deletes). Fokko, or anyone in the PMC, would you be
> able
> > > to
> > > > > > grant
> > > > > > > me
> > > > > > > > > the
> > > > > > > > > > >> privileges once more? My username is aizhamal. I'd
> like
> > to
> > > > do
> > > > > > this
> > > > > > > > as
> > > > > > > > > > soon
> > > > > > > > > > >> as possible, so that I won't have to clean up issues
> > added
> > > > to
> > > > > > > > > components
> > > > > > > > > > >> that are to be removed.
> > > > > > > > > > >>
> > > > > > > > > > >> Thanks a lot! I'll notify you on this thread once I
> have
> > > > done
> > > > > > the
> > > > > > > > > > changes
> > > > > > > > > > >> to components. :)
> > > > > > > > > > >>
> > > > > > > > > > >> Aizhamal
> > > > > > > > > > >>
> > > > > > > > > > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat
> kyzy <
> > > > > > > > > > aizhamal@google.com>
> > > > > > > > > > >> wrote:
> > > > > > > > > > >>
> > > > > > > > > > >>> Thank you for Jira powers, Fokko :) I am aiming to
> get
> > it
> > > > > done
> > > > > > by
> > > > > > > > > > Monday.
> > > > > > > > > > >>>
> > > > > > > > > > >>> Regards,
> > > > > > > > > > >>> Aizhamal
> > > > > > > > > > >>>
> > > > > > > > > > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > > > > > > > > > >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> > > > > > > > > > >>> *To: * <de...@airflow.apache.org>
> > > > > > > > > > >>> *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
> > > > > > > > > > >>>> <ai...@google.com.invalid>:
> > > > > > > > > > >>>>
> > > > > > > > > > >>>> > Hello all,
> > > > > > > > > > >>>> >
> > > > > > > > > > >>>> > If it's okay by everyone, I would like to start
> > > > performing
> > > > > > the
> > > > > > > > > > changes
> > > > > > > > > > >>>> > outlined in the doc. +Siddharth Anand <
> > > > sanand@apache.org>
> > > > > > > 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 <Ja...@polidea.com>
> > > > > > > > > > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > > > > > > > > > >>>> > *To: * <de...@airflow.apache.org>
> > > > > > > > > > >>>> > *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-labels-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
> > > > > > > > > > >>>> > > <ai...@google.com.invalid> 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
> > > > > > > > > > >>>> findability:
> > > > > > > > > > >>>> > 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 is
> > > > > > > > > > >>>> > > > > 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 and
> > > > > > > > > > >>>> > > close
> > > > > > > > > > >>>> > > > those issues more efficiently. Any other
> > thoughts?
> > > > > > > > > > >>>> > > >
> > > > > > > > > > >>>> > > > Best,
> > > > > > > > > > >>>> > > > Aizhamal
> > > > > > > > > > >>>> > > >
> > > > > > > > > > >>>> > > >
> > > > > > > > > > >>>> > > >
> > > > > > > > > > >>>> > > >
> > > > > > > > > > >>>> > > > >
> > > > > > > > > > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > > > > >>>> > > > > 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
> > > > > > > > > > label
> > > > > > > > > > >>>> > 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’t
> > > have
> > > > > one
> > > > > > > at
> > > > > > > > > the
> > > > > > > > > > >>>> moment
> > > > > > > > > > >>>> > > > > > >
> > > > > > > > > > >>>> > > > > > >
> > > > > > > > > > >>>>
> > > > > > >
> -----------------------------------------------------------------
> > > > > > > > > > >>>> > > > > > >
> > > > > > > > > > >>>> > > > > > > Ensure that no new components are
> created
> > > > unless
> > > > > > > it’s
> > > > > > > > > > >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > > > > > > > >>>> > > > > > > [2]
> > > > > > > > > > >>>> > > > > > >
> > > > > > > > > > >>>> > > > >
> > > > > > > > > > >>>> > > >
> > > > > > > > > > >>>> > >
> > > > > > > > > > >>>> >
> > > > > > > > > > >>>>
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > > > > > > > > >>>> > > > >
> > > > > > > > > > >>>> > > > >
> > > > > > > > > > >>>> > > > >
> > > > > > > > > > >>>> > > >
> > > > > > > > > > >>>> > >
> > > > > > > > > > >>>> > >
> > > > > > > > > > >>>> > > --
> > > > > > > > > > >>>> > >
> > > > > > > > > > >>>> > > Jarek Potiuk
> > > > > > > > > > >>>> > > Polidea <https://www.polidea.com/> | Principal
> > > > Software
> > > > > > > > > Engineer
> > > > > > > > > > >>>> > >
> > > > > > > > > > >>>> > > M: +48 660 796 129 <+48660796129>
> > > > > > > > > > >>>> > > E: jarek.potiuk@polidea.com
> > > > > > > > > > >>>> > >
> > > > > > > > > > >>>> >
> > > > > > > > > > >>>>
> > > > > > > > > > >>>
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > Jarek Potiuk
> > > > > > > > Polidea <https://www.polidea.com/> | Principal Software
> > Engineer
> > > > > > > >
> > > > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > > > E: jarek.potiuk@polidea.com
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Jarek Potiuk
> > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > > >
> > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > E: jarek.potiuk@polidea.com
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > E: jarek.potiuk@polidea.com
> > > >
> > >
> >
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
Thanks everyone for your support and help!
I am done with most of the tasks outlined in the document. Over the next
few weeks I will keep going through issues that have no components and try
to add one to them.
Also, I have added descriptions for the components that I know about, but
there are still many without description. It would be great if others could
add them directly in JIRA, or add them in the same document[1] so that PMC
can add that to JIRA.
In the future, we can continue to improve the JIRA workflow, and our
component structure. Some ideas worth considering for later:
- Adding (removing) components that are needed (not needed)
- Have component owners
- Adding prefixes to component names to facilitate filing new issues in the
right components
- Changing the JIRA workflow to better identify issues that need to be
triaged
- etc.
I think we can close this thread now. Thanks again!
Aizhamal
[1]
https://docs.google.com/document/d/1gticSJ7LgD15XHgQhEP78-Ky38Er_NnMlarIvSQ8NYM/edit?usp=sharing
On Tue, May 28, 2019 at 4:44 PM Daniel Imberman <
dimberman.opensource@gmail.com> wrote:
> Hi Aizhamal,
>
> Thank you for taking this on :). I've been looking to add epics recently
> but that's just because I didn't know that components were a thing (they
> make much more sense here).
>
> +1!
>
> Daniel
>
> On Tue, May 28, 2019 at 1:06 PM Aizhamal Nurmamat kyzy
> <ai...@google.com.invalid> wrote:
>
> > Yes, that should work. Thanks Jarek :)
> >
> > On Tue, May 28, 2019 at 12:54 PM Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> > > We already have "unreleased versions" there and 2.0.0 is there. We use
> > > 2.0.0 when we mark features as resolved in JIRA when we merge in
> master -
> > > so that should be perfectly OK to use it,
> > >
> > > On Tue, May 28, 2019 at 9:01 PM Aizhamal Nurmamat kyzy
> > > <ai...@google.com.invalid> wrote:
> > >
> > > > One more thing that we missed in discussions: now that the ‘Affects
> > > > version’ is a required field, how should we file issues that are
> > > currently
> > > > in master, but are not in a release? is it possible to add a future
> > > version
> > > > to Jira? Or ‘master’ as a version (though it may defeat the purpose)?
> > > >
> > > > On Tue, May 28, 2019 at 11:57 Jarek Potiuk <Jarek.Potiuk@polidea.com
> >
> > > > wrote:
> > > >
> > > > > All good ! These are required fields now. Thanks for setting this
> up
> > > > > Aizhamal.
> > > > >
> > > > > On Tue, May 28, 2019 at 8:49 PM Aizhamal Nurmamat kyzy
> > > > > <ai...@google.com.invalid> wrote:
> > > > >
> > > > > > Hello everyone,
> > > > > >
> > > > > > `Component` & `Affects version` are required fields when filing
> > > Airflow
> > > > > > Jira issues now. Could you please help me test it and confirm
> that
> > it
> > > > is
> > > > > > working as desired?
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > > Aizhamal
> > > > > >
> > > > > > On Wed, May 22, 2019 at 11:01 PM Jarek Potiuk <
> > > > Jarek.Potiuk@polidea.com>
> > > > > > wrote:
> > > > > >
> > > > > > > I think we indeed need to do some minimal and as automated as
> > > > possible
> > > > > > > "triage" process in place and having some JIRA automation
> around
> > it
> > > > > would
> > > > > > > be great.
> > > > > > >
> > > > > > > I think it's something that Ash after he returns from his
> > holidays
> > > > > > > mentioned that he would like to take care about - especially
> with
> > > the
> > > > > > > upcoming 2.0 release. With the number of committers we have
> now,
> > I
> > > > > think
> > > > > > we
> > > > > > > need to organise it a bit. I am happy to help with discussing
> the
> > > > > process
> > > > > > > and taking part in introducing it.
> > > > > > >
> > > > > > > J.
> > > > > > >
> > > > > > > On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy
> > > > > > > <ai...@google.com.invalid> wrote:
> > > > > > >
> > > > > > > > Hi Fokko,
> > > > > > > >
> > > > > > > > Sid gave me the admin rights yesterday, forgot to update
> here.
> > > > Thank
> > > > > > you.
> > > > > > > >
> > > > > > > > I have edited the components themselves, but to make
> components
> > > the
> > > > > > > > required filed I need to ask Infra. I created this ticket
> [1],
> > > > still
> > > > > > > > waiting for it to be resolved.
> > > > > > > >
> > > > > > > > Wouldn't it be smarter that users won't tag labels/component
> > > > > > themselves?
> > > > > > > > > Any new ticket will get "triage" tag and once the community
> > > > review
> > > > > > the
> > > > > > > > > request they will set the proper components/priority ?
> > > > > > > > >
> > > > > > > > > Users can easily tag the wrong components so it's likely
> that
> > > the
> > > > > > > ordered
> > > > > > > > > Jira we have now won't stay like this for long.
> > > > > > > > >
> > > > > > > >
> > > > > > > > Asking users to add the components by themselves may add some
> > > noise
> > > > > to
> > > > > > > the
> > > > > > > > triage process, but it should reduce the workload on
> > maintainers,
> > > > > > > triagers,
> > > > > > > > and others tracking specific areas of the project. Although
> at
> > > the
> > > > > > moment
> > > > > > > > it's not possible to know for sure if an issue has been
> triaged
> > > or
> > > > > not,
> > > > > > > we
> > > > > > > > can move to a process that clearly marks untriaged issues as
> > > such,
> > > > > and
> > > > > > > > maintainers will be able to look at an issue, and add/remove
> > any
> > > > > > > > components/labels if necessary.
> > > > > > > >
> > > > > > > > At the moment there are ~400 issues without any components
> > added.
> > > > > I’ll
> > > > > > go
> > > > > > > > through them and try to give them a component; but this sort
> of
> > > > > “issue
> > > > > > > > lake” can easily become forgotten. We also can’t ensure/force
> > > > > > maintainers
> > > > > > > > to always do triage of issues filed in this lake.
> > > > > > > >
> > > > > > > > Another reason to have issues filed with a component is
> because
> > > > there
> > > > > > are
> > > > > > > > parties that care and track only certain components, and for
> > them
> > > > it
> > > > > is
> > > > > > > > hard to discover all the issues.
> > > > > > > >
> > > > > > > > In other apache projects, the triage process relies on a Jira
> > > > > workflow
> > > > > > > that
> > > > > > > > goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see
> > possible
> > > > > jira
> > > > > > > > statuses [2]). This automatically marks new issues in a
> “Triage
> > > > > Needed”
> > > > > > > > status. I’d like to discuss this process after we’re done
> > making
> > > > the
> > > > > > > > changes proposed in this document.
> > > > > > > >
> > > > > > > > Let me know what you all think.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Aizhamal
> > > > > > > >
> > > > > > > > [1] https://issues.apache.org/jira/browse/INFRA-18410
> > > > > > > > [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > > > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko
> > > > > > > > <fo...@driesprong.frl>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi Aizhamal,
> > > > > > > > > >
> > > > > > > > > > Sorry for the late reply. You're still an administrator
> on
> > > the
> > > > > > Jira.
> > > > > > > > > Please let me know if you're missing any privileges.
> > > > > > > > > >
> > > > > > > > > > Cheers, Fokko
> > > > > > > > > >
> > > > > > > > > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
> > > > > > > > > <ai...@google.com.invalid>:
> > > > > > > > > >
> > > > > > > > > >> Hello everyone,
> > > > > > > > > >> it took me longer than expected, but I finally got
> around
> > to
> > > > > > making
> > > > > > > > > these
> > > > > > > > > >> changes. I've moved all the issues to rightful
> components
> > > > > (except
> > > > > > > for
> > > > > > > > > those
> > > > > > > > > >> lacking any component - I'll work on those afterwards).
> > > > > > > > > >> I think I am unable to make changes to the components
> > > > themselves
> > > > > > > > > (renames /
> > > > > > > > > >> deletes). Fokko, or anyone in the PMC, would you be able
> > to
> > > > > grant
> > > > > > me
> > > > > > > > the
> > > > > > > > > >> privileges once more? My username is aizhamal. I'd like
> to
> > > do
> > > > > this
> > > > > > > as
> > > > > > > > > soon
> > > > > > > > > >> as possible, so that I won't have to clean up issues
> added
> > > to
> > > > > > > > components
> > > > > > > > > >> that are to be removed.
> > > > > > > > > >>
> > > > > > > > > >> Thanks a lot! I'll notify you on this thread once I have
> > > done
> > > > > the
> > > > > > > > > changes
> > > > > > > > > >> to components. :)
> > > > > > > > > >>
> > > > > > > > > >> Aizhamal
> > > > > > > > > >>
> > > > > > > > > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> > > > > > > > > aizhamal@google.com>
> > > > > > > > > >> wrote:
> > > > > > > > > >>
> > > > > > > > > >>> Thank you for Jira powers, Fokko :) I am aiming to get
> it
> > > > done
> > > > > by
> > > > > > > > > Monday.
> > > > > > > > > >>>
> > > > > > > > > >>> Regards,
> > > > > > > > > >>> Aizhamal
> > > > > > > > > >>>
> > > > > > > > > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > > > > > > > > >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> > > > > > > > > >>> *To: * <de...@airflow.apache.org>
> > > > > > > > > >>> *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
> > > > > > > > > >>>> <ai...@google.com.invalid>:
> > > > > > > > > >>>>
> > > > > > > > > >>>> > Hello all,
> > > > > > > > > >>>> >
> > > > > > > > > >>>> > If it's okay by everyone, I would like to start
> > > performing
> > > > > the
> > > > > > > > > changes
> > > > > > > > > >>>> > outlined in the doc. +Siddharth Anand <
> > > sanand@apache.org>
> > > > > > 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 <Ja...@polidea.com>
> > > > > > > > > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > > > > > > > > >>>> > *To: * <de...@airflow.apache.org>
> > > > > > > > > >>>> > *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-labels-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
> > > > > > > > > >>>> > > <ai...@google.com.invalid> 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
> > > > > > > > > >>>> findability:
> > > > > > > > > >>>> > 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 is
> > > > > > > > > >>>> > > > > 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 and
> > > > > > > > > >>>> > > close
> > > > > > > > > >>>> > > > those issues more efficiently. Any other
> thoughts?
> > > > > > > > > >>>> > > >
> > > > > > > > > >>>> > > > Best,
> > > > > > > > > >>>> > > > Aizhamal
> > > > > > > > > >>>> > > >
> > > > > > > > > >>>> > > >
> > > > > > > > > >>>> > > >
> > > > > > > > > >>>> > > >
> > > > > > > > > >>>> > > > >
> > > > > > > > > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > > > >>>> > > > > 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
> > > > > > > > > label
> > > > > > > > > >>>> > 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’t
> > have
> > > > one
> > > > > > at
> > > > > > > > the
> > > > > > > > > >>>> moment
> > > > > > > > > >>>> > > > > > >
> > > > > > > > > >>>> > > > > > >
> > > > > > > > > >>>>
> > > > > > -----------------------------------------------------------------
> > > > > > > > > >>>> > > > > > >
> > > > > > > > > >>>> > > > > > > Ensure that no new components are created
> > > unless
> > > > > > it’s
> > > > > > > > > >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > > > > > > >>>> > > > > > > [2]
> > > > > > > > > >>>> > > > > > >
> > > > > > > > > >>>> > > > >
> > > > > > > > > >>>> > > >
> > > > > > > > > >>>> > >
> > > > > > > > > >>>> >
> > > > > > > > > >>>>
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > > > > > > > >>>> > > > >
> > > > > > > > > >>>> > > > >
> > > > > > > > > >>>> > > > >
> > > > > > > > > >>>> > > >
> > > > > > > > > >>>> > >
> > > > > > > > > >>>> > >
> > > > > > > > > >>>> > > --
> > > > > > > > > >>>> > >
> > > > > > > > > >>>> > > Jarek Potiuk
> > > > > > > > > >>>> > > Polidea <https://www.polidea.com/> | Principal
> > > Software
> > > > > > > > Engineer
> > > > > > > > > >>>> > >
> > > > > > > > > >>>> > > M: +48 660 796 129 <+48660796129>
> > > > > > > > > >>>> > > E: jarek.potiuk@polidea.com
> > > > > > > > > >>>> > >
> > > > > > > > > >>>> >
> > > > > > > > > >>>>
> > > > > > > > > >>>
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Jarek Potiuk
> > > > > > > Polidea <https://www.polidea.com/> | Principal Software
> Engineer
> > > > > > >
> > > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > > E: jarek.potiuk@polidea.com
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Jarek Potiuk
> > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > >
> > > > > M: +48 660 796 129 <+48660796129>
> > > > > E: jarek.potiuk@polidea.com
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > E: jarek.potiuk@polidea.com
> > >
> >
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Daniel Imberman <di...@gmail.com>.
Hi Aizhamal,
Thank you for taking this on :). I've been looking to add epics recently
but that's just because I didn't know that components were a thing (they
make much more sense here).
+1!
Daniel
On Tue, May 28, 2019 at 1:06 PM Aizhamal Nurmamat kyzy
<ai...@google.com.invalid> wrote:
> Yes, that should work. Thanks Jarek :)
>
> On Tue, May 28, 2019 at 12:54 PM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > We already have "unreleased versions" there and 2.0.0 is there. We use
> > 2.0.0 when we mark features as resolved in JIRA when we merge in master -
> > so that should be perfectly OK to use it,
> >
> > On Tue, May 28, 2019 at 9:01 PM Aizhamal Nurmamat kyzy
> > <ai...@google.com.invalid> wrote:
> >
> > > One more thing that we missed in discussions: now that the ‘Affects
> > > version’ is a required field, how should we file issues that are
> > currently
> > > in master, but are not in a release? is it possible to add a future
> > version
> > > to Jira? Or ‘master’ as a version (though it may defeat the purpose)?
> > >
> > > On Tue, May 28, 2019 at 11:57 Jarek Potiuk <Ja...@polidea.com>
> > > wrote:
> > >
> > > > All good ! These are required fields now. Thanks for setting this up
> > > > Aizhamal.
> > > >
> > > > On Tue, May 28, 2019 at 8:49 PM Aizhamal Nurmamat kyzy
> > > > <ai...@google.com.invalid> wrote:
> > > >
> > > > > Hello everyone,
> > > > >
> > > > > `Component` & `Affects version` are required fields when filing
> > Airflow
> > > > > Jira issues now. Could you please help me test it and confirm that
> it
> > > is
> > > > > working as desired?
> > > > >
> > > > >
> > > > > Thanks
> > > > > Aizhamal
> > > > >
> > > > > On Wed, May 22, 2019 at 11:01 PM Jarek Potiuk <
> > > Jarek.Potiuk@polidea.com>
> > > > > wrote:
> > > > >
> > > > > > I think we indeed need to do some minimal and as automated as
> > > possible
> > > > > > "triage" process in place and having some JIRA automation around
> it
> > > > would
> > > > > > be great.
> > > > > >
> > > > > > I think it's something that Ash after he returns from his
> holidays
> > > > > > mentioned that he would like to take care about - especially with
> > the
> > > > > > upcoming 2.0 release. With the number of committers we have now,
> I
> > > > think
> > > > > we
> > > > > > need to organise it a bit. I am happy to help with discussing the
> > > > process
> > > > > > and taking part in introducing it.
> > > > > >
> > > > > > J.
> > > > > >
> > > > > > On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy
> > > > > > <ai...@google.com.invalid> wrote:
> > > > > >
> > > > > > > Hi Fokko,
> > > > > > >
> > > > > > > Sid gave me the admin rights yesterday, forgot to update here.
> > > Thank
> > > > > you.
> > > > > > >
> > > > > > > I have edited the components themselves, but to make components
> > the
> > > > > > > required filed I need to ask Infra. I created this ticket [1],
> > > still
> > > > > > > waiting for it to be resolved.
> > > > > > >
> > > > > > > Wouldn't it be smarter that users won't tag labels/component
> > > > > themselves?
> > > > > > > > Any new ticket will get "triage" tag and once the community
> > > review
> > > > > the
> > > > > > > > request they will set the proper components/priority ?
> > > > > > > >
> > > > > > > > Users can easily tag the wrong components so it's likely that
> > the
> > > > > > ordered
> > > > > > > > Jira we have now won't stay like this for long.
> > > > > > > >
> > > > > > >
> > > > > > > Asking users to add the components by themselves may add some
> > noise
> > > > to
> > > > > > the
> > > > > > > triage process, but it should reduce the workload on
> maintainers,
> > > > > > triagers,
> > > > > > > and others tracking specific areas of the project. Although at
> > the
> > > > > moment
> > > > > > > it's not possible to know for sure if an issue has been triaged
> > or
> > > > not,
> > > > > > we
> > > > > > > can move to a process that clearly marks untriaged issues as
> > such,
> > > > and
> > > > > > > maintainers will be able to look at an issue, and add/remove
> any
> > > > > > > components/labels if necessary.
> > > > > > >
> > > > > > > At the moment there are ~400 issues without any components
> added.
> > > > I’ll
> > > > > go
> > > > > > > through them and try to give them a component; but this sort of
> > > > “issue
> > > > > > > lake” can easily become forgotten. We also can’t ensure/force
> > > > > maintainers
> > > > > > > to always do triage of issues filed in this lake.
> > > > > > >
> > > > > > > Another reason to have issues filed with a component is because
> > > there
> > > > > are
> > > > > > > parties that care and track only certain components, and for
> them
> > > it
> > > > is
> > > > > > > hard to discover all the issues.
> > > > > > >
> > > > > > > In other apache projects, the triage process relies on a Jira
> > > > workflow
> > > > > > that
> > > > > > > goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see
> possible
> > > > jira
> > > > > > > statuses [2]). This automatically marks new issues in a “Triage
> > > > Needed”
> > > > > > > status. I’d like to discuss this process after we’re done
> making
> > > the
> > > > > > > changes proposed in this document.
> > > > > > >
> > > > > > > Let me know what you all think.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Aizhamal
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/INFRA-18410
> > > > > > > [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko
> > > > > > > <fo...@driesprong.frl>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Aizhamal,
> > > > > > > > >
> > > > > > > > > Sorry for the late reply. You're still an administrator on
> > the
> > > > > Jira.
> > > > > > > > Please let me know if you're missing any privileges.
> > > > > > > > >
> > > > > > > > > Cheers, Fokko
> > > > > > > > >
> > > > > > > > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
> > > > > > > > <ai...@google.com.invalid>:
> > > > > > > > >
> > > > > > > > >> Hello everyone,
> > > > > > > > >> it took me longer than expected, but I finally got around
> to
> > > > > making
> > > > > > > > these
> > > > > > > > >> changes. I've moved all the issues to rightful components
> > > > (except
> > > > > > for
> > > > > > > > those
> > > > > > > > >> lacking any component - I'll work on those afterwards).
> > > > > > > > >> I think I am unable to make changes to the components
> > > themselves
> > > > > > > > (renames /
> > > > > > > > >> deletes). Fokko, or anyone in the PMC, would you be able
> to
> > > > grant
> > > > > me
> > > > > > > the
> > > > > > > > >> privileges once more? My username is aizhamal. I'd like to
> > do
> > > > this
> > > > > > as
> > > > > > > > soon
> > > > > > > > >> as possible, so that I won't have to clean up issues added
> > to
> > > > > > > components
> > > > > > > > >> that are to be removed.
> > > > > > > > >>
> > > > > > > > >> Thanks a lot! I'll notify you on this thread once I have
> > done
> > > > the
> > > > > > > > changes
> > > > > > > > >> to components. :)
> > > > > > > > >>
> > > > > > > > >> Aizhamal
> > > > > > > > >>
> > > > > > > > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> > > > > > > > aizhamal@google.com>
> > > > > > > > >> wrote:
> > > > > > > > >>
> > > > > > > > >>> Thank you for Jira powers, Fokko :) I am aiming to get it
> > > done
> > > > by
> > > > > > > > Monday.
> > > > > > > > >>>
> > > > > > > > >>> Regards,
> > > > > > > > >>> Aizhamal
> > > > > > > > >>>
> > > > > > > > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > > > > > > > >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> > > > > > > > >>> *To: * <de...@airflow.apache.org>
> > > > > > > > >>> *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
> > > > > > > > >>>> <ai...@google.com.invalid>:
> > > > > > > > >>>>
> > > > > > > > >>>> > Hello all,
> > > > > > > > >>>> >
> > > > > > > > >>>> > If it's okay by everyone, I would like to start
> > performing
> > > > the
> > > > > > > > changes
> > > > > > > > >>>> > outlined in the doc. +Siddharth Anand <
> > sanand@apache.org>
> > > > > 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 <Ja...@polidea.com>
> > > > > > > > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > > > > > > > >>>> > *To: * <de...@airflow.apache.org>
> > > > > > > > >>>> > *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-labels-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
> > > > > > > > >>>> > > <ai...@google.com.invalid> 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
> > > > > > > > >>>> findability:
> > > > > > > > >>>> > 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 is
> > > > > > > > >>>> > > > > 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 and
> > > > > > > > >>>> > > close
> > > > > > > > >>>> > > > those issues more efficiently. Any other thoughts?
> > > > > > > > >>>> > > >
> > > > > > > > >>>> > > > Best,
> > > > > > > > >>>> > > > Aizhamal
> > > > > > > > >>>> > > >
> > > > > > > > >>>> > > >
> > > > > > > > >>>> > > >
> > > > > > > > >>>> > > >
> > > > > > > > >>>> > > > >
> > > > > > > > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > > >>>> > > > > 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
> > > > > > > > label
> > > > > > > > >>>> > 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’t
> have
> > > one
> > > > > at
> > > > > > > the
> > > > > > > > >>>> moment
> > > > > > > > >>>> > > > > > >
> > > > > > > > >>>> > > > > > >
> > > > > > > > >>>>
> > > > > -----------------------------------------------------------------
> > > > > > > > >>>> > > > > > >
> > > > > > > > >>>> > > > > > > Ensure that no new components are created
> > unless
> > > > > it’s
> > > > > > > > >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > > > > > >>>> > > > > > > [2]
> > > > > > > > >>>> > > > > > >
> > > > > > > > >>>> > > > >
> > > > > > > > >>>> > > >
> > > > > > > > >>>> > >
> > > > > > > > >>>> >
> > > > > > > > >>>>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > > > > > > >>>> > > > >
> > > > > > > > >>>> > > > >
> > > > > > > > >>>> > > > >
> > > > > > > > >>>> > > >
> > > > > > > > >>>> > >
> > > > > > > > >>>> > >
> > > > > > > > >>>> > > --
> > > > > > > > >>>> > >
> > > > > > > > >>>> > > Jarek Potiuk
> > > > > > > > >>>> > > Polidea <https://www.polidea.com/> | Principal
> > Software
> > > > > > > Engineer
> > > > > > > > >>>> > >
> > > > > > > > >>>> > > M: +48 660 796 129 <+48660796129>
> > > > > > > > >>>> > > E: jarek.potiuk@polidea.com
> > > > > > > > >>>> > >
> > > > > > > > >>>> >
> > > > > > > > >>>>
> > > > > > > > >>>
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Jarek Potiuk
> > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > > >
> > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > E: jarek.potiuk@polidea.com
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > E: jarek.potiuk@polidea.com
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > E: jarek.potiuk@polidea.com
> >
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
Yes, that should work. Thanks Jarek :)
On Tue, May 28, 2019 at 12:54 PM Jarek Potiuk <Ja...@polidea.com>
wrote:
> We already have "unreleased versions" there and 2.0.0 is there. We use
> 2.0.0 when we mark features as resolved in JIRA when we merge in master -
> so that should be perfectly OK to use it,
>
> On Tue, May 28, 2019 at 9:01 PM Aizhamal Nurmamat kyzy
> <ai...@google.com.invalid> wrote:
>
> > One more thing that we missed in discussions: now that the ‘Affects
> > version’ is a required field, how should we file issues that are
> currently
> > in master, but are not in a release? is it possible to add a future
> version
> > to Jira? Or ‘master’ as a version (though it may defeat the purpose)?
> >
> > On Tue, May 28, 2019 at 11:57 Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> > > All good ! These are required fields now. Thanks for setting this up
> > > Aizhamal.
> > >
> > > On Tue, May 28, 2019 at 8:49 PM Aizhamal Nurmamat kyzy
> > > <ai...@google.com.invalid> wrote:
> > >
> > > > Hello everyone,
> > > >
> > > > `Component` & `Affects version` are required fields when filing
> Airflow
> > > > Jira issues now. Could you please help me test it and confirm that it
> > is
> > > > working as desired?
> > > >
> > > >
> > > > Thanks
> > > > Aizhamal
> > > >
> > > > On Wed, May 22, 2019 at 11:01 PM Jarek Potiuk <
> > Jarek.Potiuk@polidea.com>
> > > > wrote:
> > > >
> > > > > I think we indeed need to do some minimal and as automated as
> > possible
> > > > > "triage" process in place and having some JIRA automation around it
> > > would
> > > > > be great.
> > > > >
> > > > > I think it's something that Ash after he returns from his holidays
> > > > > mentioned that he would like to take care about - especially with
> the
> > > > > upcoming 2.0 release. With the number of committers we have now, I
> > > think
> > > > we
> > > > > need to organise it a bit. I am happy to help with discussing the
> > > process
> > > > > and taking part in introducing it.
> > > > >
> > > > > J.
> > > > >
> > > > > On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy
> > > > > <ai...@google.com.invalid> wrote:
> > > > >
> > > > > > Hi Fokko,
> > > > > >
> > > > > > Sid gave me the admin rights yesterday, forgot to update here.
> > Thank
> > > > you.
> > > > > >
> > > > > > I have edited the components themselves, but to make components
> the
> > > > > > required filed I need to ask Infra. I created this ticket [1],
> > still
> > > > > > waiting for it to be resolved.
> > > > > >
> > > > > > Wouldn't it be smarter that users won't tag labels/component
> > > > themselves?
> > > > > > > Any new ticket will get "triage" tag and once the community
> > review
> > > > the
> > > > > > > request they will set the proper components/priority ?
> > > > > > >
> > > > > > > Users can easily tag the wrong components so it's likely that
> the
> > > > > ordered
> > > > > > > Jira we have now won't stay like this for long.
> > > > > > >
> > > > > >
> > > > > > Asking users to add the components by themselves may add some
> noise
> > > to
> > > > > the
> > > > > > triage process, but it should reduce the workload on maintainers,
> > > > > triagers,
> > > > > > and others tracking specific areas of the project. Although at
> the
> > > > moment
> > > > > > it's not possible to know for sure if an issue has been triaged
> or
> > > not,
> > > > > we
> > > > > > can move to a process that clearly marks untriaged issues as
> such,
> > > and
> > > > > > maintainers will be able to look at an issue, and add/remove any
> > > > > > components/labels if necessary.
> > > > > >
> > > > > > At the moment there are ~400 issues without any components added.
> > > I’ll
> > > > go
> > > > > > through them and try to give them a component; but this sort of
> > > “issue
> > > > > > lake” can easily become forgotten. We also can’t ensure/force
> > > > maintainers
> > > > > > to always do triage of issues filed in this lake.
> > > > > >
> > > > > > Another reason to have issues filed with a component is because
> > there
> > > > are
> > > > > > parties that care and track only certain components, and for them
> > it
> > > is
> > > > > > hard to discover all the issues.
> > > > > >
> > > > > > In other apache projects, the triage process relies on a Jira
> > > workflow
> > > > > that
> > > > > > goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see possible
> > > jira
> > > > > > statuses [2]). This automatically marks new issues in a “Triage
> > > Needed”
> > > > > > status. I’d like to discuss this process after we’re done making
> > the
> > > > > > changes proposed in this document.
> > > > > >
> > > > > > Let me know what you all think.
> > > > > >
> > > > > > Thanks,
> > > > > > Aizhamal
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/INFRA-18410
> > > > > > [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
> > > > > >
> > > > > >
> > > > > >
> > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko
> > > > > > <fo...@driesprong.frl>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Aizhamal,
> > > > > > > >
> > > > > > > > Sorry for the late reply. You're still an administrator on
> the
> > > > Jira.
> > > > > > > Please let me know if you're missing any privileges.
> > > > > > > >
> > > > > > > > Cheers, Fokko
> > > > > > > >
> > > > > > > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
> > > > > > > <ai...@google.com.invalid>:
> > > > > > > >
> > > > > > > >> Hello everyone,
> > > > > > > >> it took me longer than expected, but I finally got around to
> > > > making
> > > > > > > these
> > > > > > > >> changes. I've moved all the issues to rightful components
> > > (except
> > > > > for
> > > > > > > those
> > > > > > > >> lacking any component - I'll work on those afterwards).
> > > > > > > >> I think I am unable to make changes to the components
> > themselves
> > > > > > > (renames /
> > > > > > > >> deletes). Fokko, or anyone in the PMC, would you be able to
> > > grant
> > > > me
> > > > > > the
> > > > > > > >> privileges once more? My username is aizhamal. I'd like to
> do
> > > this
> > > > > as
> > > > > > > soon
> > > > > > > >> as possible, so that I won't have to clean up issues added
> to
> > > > > > components
> > > > > > > >> that are to be removed.
> > > > > > > >>
> > > > > > > >> Thanks a lot! I'll notify you on this thread once I have
> done
> > > the
> > > > > > > changes
> > > > > > > >> to components. :)
> > > > > > > >>
> > > > > > > >> Aizhamal
> > > > > > > >>
> > > > > > > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> > > > > > > aizhamal@google.com>
> > > > > > > >> wrote:
> > > > > > > >>
> > > > > > > >>> Thank you for Jira powers, Fokko :) I am aiming to get it
> > done
> > > by
> > > > > > > Monday.
> > > > > > > >>>
> > > > > > > >>> Regards,
> > > > > > > >>> Aizhamal
> > > > > > > >>>
> > > > > > > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > > > > > > >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> > > > > > > >>> *To: * <de...@airflow.apache.org>
> > > > > > > >>> *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
> > > > > > > >>>> <ai...@google.com.invalid>:
> > > > > > > >>>>
> > > > > > > >>>> > Hello all,
> > > > > > > >>>> >
> > > > > > > >>>> > If it's okay by everyone, I would like to start
> performing
> > > the
> > > > > > > changes
> > > > > > > >>>> > outlined in the doc. +Siddharth Anand <
> sanand@apache.org>
> > > > 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 <Ja...@polidea.com>
> > > > > > > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > > > > > > >>>> > *To: * <de...@airflow.apache.org>
> > > > > > > >>>> > *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-labels-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
> > > > > > > >>>> > > <ai...@google.com.invalid> 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
> > > > > > > >>>> findability:
> > > > > > > >>>> > 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 is
> > > > > > > >>>> > > > > 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 and
> > > > > > > >>>> > > close
> > > > > > > >>>> > > > those issues more efficiently. Any other thoughts?
> > > > > > > >>>> > > >
> > > > > > > >>>> > > > Best,
> > > > > > > >>>> > > > Aizhamal
> > > > > > > >>>> > > >
> > > > > > > >>>> > > >
> > > > > > > >>>> > > >
> > > > > > > >>>> > > >
> > > > > > > >>>> > > > >
> > > > > > > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > >>>> > > > > 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
> > > > > > > label
> > > > > > > >>>> > 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’t have
> > one
> > > > at
> > > > > > the
> > > > > > > >>>> moment
> > > > > > > >>>> > > > > > >
> > > > > > > >>>> > > > > > >
> > > > > > > >>>>
> > > > -----------------------------------------------------------------
> > > > > > > >>>> > > > > > >
> > > > > > > >>>> > > > > > > Ensure that no new components are created
> unless
> > > > it’s
> > > > > > > >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > > > > >>>> > > > > > > [2]
> > > > > > > >>>> > > > > > >
> > > > > > > >>>> > > > >
> > > > > > > >>>> > > >
> > > > > > > >>>> > >
> > > > > > > >>>> >
> > > > > > > >>>>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > > > > > >>>> > > > >
> > > > > > > >>>> > > > >
> > > > > > > >>>> > > > >
> > > > > > > >>>> > > >
> > > > > > > >>>> > >
> > > > > > > >>>> > >
> > > > > > > >>>> > > --
> > > > > > > >>>> > >
> > > > > > > >>>> > > Jarek Potiuk
> > > > > > > >>>> > > Polidea <https://www.polidea.com/> | Principal
> Software
> > > > > > Engineer
> > > > > > > >>>> > >
> > > > > > > >>>> > > M: +48 660 796 129 <+48660796129>
> > > > > > > >>>> > > E: jarek.potiuk@polidea.com
> > > > > > > >>>> > >
> > > > > > > >>>> >
> > > > > > > >>>>
> > > > > > > >>>
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Jarek Potiuk
> > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > >
> > > > > M: +48 660 796 129 <+48660796129>
> > > > > E: jarek.potiuk@polidea.com
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > E: jarek.potiuk@polidea.com
> > >
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> E: jarek.potiuk@polidea.com
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Jarek Potiuk <Ja...@polidea.com>.
We already have "unreleased versions" there and 2.0.0 is there. We use
2.0.0 when we mark features as resolved in JIRA when we merge in master -
so that should be perfectly OK to use it,
On Tue, May 28, 2019 at 9:01 PM Aizhamal Nurmamat kyzy
<ai...@google.com.invalid> wrote:
> One more thing that we missed in discussions: now that the ‘Affects
> version’ is a required field, how should we file issues that are currently
> in master, but are not in a release? is it possible to add a future version
> to Jira? Or ‘master’ as a version (though it may defeat the purpose)?
>
> On Tue, May 28, 2019 at 11:57 Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > All good ! These are required fields now. Thanks for setting this up
> > Aizhamal.
> >
> > On Tue, May 28, 2019 at 8:49 PM Aizhamal Nurmamat kyzy
> > <ai...@google.com.invalid> wrote:
> >
> > > Hello everyone,
> > >
> > > `Component` & `Affects version` are required fields when filing Airflow
> > > Jira issues now. Could you please help me test it and confirm that it
> is
> > > working as desired?
> > >
> > >
> > > Thanks
> > > Aizhamal
> > >
> > > On Wed, May 22, 2019 at 11:01 PM Jarek Potiuk <
> Jarek.Potiuk@polidea.com>
> > > wrote:
> > >
> > > > I think we indeed need to do some minimal and as automated as
> possible
> > > > "triage" process in place and having some JIRA automation around it
> > would
> > > > be great.
> > > >
> > > > I think it's something that Ash after he returns from his holidays
> > > > mentioned that he would like to take care about - especially with the
> > > > upcoming 2.0 release. With the number of committers we have now, I
> > think
> > > we
> > > > need to organise it a bit. I am happy to help with discussing the
> > process
> > > > and taking part in introducing it.
> > > >
> > > > J.
> > > >
> > > > On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy
> > > > <ai...@google.com.invalid> wrote:
> > > >
> > > > > Hi Fokko,
> > > > >
> > > > > Sid gave me the admin rights yesterday, forgot to update here.
> Thank
> > > you.
> > > > >
> > > > > I have edited the components themselves, but to make components the
> > > > > required filed I need to ask Infra. I created this ticket [1],
> still
> > > > > waiting for it to be resolved.
> > > > >
> > > > > Wouldn't it be smarter that users won't tag labels/component
> > > themselves?
> > > > > > Any new ticket will get "triage" tag and once the community
> review
> > > the
> > > > > > request they will set the proper components/priority ?
> > > > > >
> > > > > > Users can easily tag the wrong components so it's likely that the
> > > > ordered
> > > > > > Jira we have now won't stay like this for long.
> > > > > >
> > > > >
> > > > > Asking users to add the components by themselves may add some noise
> > to
> > > > the
> > > > > triage process, but it should reduce the workload on maintainers,
> > > > triagers,
> > > > > and others tracking specific areas of the project. Although at the
> > > moment
> > > > > it's not possible to know for sure if an issue has been triaged or
> > not,
> > > > we
> > > > > can move to a process that clearly marks untriaged issues as such,
> > and
> > > > > maintainers will be able to look at an issue, and add/remove any
> > > > > components/labels if necessary.
> > > > >
> > > > > At the moment there are ~400 issues without any components added.
> > I’ll
> > > go
> > > > > through them and try to give them a component; but this sort of
> > “issue
> > > > > lake” can easily become forgotten. We also can’t ensure/force
> > > maintainers
> > > > > to always do triage of issues filed in this lake.
> > > > >
> > > > > Another reason to have issues filed with a component is because
> there
> > > are
> > > > > parties that care and track only certain components, and for them
> it
> > is
> > > > > hard to discover all the issues.
> > > > >
> > > > > In other apache projects, the triage process relies on a Jira
> > workflow
> > > > that
> > > > > goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see possible
> > jira
> > > > > statuses [2]). This automatically marks new issues in a “Triage
> > Needed”
> > > > > status. I’d like to discuss this process after we’re done making
> the
> > > > > changes proposed in this document.
> > > > >
> > > > > Let me know what you all think.
> > > > >
> > > > > Thanks,
> > > > > Aizhamal
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/INFRA-18410
> > > > > [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
> > > > >
> > > > >
> > > > >
> > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko
> > > > > <fo...@driesprong.frl>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Aizhamal,
> > > > > > >
> > > > > > > Sorry for the late reply. You're still an administrator on the
> > > Jira.
> > > > > > Please let me know if you're missing any privileges.
> > > > > > >
> > > > > > > Cheers, Fokko
> > > > > > >
> > > > > > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
> > > > > > <ai...@google.com.invalid>:
> > > > > > >
> > > > > > >> Hello everyone,
> > > > > > >> it took me longer than expected, but I finally got around to
> > > making
> > > > > > these
> > > > > > >> changes. I've moved all the issues to rightful components
> > (except
> > > > for
> > > > > > those
> > > > > > >> lacking any component - I'll work on those afterwards).
> > > > > > >> I think I am unable to make changes to the components
> themselves
> > > > > > (renames /
> > > > > > >> deletes). Fokko, or anyone in the PMC, would you be able to
> > grant
> > > me
> > > > > the
> > > > > > >> privileges once more? My username is aizhamal. I'd like to do
> > this
> > > > as
> > > > > > soon
> > > > > > >> as possible, so that I won't have to clean up issues added to
> > > > > components
> > > > > > >> that are to be removed.
> > > > > > >>
> > > > > > >> Thanks a lot! I'll notify you on this thread once I have done
> > the
> > > > > > changes
> > > > > > >> to components. :)
> > > > > > >>
> > > > > > >> Aizhamal
> > > > > > >>
> > > > > > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> > > > > > aizhamal@google.com>
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >>> Thank you for Jira powers, Fokko :) I am aiming to get it
> done
> > by
> > > > > > Monday.
> > > > > > >>>
> > > > > > >>> Regards,
> > > > > > >>> Aizhamal
> > > > > > >>>
> > > > > > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > > > > > >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> > > > > > >>> *To: * <de...@airflow.apache.org>
> > > > > > >>> *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
> > > > > > >>>> <ai...@google.com.invalid>:
> > > > > > >>>>
> > > > > > >>>> > Hello all,
> > > > > > >>>> >
> > > > > > >>>> > If it's okay by everyone, I would like to start performing
> > the
> > > > > > changes
> > > > > > >>>> > outlined in the doc. +Siddharth Anand <sa...@apache.org>
> > > 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 <Ja...@polidea.com>
> > > > > > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > > > > > >>>> > *To: * <de...@airflow.apache.org>
> > > > > > >>>> > *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-labels-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
> > > > > > >>>> > > <ai...@google.com.invalid> 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
> > > > > > >>>> findability:
> > > > > > >>>> > 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 is
> > > > > > >>>> > > > > 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 and
> > > > > > >>>> > > close
> > > > > > >>>> > > > those issues more efficiently. Any other thoughts?
> > > > > > >>>> > > >
> > > > > > >>>> > > > Best,
> > > > > > >>>> > > > Aizhamal
> > > > > > >>>> > > >
> > > > > > >>>> > > >
> > > > > > >>>> > > >
> > > > > > >>>> > > >
> > > > > > >>>> > > > >
> > > > > > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > >>>> > > > > 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
> > > > > > label
> > > > > > >>>> > 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’t have
> one
> > > at
> > > > > the
> > > > > > >>>> moment
> > > > > > >>>> > > > > > >
> > > > > > >>>> > > > > > >
> > > > > > >>>>
> > > -----------------------------------------------------------------
> > > > > > >>>> > > > > > >
> > > > > > >>>> > > > > > > Ensure that no new components are created unless
> > > it’s
> > > > > > >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > > > >>>> > > > > > > [2]
> > > > > > >>>> > > > > > >
> > > > > > >>>> > > > >
> > > > > > >>>> > > >
> > > > > > >>>> > >
> > > > > > >>>> >
> > > > > > >>>>
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > > > > >>>> > > > >
> > > > > > >>>> > > > >
> > > > > > >>>> > > > >
> > > > > > >>>> > > >
> > > > > > >>>> > >
> > > > > > >>>> > >
> > > > > > >>>> > > --
> > > > > > >>>> > >
> > > > > > >>>> > > Jarek Potiuk
> > > > > > >>>> > > Polidea <https://www.polidea.com/> | Principal Software
> > > > > Engineer
> > > > > > >>>> > >
> > > > > > >>>> > > M: +48 660 796 129 <+48660796129>
> > > > > > >>>> > > E: jarek.potiuk@polidea.com
> > > > > > >>>> > >
> > > > > > >>>> >
> > > > > > >>>>
> > > > > > >>>
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > E: jarek.potiuk@polidea.com
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > E: jarek.potiuk@polidea.com
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
E: jarek.potiuk@polidea.com
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
One more thing that we missed in discussions: now that the ‘Affects
version’ is a required field, how should we file issues that are currently
in master, but are not in a release? is it possible to add a future version
to Jira? Or ‘master’ as a version (though it may defeat the purpose)?
On Tue, May 28, 2019 at 11:57 Jarek Potiuk <Ja...@polidea.com> wrote:
> All good ! These are required fields now. Thanks for setting this up
> Aizhamal.
>
> On Tue, May 28, 2019 at 8:49 PM Aizhamal Nurmamat kyzy
> <ai...@google.com.invalid> wrote:
>
> > Hello everyone,
> >
> > `Component` & `Affects version` are required fields when filing Airflow
> > Jira issues now. Could you please help me test it and confirm that it is
> > working as desired?
> >
> >
> > Thanks
> > Aizhamal
> >
> > On Wed, May 22, 2019 at 11:01 PM Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> > > I think we indeed need to do some minimal and as automated as possible
> > > "triage" process in place and having some JIRA automation around it
> would
> > > be great.
> > >
> > > I think it's something that Ash after he returns from his holidays
> > > mentioned that he would like to take care about - especially with the
> > > upcoming 2.0 release. With the number of committers we have now, I
> think
> > we
> > > need to organise it a bit. I am happy to help with discussing the
> process
> > > and taking part in introducing it.
> > >
> > > J.
> > >
> > > On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy
> > > <ai...@google.com.invalid> wrote:
> > >
> > > > Hi Fokko,
> > > >
> > > > Sid gave me the admin rights yesterday, forgot to update here. Thank
> > you.
> > > >
> > > > I have edited the components themselves, but to make components the
> > > > required filed I need to ask Infra. I created this ticket [1], still
> > > > waiting for it to be resolved.
> > > >
> > > > Wouldn't it be smarter that users won't tag labels/component
> > themselves?
> > > > > Any new ticket will get "triage" tag and once the community review
> > the
> > > > > request they will set the proper components/priority ?
> > > > >
> > > > > Users can easily tag the wrong components so it's likely that the
> > > ordered
> > > > > Jira we have now won't stay like this for long.
> > > > >
> > > >
> > > > Asking users to add the components by themselves may add some noise
> to
> > > the
> > > > triage process, but it should reduce the workload on maintainers,
> > > triagers,
> > > > and others tracking specific areas of the project. Although at the
> > moment
> > > > it's not possible to know for sure if an issue has been triaged or
> not,
> > > we
> > > > can move to a process that clearly marks untriaged issues as such,
> and
> > > > maintainers will be able to look at an issue, and add/remove any
> > > > components/labels if necessary.
> > > >
> > > > At the moment there are ~400 issues without any components added.
> I’ll
> > go
> > > > through them and try to give them a component; but this sort of
> “issue
> > > > lake” can easily become forgotten. We also can’t ensure/force
> > maintainers
> > > > to always do triage of issues filed in this lake.
> > > >
> > > > Another reason to have issues filed with a component is because there
> > are
> > > > parties that care and track only certain components, and for them it
> is
> > > > hard to discover all the issues.
> > > >
> > > > In other apache projects, the triage process relies on a Jira
> workflow
> > > that
> > > > goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see possible
> jira
> > > > statuses [2]). This automatically marks new issues in a “Triage
> Needed”
> > > > status. I’d like to discuss this process after we’re done making the
> > > > changes proposed in this document.
> > > >
> > > > Let me know what you all think.
> > > >
> > > > Thanks,
> > > > Aizhamal
> > > >
> > > > [1] https://issues.apache.org/jira/browse/INFRA-18410
> > > > [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
> > > >
> > > >
> > > >
> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko
> > > > <fo...@driesprong.frl>
> > > > > wrote:
> > > > >
> > > > > > Hi Aizhamal,
> > > > > >
> > > > > > Sorry for the late reply. You're still an administrator on the
> > Jira.
> > > > > Please let me know if you're missing any privileges.
> > > > > >
> > > > > > Cheers, Fokko
> > > > > >
> > > > > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
> > > > > <ai...@google.com.invalid>:
> > > > > >
> > > > > >> Hello everyone,
> > > > > >> it took me longer than expected, but I finally got around to
> > making
> > > > > these
> > > > > >> changes. I've moved all the issues to rightful components
> (except
> > > for
> > > > > those
> > > > > >> lacking any component - I'll work on those afterwards).
> > > > > >> I think I am unable to make changes to the components themselves
> > > > > (renames /
> > > > > >> deletes). Fokko, or anyone in the PMC, would you be able to
> grant
> > me
> > > > the
> > > > > >> privileges once more? My username is aizhamal. I'd like to do
> this
> > > as
> > > > > soon
> > > > > >> as possible, so that I won't have to clean up issues added to
> > > > components
> > > > > >> that are to be removed.
> > > > > >>
> > > > > >> Thanks a lot! I'll notify you on this thread once I have done
> the
> > > > > changes
> > > > > >> to components. :)
> > > > > >>
> > > > > >> Aizhamal
> > > > > >>
> > > > > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> > > > > aizhamal@google.com>
> > > > > >> wrote:
> > > > > >>
> > > > > >>> Thank you for Jira powers, Fokko :) I am aiming to get it done
> by
> > > > > Monday.
> > > > > >>>
> > > > > >>> Regards,
> > > > > >>> Aizhamal
> > > > > >>>
> > > > > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > > > > >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> > > > > >>> *To: * <de...@airflow.apache.org>
> > > > > >>> *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
> > > > > >>>> <ai...@google.com.invalid>:
> > > > > >>>>
> > > > > >>>> > Hello all,
> > > > > >>>> >
> > > > > >>>> > If it's okay by everyone, I would like to start performing
> the
> > > > > changes
> > > > > >>>> > outlined in the doc. +Siddharth Anand <sa...@apache.org>
> > 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 <Ja...@polidea.com>
> > > > > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > > > > >>>> > *To: * <de...@airflow.apache.org>
> > > > > >>>> > *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-labels-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
> > > > > >>>> > > <ai...@google.com.invalid> 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
> > > > > >>>> findability:
> > > > > >>>> > 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 is
> > > > > >>>> > > > > 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 and
> > > > > >>>> > > close
> > > > > >>>> > > > those issues more efficiently. Any other thoughts?
> > > > > >>>> > > >
> > > > > >>>> > > > Best,
> > > > > >>>> > > > Aizhamal
> > > > > >>>> > > >
> > > > > >>>> > > >
> > > > > >>>> > > >
> > > > > >>>> > > >
> > > > > >>>> > > > >
> > > > > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > >>>> > > > > 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
> > > > > label
> > > > > >>>> > 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’t have one
> > at
> > > > the
> > > > > >>>> moment
> > > > > >>>> > > > > > >
> > > > > >>>> > > > > > >
> > > > > >>>>
> > -----------------------------------------------------------------
> > > > > >>>> > > > > > >
> > > > > >>>> > > > > > > Ensure that no new components are created unless
> > it’s
> > > > > >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > > >>>> > > > > > > [2]
> > > > > >>>> > > > > > >
> > > > > >>>> > > > >
> > > > > >>>> > > >
> > > > > >>>> > >
> > > > > >>>> >
> > > > > >>>>
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > > > >>>> > > > >
> > > > > >>>> > > > >
> > > > > >>>> > > > >
> > > > > >>>> > > >
> > > > > >>>> > >
> > > > > >>>> > >
> > > > > >>>> > > --
> > > > > >>>> > >
> > > > > >>>> > > Jarek Potiuk
> > > > > >>>> > > Polidea <https://www.polidea.com/> | Principal Software
> > > > Engineer
> > > > > >>>> > >
> > > > > >>>> > > M: +48 660 796 129 <+48660796129>
> > > > > >>>> > > E: jarek.potiuk@polidea.com
> > > > > >>>> > >
> > > > > >>>> >
> > > > > >>>>
> > > > > >>>
> > > >
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > E: jarek.potiuk@polidea.com
> > >
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> E: jarek.potiuk@polidea.com
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Jarek Potiuk <Ja...@polidea.com>.
All good ! These are required fields now. Thanks for setting this up
Aizhamal.
On Tue, May 28, 2019 at 8:49 PM Aizhamal Nurmamat kyzy
<ai...@google.com.invalid> wrote:
> Hello everyone,
>
> `Component` & `Affects version` are required fields when filing Airflow
> Jira issues now. Could you please help me test it and confirm that it is
> working as desired?
>
>
> Thanks
> Aizhamal
>
> On Wed, May 22, 2019 at 11:01 PM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > I think we indeed need to do some minimal and as automated as possible
> > "triage" process in place and having some JIRA automation around it would
> > be great.
> >
> > I think it's something that Ash after he returns from his holidays
> > mentioned that he would like to take care about - especially with the
> > upcoming 2.0 release. With the number of committers we have now, I think
> we
> > need to organise it a bit. I am happy to help with discussing the process
> > and taking part in introducing it.
> >
> > J.
> >
> > On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy
> > <ai...@google.com.invalid> wrote:
> >
> > > Hi Fokko,
> > >
> > > Sid gave me the admin rights yesterday, forgot to update here. Thank
> you.
> > >
> > > I have edited the components themselves, but to make components the
> > > required filed I need to ask Infra. I created this ticket [1], still
> > > waiting for it to be resolved.
> > >
> > > Wouldn't it be smarter that users won't tag labels/component
> themselves?
> > > > Any new ticket will get "triage" tag and once the community review
> the
> > > > request they will set the proper components/priority ?
> > > >
> > > > Users can easily tag the wrong components so it's likely that the
> > ordered
> > > > Jira we have now won't stay like this for long.
> > > >
> > >
> > > Asking users to add the components by themselves may add some noise to
> > the
> > > triage process, but it should reduce the workload on maintainers,
> > triagers,
> > > and others tracking specific areas of the project. Although at the
> moment
> > > it's not possible to know for sure if an issue has been triaged or not,
> > we
> > > can move to a process that clearly marks untriaged issues as such, and
> > > maintainers will be able to look at an issue, and add/remove any
> > > components/labels if necessary.
> > >
> > > At the moment there are ~400 issues without any components added. I’ll
> go
> > > through them and try to give them a component; but this sort of “issue
> > > lake” can easily become forgotten. We also can’t ensure/force
> maintainers
> > > to always do triage of issues filed in this lake.
> > >
> > > Another reason to have issues filed with a component is because there
> are
> > > parties that care and track only certain components, and for them it is
> > > hard to discover all the issues.
> > >
> > > In other apache projects, the triage process relies on a Jira workflow
> > that
> > > goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see possible jira
> > > statuses [2]). This automatically marks new issues in a “Triage Needed”
> > > status. I’d like to discuss this process after we’re done making the
> > > changes proposed in this document.
> > >
> > > Let me know what you all think.
> > >
> > > Thanks,
> > > Aizhamal
> > >
> > > [1] https://issues.apache.org/jira/browse/INFRA-18410
> > > [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
> > >
> > >
> > >
> > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko
> > > <fo...@driesprong.frl>
> > > > wrote:
> > > >
> > > > > Hi Aizhamal,
> > > > >
> > > > > Sorry for the late reply. You're still an administrator on the
> Jira.
> > > > Please let me know if you're missing any privileges.
> > > > >
> > > > > Cheers, Fokko
> > > > >
> > > > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
> > > > <ai...@google.com.invalid>:
> > > > >
> > > > >> Hello everyone,
> > > > >> it took me longer than expected, but I finally got around to
> making
> > > > these
> > > > >> changes. I've moved all the issues to rightful components (except
> > for
> > > > those
> > > > >> lacking any component - I'll work on those afterwards).
> > > > >> I think I am unable to make changes to the components themselves
> > > > (renames /
> > > > >> deletes). Fokko, or anyone in the PMC, would you be able to grant
> me
> > > the
> > > > >> privileges once more? My username is aizhamal. I'd like to do this
> > as
> > > > soon
> > > > >> as possible, so that I won't have to clean up issues added to
> > > components
> > > > >> that are to be removed.
> > > > >>
> > > > >> Thanks a lot! I'll notify you on this thread once I have done the
> > > > changes
> > > > >> to components. :)
> > > > >>
> > > > >> Aizhamal
> > > > >>
> > > > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> > > > aizhamal@google.com>
> > > > >> wrote:
> > > > >>
> > > > >>> Thank you for Jira powers, Fokko :) I am aiming to get it done by
> > > > Monday.
> > > > >>>
> > > > >>> Regards,
> > > > >>> Aizhamal
> > > > >>>
> > > > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > > > >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> > > > >>> *To: * <de...@airflow.apache.org>
> > > > >>> *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
> > > > >>>> <ai...@google.com.invalid>:
> > > > >>>>
> > > > >>>> > Hello all,
> > > > >>>> >
> > > > >>>> > If it's okay by everyone, I would like to start performing the
> > > > changes
> > > > >>>> > outlined in the doc. +Siddharth Anand <sa...@apache.org>
> 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 <Ja...@polidea.com>
> > > > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > > > >>>> > *To: * <de...@airflow.apache.org>
> > > > >>>> > *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-labels-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
> > > > >>>> > > <ai...@google.com.invalid> 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
> > > > >>>> findability:
> > > > >>>> > 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 is
> > > > >>>> > > > > 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 and
> > > > >>>> > > close
> > > > >>>> > > > those issues more efficiently. Any other thoughts?
> > > > >>>> > > >
> > > > >>>> > > > Best,
> > > > >>>> > > > Aizhamal
> > > > >>>> > > >
> > > > >>>> > > >
> > > > >>>> > > >
> > > > >>>> > > >
> > > > >>>> > > > >
> > > > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > >>>> > > > > 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
> > > > label
> > > > >>>> > 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’t have one
> at
> > > the
> > > > >>>> moment
> > > > >>>> > > > > > >
> > > > >>>> > > > > > >
> > > > >>>>
> -----------------------------------------------------------------
> > > > >>>> > > > > > >
> > > > >>>> > > > > > > Ensure that no new components are created unless
> it’s
> > > > >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > >>>> > > > > > > [2]
> > > > >>>> > > > > > >
> > > > >>>> > > > >
> > > > >>>> > > >
> > > > >>>> > >
> > > > >>>> >
> > > > >>>>
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > > >>>> > > > >
> > > > >>>> > > > >
> > > > >>>> > > > >
> > > > >>>> > > >
> > > > >>>> > >
> > > > >>>> > >
> > > > >>>> > > --
> > > > >>>> > >
> > > > >>>> > > Jarek Potiuk
> > > > >>>> > > Polidea <https://www.polidea.com/> | Principal Software
> > > Engineer
> > > > >>>> > >
> > > > >>>> > > M: +48 660 796 129 <+48660796129>
> > > > >>>> > > E: jarek.potiuk@polidea.com
> > > > >>>> > >
> > > > >>>> >
> > > > >>>>
> > > > >>>
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > E: jarek.potiuk@polidea.com
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
E: jarek.potiuk@polidea.com
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
Hello everyone,
`Component` & `Affects version` are required fields when filing Airflow
Jira issues now. Could you please help me test it and confirm that it is
working as desired?
Thanks
Aizhamal
On Wed, May 22, 2019 at 11:01 PM Jarek Potiuk <Ja...@polidea.com>
wrote:
> I think we indeed need to do some minimal and as automated as possible
> "triage" process in place and having some JIRA automation around it would
> be great.
>
> I think it's something that Ash after he returns from his holidays
> mentioned that he would like to take care about - especially with the
> upcoming 2.0 release. With the number of committers we have now, I think we
> need to organise it a bit. I am happy to help with discussing the process
> and taking part in introducing it.
>
> J.
>
> On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy
> <ai...@google.com.invalid> wrote:
>
> > Hi Fokko,
> >
> > Sid gave me the admin rights yesterday, forgot to update here. Thank you.
> >
> > I have edited the components themselves, but to make components the
> > required filed I need to ask Infra. I created this ticket [1], still
> > waiting for it to be resolved.
> >
> > Wouldn't it be smarter that users won't tag labels/component themselves?
> > > Any new ticket will get "triage" tag and once the community review the
> > > request they will set the proper components/priority ?
> > >
> > > Users can easily tag the wrong components so it's likely that the
> ordered
> > > Jira we have now won't stay like this for long.
> > >
> >
> > Asking users to add the components by themselves may add some noise to
> the
> > triage process, but it should reduce the workload on maintainers,
> triagers,
> > and others tracking specific areas of the project. Although at the moment
> > it's not possible to know for sure if an issue has been triaged or not,
> we
> > can move to a process that clearly marks untriaged issues as such, and
> > maintainers will be able to look at an issue, and add/remove any
> > components/labels if necessary.
> >
> > At the moment there are ~400 issues without any components added. I’ll go
> > through them and try to give them a component; but this sort of “issue
> > lake” can easily become forgotten. We also can’t ensure/force maintainers
> > to always do triage of issues filed in this lake.
> >
> > Another reason to have issues filed with a component is because there are
> > parties that care and track only certain components, and for them it is
> > hard to discover all the issues.
> >
> > In other apache projects, the triage process relies on a Jira workflow
> that
> > goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see possible jira
> > statuses [2]). This automatically marks new issues in a “Triage Needed”
> > status. I’d like to discuss this process after we’re done making the
> > changes proposed in this document.
> >
> > Let me know what you all think.
> >
> > Thanks,
> > Aizhamal
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-18410
> > [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
> >
> >
> >
> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko
> > <fo...@driesprong.frl>
> > > wrote:
> > >
> > > > Hi Aizhamal,
> > > >
> > > > Sorry for the late reply. You're still an administrator on the Jira.
> > > Please let me know if you're missing any privileges.
> > > >
> > > > Cheers, Fokko
> > > >
> > > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
> > > <ai...@google.com.invalid>:
> > > >
> > > >> Hello everyone,
> > > >> it took me longer than expected, but I finally got around to making
> > > these
> > > >> changes. I've moved all the issues to rightful components (except
> for
> > > those
> > > >> lacking any component - I'll work on those afterwards).
> > > >> I think I am unable to make changes to the components themselves
> > > (renames /
> > > >> deletes). Fokko, or anyone in the PMC, would you be able to grant me
> > the
> > > >> privileges once more? My username is aizhamal. I'd like to do this
> as
> > > soon
> > > >> as possible, so that I won't have to clean up issues added to
> > components
> > > >> that are to be removed.
> > > >>
> > > >> Thanks a lot! I'll notify you on this thread once I have done the
> > > changes
> > > >> to components. :)
> > > >>
> > > >> Aizhamal
> > > >>
> > > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> > > aizhamal@google.com>
> > > >> wrote:
> > > >>
> > > >>> Thank you for Jira powers, Fokko :) I am aiming to get it done by
> > > Monday.
> > > >>>
> > > >>> Regards,
> > > >>> Aizhamal
> > > >>>
> > > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > > >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> > > >>> *To: * <de...@airflow.apache.org>
> > > >>> *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
> > > >>>> <ai...@google.com.invalid>:
> > > >>>>
> > > >>>> > Hello all,
> > > >>>> >
> > > >>>> > If it's okay by everyone, I would like to start performing the
> > > changes
> > > >>>> > outlined in the doc. +Siddharth Anand <sa...@apache.org> 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 <Ja...@polidea.com>
> > > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > > >>>> > *To: * <de...@airflow.apache.org>
> > > >>>> > *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-labels-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
> > > >>>> > > <ai...@google.com.invalid> 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
> > > >>>> findability:
> > > >>>> > 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 is
> > > >>>> > > > > 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 and
> > > >>>> > > close
> > > >>>> > > > those issues more efficiently. Any other thoughts?
> > > >>>> > > >
> > > >>>> > > > Best,
> > > >>>> > > > Aizhamal
> > > >>>> > > >
> > > >>>> > > >
> > > >>>> > > >
> > > >>>> > > >
> > > >>>> > > > >
> > > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > >>>> > > > > 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
> > > label
> > > >>>> > 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’t have one at
> > the
> > > >>>> moment
> > > >>>> > > > > > >
> > > >>>> > > > > > >
> > > >>>> -----------------------------------------------------------------
> > > >>>> > > > > > >
> > > >>>> > > > > > > Ensure that no new components are created unless it’s
> > > >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > >>>> > > > > > > [2]
> > > >>>> > > > > > >
> > > >>>> > > > >
> > > >>>> > > >
> > > >>>> > >
> > > >>>> >
> > > >>>>
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > >>>> > > > >
> > > >>>> > > > >
> > > >>>> > > > >
> > > >>>> > > >
> > > >>>> > >
> > > >>>> > >
> > > >>>> > > --
> > > >>>> > >
> > > >>>> > > Jarek Potiuk
> > > >>>> > > Polidea <https://www.polidea.com/> | Principal Software
> > Engineer
> > > >>>> > >
> > > >>>> > > M: +48 660 796 129 <+48660796129>
> > > >>>> > > E: jarek.potiuk@polidea.com
> > > >>>> > >
> > > >>>> >
> > > >>>>
> > > >>>
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> E: jarek.potiuk@polidea.com
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Jarek Potiuk <Ja...@polidea.com>.
I think we indeed need to do some minimal and as automated as possible
"triage" process in place and having some JIRA automation around it would
be great.
I think it's something that Ash after he returns from his holidays
mentioned that he would like to take care about - especially with the
upcoming 2.0 release. With the number of committers we have now, I think we
need to organise it a bit. I am happy to help with discussing the process
and taking part in introducing it.
J.
On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy
<ai...@google.com.invalid> wrote:
> Hi Fokko,
>
> Sid gave me the admin rights yesterday, forgot to update here. Thank you.
>
> I have edited the components themselves, but to make components the
> required filed I need to ask Infra. I created this ticket [1], still
> waiting for it to be resolved.
>
> Wouldn't it be smarter that users won't tag labels/component themselves?
> > Any new ticket will get "triage" tag and once the community review the
> > request they will set the proper components/priority ?
> >
> > Users can easily tag the wrong components so it's likely that the ordered
> > Jira we have now won't stay like this for long.
> >
>
> Asking users to add the components by themselves may add some noise to the
> triage process, but it should reduce the workload on maintainers, triagers,
> and others tracking specific areas of the project. Although at the moment
> it's not possible to know for sure if an issue has been triaged or not, we
> can move to a process that clearly marks untriaged issues as such, and
> maintainers will be able to look at an issue, and add/remove any
> components/labels if necessary.
>
> At the moment there are ~400 issues without any components added. I’ll go
> through them and try to give them a component; but this sort of “issue
> lake” can easily become forgotten. We also can’t ensure/force maintainers
> to always do triage of issues filed in this lake.
>
> Another reason to have issues filed with a component is because there are
> parties that care and track only certain components, and for them it is
> hard to discover all the issues.
>
> In other apache projects, the triage process relies on a Jira workflow that
> goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see possible jira
> statuses [2]). This automatically marks new issues in a “Triage Needed”
> status. I’d like to discuss this process after we’re done making the
> changes proposed in this document.
>
> Let me know what you all think.
>
> Thanks,
> Aizhamal
>
> [1] https://issues.apache.org/jira/browse/INFRA-18410
> [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
>
>
>
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko
> <fo...@driesprong.frl>
> > wrote:
> >
> > > Hi Aizhamal,
> > >
> > > Sorry for the late reply. You're still an administrator on the Jira.
> > Please let me know if you're missing any privileges.
> > >
> > > Cheers, Fokko
> > >
> > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
> > <ai...@google.com.invalid>:
> > >
> > >> Hello everyone,
> > >> it took me longer than expected, but I finally got around to making
> > these
> > >> changes. I've moved all the issues to rightful components (except for
> > those
> > >> lacking any component - I'll work on those afterwards).
> > >> I think I am unable to make changes to the components themselves
> > (renames /
> > >> deletes). Fokko, or anyone in the PMC, would you be able to grant me
> the
> > >> privileges once more? My username is aizhamal. I'd like to do this as
> > soon
> > >> as possible, so that I won't have to clean up issues added to
> components
> > >> that are to be removed.
> > >>
> > >> Thanks a lot! I'll notify you on this thread once I have done the
> > changes
> > >> to components. :)
> > >>
> > >> Aizhamal
> > >>
> > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> > aizhamal@google.com>
> > >> wrote:
> > >>
> > >>> Thank you for Jira powers, Fokko :) I am aiming to get it done by
> > Monday.
> > >>>
> > >>> Regards,
> > >>> Aizhamal
> > >>>
> > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> > >>> *To: * <de...@airflow.apache.org>
> > >>> *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
> > >>>> <ai...@google.com.invalid>:
> > >>>>
> > >>>> > Hello all,
> > >>>> >
> > >>>> > If it's okay by everyone, I would like to start performing the
> > changes
> > >>>> > outlined in the doc. +Siddharth Anand <sa...@apache.org> 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 <Ja...@polidea.com>
> > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > >>>> > *To: * <de...@airflow.apache.org>
> > >>>> > *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-labels-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
> > >>>> > > <ai...@google.com.invalid> 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
> > >>>> findability:
> > >>>> > 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 is
> > >>>> > > > > 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 and
> > >>>> > > close
> > >>>> > > > those issues more efficiently. Any other thoughts?
> > >>>> > > >
> > >>>> > > > Best,
> > >>>> > > > Aizhamal
> > >>>> > > >
> > >>>> > > >
> > >>>> > > >
> > >>>> > > >
> > >>>> > > > >
> > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > >>>> > > > > 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
> > label
> > >>>> > 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’t have one at
> the
> > >>>> moment
> > >>>> > > > > > >
> > >>>> > > > > > >
> > >>>> -----------------------------------------------------------------
> > >>>> > > > > > >
> > >>>> > > > > > > Ensure that no new components are created unless it’s
> > >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > >>>> > > > > > > [2]
> > >>>> > > > > > >
> > >>>> > > > >
> > >>>> > > >
> > >>>> > >
> > >>>> >
> > >>>>
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > >>>> > > > >
> > >>>> > > > >
> > >>>> > > > >
> > >>>> > > >
> > >>>> > >
> > >>>> > >
> > >>>> > > --
> > >>>> > >
> > >>>> > > Jarek Potiuk
> > >>>> > > Polidea <https://www.polidea.com/> | Principal Software
> Engineer
> > >>>> > >
> > >>>> > > M: +48 660 796 129 <+48660796129>
> > >>>> > > E: jarek.potiuk@polidea.com
> > >>>> > >
> > >>>> >
> > >>>>
> > >>>
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
E: jarek.potiuk@polidea.com
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
Hi Fokko,
Sid gave me the admin rights yesterday, forgot to update here. Thank you.
I have edited the components themselves, but to make components the
required filed I need to ask Infra. I created this ticket [1], still
waiting for it to be resolved.
Wouldn't it be smarter that users won't tag labels/component themselves?
> Any new ticket will get "triage" tag and once the community review the
> request they will set the proper components/priority ?
>
> Users can easily tag the wrong components so it's likely that the ordered
> Jira we have now won't stay like this for long.
>
Asking users to add the components by themselves may add some noise to the
triage process, but it should reduce the workload on maintainers, triagers,
and others tracking specific areas of the project. Although at the moment
it's not possible to know for sure if an issue has been triaged or not, we
can move to a process that clearly marks untriaged issues as such, and
maintainers will be able to look at an issue, and add/remove any
components/labels if necessary.
At the moment there are ~400 issues without any components added. I’ll go
through them and try to give them a component; but this sort of “issue
lake” can easily become forgotten. We also can’t ensure/force maintainers
to always do triage of issues filed in this lake.
Another reason to have issues filed with a component is because there are
parties that care and track only certain components, and for them it is
hard to discover all the issues.
In other apache projects, the triage process relies on a Jira workflow that
goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see possible jira
statuses [2]). This automatically marks new issues in a “Triage Needed”
status. I’d like to discuss this process after we’re done making the
changes proposed in this document.
Let me know what you all think.
Thanks,
Aizhamal
[1] https://issues.apache.org/jira/browse/INFRA-18410
[2] https://issues.apache.org/jira/ShowConstantsHelp.jspa
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko <fo...@driesprong.frl>
> wrote:
>
> > Hi Aizhamal,
> >
> > Sorry for the late reply. You're still an administrator on the Jira.
> Please let me know if you're missing any privileges.
> >
> > Cheers, Fokko
> >
> > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
> <ai...@google.com.invalid>:
> >
> >> Hello everyone,
> >> it took me longer than expected, but I finally got around to making
> these
> >> changes. I've moved all the issues to rightful components (except for
> those
> >> lacking any component - I'll work on those afterwards).
> >> I think I am unable to make changes to the components themselves
> (renames /
> >> deletes). Fokko, or anyone in the PMC, would you be able to grant me the
> >> privileges once more? My username is aizhamal. I'd like to do this as
> soon
> >> as possible, so that I won't have to clean up issues added to components
> >> that are to be removed.
> >>
> >> Thanks a lot! I'll notify you on this thread once I have done the
> changes
> >> to components. :)
> >>
> >> Aizhamal
> >>
> >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> aizhamal@google.com>
> >> wrote:
> >>
> >>> Thank you for Jira powers, Fokko :) I am aiming to get it done by
> Monday.
> >>>
> >>> Regards,
> >>> Aizhamal
> >>>
> >>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> >>> *Date: *Fri, May 10, 2019 at 4:05 AM
> >>> *To: * <de...@airflow.apache.org>
> >>> *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
> >>>> <ai...@google.com.invalid>:
> >>>>
> >>>> > Hello all,
> >>>> >
> >>>> > If it's okay by everyone, I would like to start performing the
> changes
> >>>> > outlined in the doc. +Siddharth Anand <sa...@apache.org> 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 <Ja...@polidea.com>
> >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
> >>>> > *To: * <de...@airflow.apache.org>
> >>>> > *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-labels-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
> >>>> > > <ai...@google.com.invalid> 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
> >>>> findability:
> >>>> > 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 is
> >>>> > > > > 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 and
> >>>> > > close
> >>>> > > > those issues more efficiently. Any other thoughts?
> >>>> > > >
> >>>> > > > Best,
> >>>> > > > Aizhamal
> >>>> > > >
> >>>> > > >
> >>>> > > >
> >>>> > > >
> >>>> > > > >
> >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> >>>> > > > > 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
> label
> >>>> > 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’t have one at the
> >>>> moment
> >>>> > > > > > >
> >>>> > > > > > >
> >>>> -----------------------------------------------------------------
> >>>> > > > > > >
> >>>> > > > > > > Ensure that no new components are created unless it’s
> >>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> >>>> > > > > > > [2]
> >>>> > > > > > >
> >>>> > > > >
> >>>> > > >
> >>>> > >
> >>>> >
> >>>>
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> >>>> > > > >
> >>>> > > > >
> >>>> > > > >
> >>>> > > >
> >>>> > >
> >>>> > >
> >>>> > > --
> >>>> > >
> >>>> > > Jarek Potiuk
> >>>> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >>>> > >
> >>>> > > M: +48 660 796 129 <+48660796129>
> >>>> > > E: jarek.potiuk@polidea.com
> >>>> > >
> >>>> >
> >>>>
> >>>
Re: [Proposal] Component changes for Apache Airflow
Posted by airflowuser <ai...@protonmail.com.INVALID>.
Wouldn't it be smarter that users won't tag labels/component themselves?
Any new ticket will get "triage" tag and once the community review the request they will set the proper components/priority ?
Users can easily tag the wrong components so it's likely that the ordered Jira we have now won't stay like this for long.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko <fo...@driesprong.frl> wrote:
> Hi Aizhamal,
>
> Sorry for the late reply. You're still an administrator on the Jira. Please let me know if you're missing any privileges.
>
> Cheers, Fokko
>
> Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy <ai...@google.com.invalid>:
>
>> Hello everyone,
>> it took me longer than expected, but I finally got around to making these
>> changes. I've moved all the issues to rightful components (except for those
>> lacking any component - I'll work on those afterwards).
>> I think I am unable to make changes to the components themselves (renames /
>> deletes). Fokko, or anyone in the PMC, would you be able to grant me the
>> privileges once more? My username is aizhamal. I'd like to do this as soon
>> as possible, so that I won't have to clean up issues added to components
>> that are to be removed.
>>
>> Thanks a lot! I'll notify you on this thread once I have done the changes
>> to components. :)
>>
>> Aizhamal
>>
>> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <ai...@google.com>
>> wrote:
>>
>>> Thank you for Jira powers, Fokko :) I am aiming to get it done by Monday.
>>>
>>> Regards,
>>> Aizhamal
>>>
>>> *From: *Driesprong, Fokko <fo...@driesprong.frl>
>>> *Date: *Fri, May 10, 2019 at 4:05 AM
>>> *To: * <de...@airflow.apache.org>
>>> *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
>>>> <ai...@google.com.invalid>:
>>>>
>>>> > Hello all,
>>>> >
>>>> > If it's okay by everyone, I would like to start performing the changes
>>>> > outlined in the doc. +Siddharth Anand <sa...@apache.org> 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 <Ja...@polidea.com>
>>>> > *Date: *Fri, May 3, 2019 at 5:31 AM
>>>> > *To: * <de...@airflow.apache.org>
>>>> > *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-labels-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
>>>> > > <ai...@google.com.invalid> 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
>>>> findability:
>>>> > 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 is
>>>> > > > > 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 and
>>>> > > close
>>>> > > > those issues more efficiently. Any other thoughts?
>>>> > > >
>>>> > > > Best,
>>>> > > > Aizhamal
>>>> > > >
>>>> > > >
>>>> > > >
>>>> > > >
>>>> > > > >
>>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>> > > > > 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 label
>>>> > 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’t have one at the
>>>> moment
>>>> > > > > > >
>>>> > > > > > >
>>>> -----------------------------------------------------------------
>>>> > > > > > >
>>>> > > > > > > Ensure that no new components are created unless it’s
>>>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
>>>> > > > > > > [2]
>>>> > > > > > >
>>>> > > > >
>>>> > > >
>>>> > >
>>>> >
>>>> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
>>>> > > > >
>>>> > > > >
>>>> > > > >
>>>> > > >
>>>> > >
>>>> > >
>>>> > > --
>>>> > >
>>>> > > Jarek Potiuk
>>>> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
>>>> > >
>>>> > > M: +48 660 796 129 <+48660796129>
>>>> > > E: jarek.potiuk@polidea.com
>>>> > >
>>>> >
>>>>
>>>
Re: [Proposal] Component changes for Apache Airflow
Posted by "Driesprong, Fokko" <fo...@driesprong.frl>.
Hi Aizhamal,
Sorry for the late reply. You're still an administrator on the Jira. Please
let me know if you're missing any privileges.
Cheers, Fokko
Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy
<ai...@google.com.invalid>:
> Hello everyone,
> it took me longer than expected, but I finally got around to making these
> changes. I've moved all the issues to rightful components (except for those
> lacking any component - I'll work on those afterwards).
> I think I am unable to make changes to the components themselves (renames /
> deletes). Fokko, or anyone in the PMC, would you be able to grant me the
> privileges once more? My username is aizhamal. I'd like to do this as soon
> as possible, so that I won't have to clean up issues added to components
> that are to be removed.
>
> Thanks a lot! I'll notify you on this thread once I have done the changes
> to components. :)
>
> Aizhamal
>
> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <
> aizhamal@google.com>
> wrote:
>
> > Thank you for Jira powers, Fokko :) I am aiming to get it done by Monday.
> >
> > Regards,
> > Aizhamal
> >
> > *From: *Driesprong, Fokko <fo...@driesprong.frl>
> > *Date: *Fri, May 10, 2019 at 4:05 AM
> > *To: * <de...@airflow.apache.org>
> > *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
> >> <ai...@google.com.invalid>:
> >>
> >> > Hello all,
> >> >
> >> > If it's okay by everyone, I would like to start performing the changes
> >> > outlined in the doc. +Siddharth Anand <sa...@apache.org> 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 <Ja...@polidea.com>
> >> > *Date: *Fri, May 3, 2019 at 5:31 AM
> >> > *To: * <de...@airflow.apache.org>
> >> > *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-labels-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
> >> > > <ai...@google.com.invalid> 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
> >> findability:
> >> > 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
> is
> >> > > > > 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
> and
> >> > > close
> >> > > > those issues more efficiently. Any other thoughts?
> >> > > >
> >> > > > Best,
> >> > > > Aizhamal
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > >
> >> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> >> > > > > 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
> label
> >> > 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’t have one at the
> >> moment
> >> > > > > > >
> >> > > > > > >
> >> -----------------------------------------------------------------
> >> > > > > > >
> >> > > > > > > Ensure that no new components are created unless it’s
> >> 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_NnMlarIvSQ8NYM/edit?usp=sharing
> >> > > > > > > [2]
> >> > > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> >> > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> > >
> >> > > --
> >> > >
> >> > > Jarek Potiuk
> >> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >> > >
> >> > > M: +48 660 796 129 <+48660796129>
> >> > > E: jarek.potiuk@polidea.com
> >> > >
> >> >
> >>
> >
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
Hello everyone,
it took me longer than expected, but I finally got around to making these
changes. I've moved all the issues to rightful components (except for those
lacking any component - I'll work on those afterwards).
I think I am unable to make changes to the components themselves (renames /
deletes). Fokko, or anyone in the PMC, would you be able to grant me the
privileges once more? My username is aizhamal. I'd like to do this as soon
as possible, so that I won't have to clean up issues added to components
that are to be removed.
Thanks a lot! I'll notify you on this thread once I have done the changes
to components. :)
Aizhamal
On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy <ai...@google.com>
wrote:
> Thank you for Jira powers, Fokko :) I am aiming to get it done by Monday.
>
> Regards,
> Aizhamal
>
> *From: *Driesprong, Fokko <fo...@driesprong.frl>
> *Date: *Fri, May 10, 2019 at 4:05 AM
> *To: * <de...@airflow.apache.org>
> *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
>> <ai...@google.com.invalid>:
>>
>> > Hello all,
>> >
>> > If it's okay by everyone, I would like to start performing the changes
>> > outlined in the doc. +Siddharth Anand <sa...@apache.org> 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 <Ja...@polidea.com>
>> > *Date: *Fri, May 3, 2019 at 5:31 AM
>> > *To: * <de...@airflow.apache.org>
>> > *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-labels-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
>> > > <ai...@google.com.invalid> 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
>> findability:
>> > 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 is
>> > > > > 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 and
>> > > close
>> > > > those issues more efficiently. Any other thoughts?
>> > > >
>> > > > Best,
>> > > > Aizhamal
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > >
>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> > > > > 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 label
>> > 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’t have one at the
>> moment
>> > > > > > >
>> > > > > > >
>> -----------------------------------------------------------------
>> > > > > > >
>> > > > > > > Ensure that no new components are created unless it’s
>> 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_NnMlarIvSQ8NYM/edit?usp=sharing
>> > > > > > > [2]
>> > > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> > >
>> > > --
>> > >
>> > > Jarek Potiuk
>> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
>> > >
>> > > M: +48 660 796 129 <+48660796129>
>> > > E: jarek.potiuk@polidea.com
>> > >
>> >
>>
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
Thank you for Jira powers, Fokko :) I am aiming to get it done by Monday.
Regards,
Aizhamal
*From: *Driesprong, Fokko <fo...@driesprong.frl>
*Date: *Fri, May 10, 2019 at 4:05 AM
*To: * <de...@airflow.apache.org>
*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
> <ai...@google.com.invalid>:
>
> > Hello all,
> >
> > If it's okay by everyone, I would like to start performing the changes
> > outlined in the doc. +Siddharth Anand <sa...@apache.org> 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 <Ja...@polidea.com>
> > *Date: *Fri, May 3, 2019 at 5:31 AM
> > *To: * <de...@airflow.apache.org>
> > *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-labels-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
> > > <ai...@google.com.invalid> 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 findability:
> > 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 is
> > > > > 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 and
> > > close
> > > > those issues more efficiently. Any other thoughts?
> > > >
> > > > Best,
> > > > Aizhamal
> > > >
> > > >
> > > >
> > > >
> > > > >
> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > 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 label
> > 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’t have one at the
> moment
> > > > > > >
> > > > > > >
> -----------------------------------------------------------------
> > > > > > >
> > > > > > > Ensure that no new components are created unless it’s 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > > > > [2]
> > > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > E: jarek.potiuk@polidea.com
> > >
> >
>
Re: [Proposal] Component changes for Apache Airflow
Posted by "Driesprong, Fokko" <fo...@driesprong.frl>.
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
<ai...@google.com.invalid>:
> Hello all,
>
> If it's okay by everyone, I would like to start performing the changes
> outlined in the doc. +Siddharth Anand <sa...@apache.org> 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 <Ja...@polidea.com>
> *Date: *Fri, May 3, 2019 at 5:31 AM
> *To: * <de...@airflow.apache.org>
> *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-labels-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
> > <ai...@google.com.invalid> 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 findability:
> 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 is
> > > > 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 and
> > close
> > > those issues more efficiently. Any other thoughts?
> > >
> > > Best,
> > > Aizhamal
> > >
> > >
> > >
> > >
> > > >
> > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > 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 label
> 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’t have one at the moment
> > > > > >
> > > > > > -----------------------------------------------------------------
> > > > > >
> > > > > > Ensure that no new components are created unless it’s 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > > > [2]
> > > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > > >
> > > >
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > E: jarek.potiuk@polidea.com
> >
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
Hello all,
If it's okay by everyone, I would like to start performing the changes
outlined in the doc. +Siddharth Anand <sa...@apache.org> 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 <Ja...@polidea.com>
*Date: *Fri, May 3, 2019 at 5:31 AM
*To: * <de...@airflow.apache.org>
*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-labels-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
> <ai...@google.com.invalid> 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 findability: 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 is
> > > 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 and
> close
> > those issues more efficiently. Any other thoughts?
> >
> > Best,
> > Aizhamal
> >
> >
> >
> >
> > >
> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > On Wednesday, May 1, 2019 12:17 PM, Ash Berlin-Taylor <as...@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 label 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’t have one at the moment
> > > > >
> > > > > -----------------------------------------------------------------
> > > > >
> > > > > Ensure that no new components are created unless it’s 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > > [2]
> > > > >
> > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> > >
> > >
> > >
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> E: jarek.potiuk@polidea.com
>
Re: [Proposal] Component changes for Apache Airflow
Posted by Jarek Potiuk <Ja...@polidea.com>.
+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-labels-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
<ai...@google.com.invalid> 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 findability: 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 is
> > 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 and close
> those issues more efficiently. Any other thoughts?
>
> Best,
> Aizhamal
>
>
>
>
> >
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Wednesday, May 1, 2019 12:17 PM, Ash Berlin-Taylor <as...@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 label 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’t have one at the moment
> > > >
> > > > -----------------------------------------------------------------
> > > >
> > > > Ensure that no new components are created unless it’s 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > > [2]
> > > >
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
> >
> >
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
E: jarek.potiuk@polidea.com
Re: [Proposal] Component changes for Apache Airflow
Posted by Aizhamal Nurmamat kyzy <ai...@google.com.INVALID>.
+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 findability: 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 is
> 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 and close
those issues more efficiently. Any other thoughts?
Best,
Aizhamal
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Wednesday, May 1, 2019 12:17 PM, Ash Berlin-Taylor <as...@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 label 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’t have one at the moment
> > >
> > > -----------------------------------------------------------------
> > >
> > > Ensure that no new components are created unless it’s 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > > [2]
> > >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
>
>
>
Re: [Proposal] Component changes for Apache Airflow
Posted by airflowuser <ai...@protonmail.com.INVALID>.
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 also think that the "version" field should be mandatory.
It's important to know against which airflow version the ticket is reported.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, May 1, 2019 12:17 PM, Ash Berlin-Taylor <as...@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 label 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’t have one at the moment
> >
> > -----------------------------------------------------------------
> >
> > Ensure that no new components are created unless it’s 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_NnMlarIvSQ8NYM/edit?usp=sharing
> > [2]
> > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933
Re: [Proposal] Component changes for Apache Airflow
Posted by Ash Berlin-Taylor <as...@apache.org>.
This sounds like a fantastic idea.
I would add to the list:
- Remove labels that should be components (we have a gcp label 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 <ai...@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’t have one at the moment
> -
>
> Ensure that no new components are created unless it’s 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_NnMlarIvSQ8NYM/edit?usp=sharing
> [2]
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933