You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airflow.apache.org by Tomasz Urbaszek <tu...@apache.org> on 2020/09/10 11:56:22 UTC
Consider using stale bot for issues
Hi all,
Currently, we have about 582 open issues on Github. The oldest opened
in March. Do you think we should consider using stale bot as we do for
PRs?
I don't think that issue that is open since March is "so important" to
keep it still open. This would also automate the process of verifying
the issue (the author will be notified and asked for an update). If
the issue is something that we want to keep open we should be able to
use the "pinned" label.
Other projects use it and I don't see anything wrong with it. I would
say that 30d is a good period for keeping an issue open.
What do you think?
Bests,
Tomek
Re: Consider using stale bot for issues
Posted by Vikram Koka <vi...@astronomer.io>.
Thanks Kaxil, appreciate the feedback.
On Sat, Sep 19, 2020 at 3:30 PM Kaxil Naik <ka...@gmail.com> wrote:
> Thanks, Vikram & Paola, the draft looks good, I left a couple of comments
> too.
>
> On Sat, Sep 19, 2020 at 11:28 PM Vikram Koka <vi...@astronomer.io> wrote:
>
> > Thanks Tomasz, Paola and I worked on this to get.a draft out for
> > discussion.
> >
> > Thank you for the quick feedback!
> >
> > On Sat, Sep 19, 2020 at 9:01 AM Tomasz Urbaszek <tu...@apache.org>
> > wrote:
> >
> > > Thanks, Vikram for the proposal! I've added a few thoughts.
> > >
> > > Tomek
> > >
> > >
> > > On Sat, Sep 19, 2020 at 2:35 AM Vikram Koka <vi...@astronomer.io>
> > wrote:
> > > >
> > > > As promised, here is a quick write-up to help kick-start the
> discussion
> > > >
> > >
> >
> https://docs.google.com/document/d/1jqmXO6mGZzHkhuvISedQVnhyc37V_iz00hokdMuoFaI/
> > > >
> > > > Elad, Asif, Paola, Pete, and apologies to anyone I missed,
> > > >
> > > > Let's collaborate on this. We can use the slack channel Ash setup
> > > > (#issue-triage) to discuss as well.
> > > > I can schedule a zoom meeting for the middle of next week to discuss.
> > > >
> > > > Best regards,
> > > >
> > > > Vikram
> > > >
> > > >
> > > > On Fri, Sep 18, 2020 at 2:33 AM Ash Berlin-Taylor <as...@apache.org>
> > > wrote:
> > > >
> > > > > I have renamed the existing, and seldom used #issue-ticket channel
> to
> > > > > #issue-triage.
> > > > >
> > > > > On Sep 18 2020, at 7:37 am, Elad Kalif <el...@gmail.com> wrote:
> > > > >
> > > > > > After reviewing some issues I think we might need a few more
> labels
> > > like:
> > > > > > area:scheduling options
> > > > > > missing information
> > > > > > can't reproduce
> > > > > >
> > > > > > maybe we can create a dedicated slack channel to work on the
> small
> > > > > details.
> > > > > >
> > > > > > Elad
> > > > > >
> > > > > > On Wed, Sep 16, 2020 at 9:12 PM Kaxil Naik <ka...@gmail.com>
> > > wrote:
> > > > > >
> > > > > >> @paola - Unfortunately the images won't render here in this
> list.
> > > You
> > > > > can
> > > > > >> upload it to external services like https://imgur.com/ and
> post a
> > > link
> > > > > >> here
> > > > > >> :)
> > > > > >>
> > > > > >> Regards,
> > > > > >> Kaxil
> > > > > >>
> > > > > >> On Wed, Sep 16, 2020 at 6:31 PM Paola Peraza Calderon <
> > > > > paola@astronomer.io
> > > > > >> >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Hey Jarek,
> > > > > >> >
> > > > > >> > Thanks! Looks like we're all set. Seeing this in GitHub:
> > > > > >> >
> > > > > >> > [image: image.png]
> > > > > >> >
> > > > > >> > It looks like I have the ability to:
> > > > > >> >
> > > > > >> > - Edit milestones/labels/assignee
> > > > > >> > - Close GH issues
> > > > > >> >
> > > > > >> > I'll let you know if I run into any other trouble
> > > permissions-wise.
> > > > > >> Thanks
> > > > > >> > again Jarek.
> > > > > >> >
> > > > > >> > Paola
> > > > > >> >
> > > > > >> > On Tue, Sep 15, 2020 at 8:40 AM Jarek Potiuk <
> > > > > Jarek.Potiuk@polidea.com>
> > > > > >> > wrote:
> > > > > >> >
> > > > > >> >> Hey Paola, Asif, Elad, Pete, Vikram - you should all be added
> > to
> > > the
> > > > > >> >> 'airflow-triage' team.
> > > > > >> >>
> > > > > >> >> Can you please accept and confirm that it works so that I can
> > > close
> > > > > >> >> the ticket :)?
> > > > > >> >>
> > > > > >> >> J.
> > > > > >> >>
> > > > > >> >> On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <
> > > > > Jarek.Potiuk@polidea.com>
> > > > > >> >> wrote:
> > > > > >> >> >
> > > > > >> >> > Ticket updated with both - Paola and Asif. :) The more,
> the
> > > > > merrier
> > > > > >> >> indeed :)
> > > > > >> >> >
> > > > > >> >> > J.
> > > > > >> >> >
> > > > > >> >> >
> > > > > >> >> > On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <
> > > > > >> >> paola@astronomer.io> wrote:
> > > > > >> >> >>
> > > > > >> >> >> Jarek - my GitHub is @paolaperaza! Thanks for submitting
> > that
> > > > > ticket
> > > > > >> >> with
> > > > > >> >> >> INFRA - let me know if there's anything else you need from
> > me
> > > > > >> on that
> > > > > >> >> front.
> > > > > >> >> >>
> > > > > >> >> >> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <
> > > ash@apache.org
> > > > > >
> > > > > >> >> wrote:
> > > > > >> >> >>
> > > > > >> >> >> > The more the merrier! Don't you have enough on your
> plate
> > > > > >> maintaining
> > > > > >> >> >> > Celery though? ;)
> > > > > >> >> >> >
> > > > > >> >> >> > -ash
> > > > > >> >> >> >
> > > > > >> >> >> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <
> > > auvipy@gmail.com>
> > > > > >> >> wrote:
> > > > > >> >> >> >
> > > > > >> >> >> > > Hi All,
> > > > > >> >> >> > >
> > > > > >> >> >> > > I'm Asif (https://github.com/auvipy), I am a python
> > > developer
> > > > > >> >> with a
> > > > > >> >> >> > > significant amount o time maintaining small and big
> open
> > > > > source
> > > > > >> >> >> > > projects. I would love to help triage & review issues
> &
> > > pull
> > > > > >> >> request
> > > > > >> >> >> > > for apache airflow.
> > > > > >> >> >> > >
> > > > > >> >> >> > > Thanks
> > > > > >> >> >> > >
> > > > > >> >> >> > >
> > > > > >> >> >> > >
> > > > > >> >> >> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
> > > turbaszek@apache.org
> > > > > >
> > > > > >> >> wrote:
> > > > > >> >> >> > >> Hi all,
> > > > > >> >> >> > >>
> > > > > >> >> >> > >> Currently, we have about 582 open issues on Github.
> The
> > > > > oldest
> > > > > >> >> opened
> > > > > >> >> >> > >> in March. Do you think we should consider using stale
> > bot
> > > > > >> as we
> > > > > >> >> do for
> > > > > >> >> >> > >> PRs?
> > > > > >> >> >> > >>
> > > > > >> >> >> > >> I don't think that issue that is open since March is
> > "so
> > > > > >> >> important" to
> > > > > >> >> >> > >> keep it still open. This would also automate the
> > process
> > > of
> > > > > >> >> verifying
> > > > > >> >> >> > >> the issue (the author will be notified and asked for
> an
> > > > > update).
> > > > > >> >> If
> > > > > >> >> >> > >> the issue is something that we want to keep open we
> > > should be
> > > > > >> >> able to
> > > > > >> >> >> > >> use the "pinned" label.
> > > > > >> >> >> > >>
> > > > > >> >> >> > >> Other projects use it and I don't see anything wrong
> > with
> > > > > >> it. I
> > > > > >> >> would
> > > > > >> >> >> > >> say that 30d is a good period for keeping an issue
> > open.
> > > > > >> >> >> > >>
> > > > > >> >> >> > >> What do you think?
> > > > > >> >> >> > >>
> > > > > >> >> >> > >> Bests,
> > > > > >> >> >> > >> Tomek
> > > > > >> >> >> > >>
> > > > > >> >> >> > >
> > > > > >> >> >> >
> > > > > >> >> >>
> > > > > >> >> >>
> > > > > >> >> >> --
> > > > > >> >> >>
> > > > > >> >> >> *Paola Peraza Calderon*
> > > > > >> >> >> Astronomer | Product
> > > > > >> >> >> 914.483.8291 <(914)%20483-8291>
> > > > > >> >> >
> > > > > >> >> >
> > > > > >> >> >
> > > > > >> >> > --
> > > > > >> >> >
> > > > > >> >> > Jarek Potiuk
> > > > > >> >> > Polidea | Principal Software Engineer
> > > > > >> >> >
> > > > > >> >> > M: +48 660 796 129
> > > > > >> >> >
> > > > > >> >> >
> > > > > >> >>
> > > > > >> >>
> > > > > >> >> --
> > > > > >> >>
> > > > > >> >> Jarek Potiuk
> > > > > >> >> Polidea | Principal Software Engineer
> > > > > >> >>
> > > > > >> >> M: +48 660 796 129
> > > > > >> >>
> > > > > >> >
> > > > > >> >
> > > > > >> > --
> > > > > >> >
> > > > > >> > *Paola Peraza Calderon*
> > > > > >> > Astronomer | Product
> > > > > >> > 914.483.8291 <(914)%20483-8291>
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >>
> > > > > >
> > > > >
> > >
> >
>
Re: Consider using stale bot for issues
Posted by Kaxil Naik <ka...@gmail.com>.
Thanks, Vikram & Paola, the draft looks good, I left a couple of comments
too.
On Sat, Sep 19, 2020 at 11:28 PM Vikram Koka <vi...@astronomer.io> wrote:
> Thanks Tomasz, Paola and I worked on this to get.a draft out for
> discussion.
>
> Thank you for the quick feedback!
>
> On Sat, Sep 19, 2020 at 9:01 AM Tomasz Urbaszek <tu...@apache.org>
> wrote:
>
> > Thanks, Vikram for the proposal! I've added a few thoughts.
> >
> > Tomek
> >
> >
> > On Sat, Sep 19, 2020 at 2:35 AM Vikram Koka <vi...@astronomer.io>
> wrote:
> > >
> > > As promised, here is a quick write-up to help kick-start the discussion
> > >
> >
> https://docs.google.com/document/d/1jqmXO6mGZzHkhuvISedQVnhyc37V_iz00hokdMuoFaI/
> > >
> > > Elad, Asif, Paola, Pete, and apologies to anyone I missed,
> > >
> > > Let's collaborate on this. We can use the slack channel Ash setup
> > > (#issue-triage) to discuss as well.
> > > I can schedule a zoom meeting for the middle of next week to discuss.
> > >
> > > Best regards,
> > >
> > > Vikram
> > >
> > >
> > > On Fri, Sep 18, 2020 at 2:33 AM Ash Berlin-Taylor <as...@apache.org>
> > wrote:
> > >
> > > > I have renamed the existing, and seldom used #issue-ticket channel to
> > > > #issue-triage.
> > > >
> > > > On Sep 18 2020, at 7:37 am, Elad Kalif <el...@gmail.com> wrote:
> > > >
> > > > > After reviewing some issues I think we might need a few more labels
> > like:
> > > > > area:scheduling options
> > > > > missing information
> > > > > can't reproduce
> > > > >
> > > > > maybe we can create a dedicated slack channel to work on the small
> > > > details.
> > > > >
> > > > > Elad
> > > > >
> > > > > On Wed, Sep 16, 2020 at 9:12 PM Kaxil Naik <ka...@gmail.com>
> > wrote:
> > > > >
> > > > >> @paola - Unfortunately the images won't render here in this list.
> > You
> > > > can
> > > > >> upload it to external services like https://imgur.com/ and post a
> > link
> > > > >> here
> > > > >> :)
> > > > >>
> > > > >> Regards,
> > > > >> Kaxil
> > > > >>
> > > > >> On Wed, Sep 16, 2020 at 6:31 PM Paola Peraza Calderon <
> > > > paola@astronomer.io
> > > > >> >
> > > > >> wrote:
> > > > >>
> > > > >> > Hey Jarek,
> > > > >> >
> > > > >> > Thanks! Looks like we're all set. Seeing this in GitHub:
> > > > >> >
> > > > >> > [image: image.png]
> > > > >> >
> > > > >> > It looks like I have the ability to:
> > > > >> >
> > > > >> > - Edit milestones/labels/assignee
> > > > >> > - Close GH issues
> > > > >> >
> > > > >> > I'll let you know if I run into any other trouble
> > permissions-wise.
> > > > >> Thanks
> > > > >> > again Jarek.
> > > > >> >
> > > > >> > Paola
> > > > >> >
> > > > >> > On Tue, Sep 15, 2020 at 8:40 AM Jarek Potiuk <
> > > > Jarek.Potiuk@polidea.com>
> > > > >> > wrote:
> > > > >> >
> > > > >> >> Hey Paola, Asif, Elad, Pete, Vikram - you should all be added
> to
> > the
> > > > >> >> 'airflow-triage' team.
> > > > >> >>
> > > > >> >> Can you please accept and confirm that it works so that I can
> > close
> > > > >> >> the ticket :)?
> > > > >> >>
> > > > >> >> J.
> > > > >> >>
> > > > >> >> On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <
> > > > Jarek.Potiuk@polidea.com>
> > > > >> >> wrote:
> > > > >> >> >
> > > > >> >> > Ticket updated with both - Paola and Asif. :) The more, the
> > > > merrier
> > > > >> >> indeed :)
> > > > >> >> >
> > > > >> >> > J.
> > > > >> >> >
> > > > >> >> >
> > > > >> >> > On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <
> > > > >> >> paola@astronomer.io> wrote:
> > > > >> >> >>
> > > > >> >> >> Jarek - my GitHub is @paolaperaza! Thanks for submitting
> that
> > > > ticket
> > > > >> >> with
> > > > >> >> >> INFRA - let me know if there's anything else you need from
> me
> > > > >> on that
> > > > >> >> front.
> > > > >> >> >>
> > > > >> >> >> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <
> > ash@apache.org
> > > > >
> > > > >> >> wrote:
> > > > >> >> >>
> > > > >> >> >> > The more the merrier! Don't you have enough on your plate
> > > > >> maintaining
> > > > >> >> >> > Celery though? ;)
> > > > >> >> >> >
> > > > >> >> >> > -ash
> > > > >> >> >> >
> > > > >> >> >> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <
> > auvipy@gmail.com>
> > > > >> >> wrote:
> > > > >> >> >> >
> > > > >> >> >> > > Hi All,
> > > > >> >> >> > >
> > > > >> >> >> > > I'm Asif (https://github.com/auvipy), I am a python
> > developer
> > > > >> >> with a
> > > > >> >> >> > > significant amount o time maintaining small and big open
> > > > source
> > > > >> >> >> > > projects. I would love to help triage & review issues &
> > pull
> > > > >> >> request
> > > > >> >> >> > > for apache airflow.
> > > > >> >> >> > >
> > > > >> >> >> > > Thanks
> > > > >> >> >> > >
> > > > >> >> >> > >
> > > > >> >> >> > >
> > > > >> >> >> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
> > turbaszek@apache.org
> > > > >
> > > > >> >> wrote:
> > > > >> >> >> > >> Hi all,
> > > > >> >> >> > >>
> > > > >> >> >> > >> Currently, we have about 582 open issues on Github. The
> > > > oldest
> > > > >> >> opened
> > > > >> >> >> > >> in March. Do you think we should consider using stale
> bot
> > > > >> as we
> > > > >> >> do for
> > > > >> >> >> > >> PRs?
> > > > >> >> >> > >>
> > > > >> >> >> > >> I don't think that issue that is open since March is
> "so
> > > > >> >> important" to
> > > > >> >> >> > >> keep it still open. This would also automate the
> process
> > of
> > > > >> >> verifying
> > > > >> >> >> > >> the issue (the author will be notified and asked for an
> > > > update).
> > > > >> >> If
> > > > >> >> >> > >> the issue is something that we want to keep open we
> > should be
> > > > >> >> able to
> > > > >> >> >> > >> use the "pinned" label.
> > > > >> >> >> > >>
> > > > >> >> >> > >> Other projects use it and I don't see anything wrong
> with
> > > > >> it. I
> > > > >> >> would
> > > > >> >> >> > >> say that 30d is a good period for keeping an issue
> open.
> > > > >> >> >> > >>
> > > > >> >> >> > >> What do you think?
> > > > >> >> >> > >>
> > > > >> >> >> > >> Bests,
> > > > >> >> >> > >> Tomek
> > > > >> >> >> > >>
> > > > >> >> >> > >
> > > > >> >> >> >
> > > > >> >> >>
> > > > >> >> >>
> > > > >> >> >> --
> > > > >> >> >>
> > > > >> >> >> *Paola Peraza Calderon*
> > > > >> >> >> Astronomer | Product
> > > > >> >> >> 914.483.8291 <(914)%20483-8291>
> > > > >> >> >
> > > > >> >> >
> > > > >> >> >
> > > > >> >> > --
> > > > >> >> >
> > > > >> >> > Jarek Potiuk
> > > > >> >> > Polidea | Principal Software Engineer
> > > > >> >> >
> > > > >> >> > M: +48 660 796 129
> > > > >> >> >
> > > > >> >> >
> > > > >> >>
> > > > >> >>
> > > > >> >> --
> > > > >> >>
> > > > >> >> Jarek Potiuk
> > > > >> >> Polidea | Principal Software Engineer
> > > > >> >>
> > > > >> >> M: +48 660 796 129
> > > > >> >>
> > > > >> >
> > > > >> >
> > > > >> > --
> > > > >> >
> > > > >> > *Paola Peraza Calderon*
> > > > >> > Astronomer | Product
> > > > >> > 914.483.8291 <(914)%20483-8291>
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >>
> > > > >
> > > >
> >
>
Re: Consider using stale bot for issues
Posted by Vikram Koka <vi...@astronomer.io>.
Thanks Tomasz, Paola and I worked on this to get.a draft out for discussion.
Thank you for the quick feedback!
On Sat, Sep 19, 2020 at 9:01 AM Tomasz Urbaszek <tu...@apache.org>
wrote:
> Thanks, Vikram for the proposal! I've added a few thoughts.
>
> Tomek
>
>
> On Sat, Sep 19, 2020 at 2:35 AM Vikram Koka <vi...@astronomer.io> wrote:
> >
> > As promised, here is a quick write-up to help kick-start the discussion
> >
> https://docs.google.com/document/d/1jqmXO6mGZzHkhuvISedQVnhyc37V_iz00hokdMuoFaI/
> >
> > Elad, Asif, Paola, Pete, and apologies to anyone I missed,
> >
> > Let's collaborate on this. We can use the slack channel Ash setup
> > (#issue-triage) to discuss as well.
> > I can schedule a zoom meeting for the middle of next week to discuss.
> >
> > Best regards,
> >
> > Vikram
> >
> >
> > On Fri, Sep 18, 2020 at 2:33 AM Ash Berlin-Taylor <as...@apache.org>
> wrote:
> >
> > > I have renamed the existing, and seldom used #issue-ticket channel to
> > > #issue-triage.
> > >
> > > On Sep 18 2020, at 7:37 am, Elad Kalif <el...@gmail.com> wrote:
> > >
> > > > After reviewing some issues I think we might need a few more labels
> like:
> > > > area:scheduling options
> > > > missing information
> > > > can't reproduce
> > > >
> > > > maybe we can create a dedicated slack channel to work on the small
> > > details.
> > > >
> > > > Elad
> > > >
> > > > On Wed, Sep 16, 2020 at 9:12 PM Kaxil Naik <ka...@gmail.com>
> wrote:
> > > >
> > > >> @paola - Unfortunately the images won't render here in this list.
> You
> > > can
> > > >> upload it to external services like https://imgur.com/ and post a
> link
> > > >> here
> > > >> :)
> > > >>
> > > >> Regards,
> > > >> Kaxil
> > > >>
> > > >> On Wed, Sep 16, 2020 at 6:31 PM Paola Peraza Calderon <
> > > paola@astronomer.io
> > > >> >
> > > >> wrote:
> > > >>
> > > >> > Hey Jarek,
> > > >> >
> > > >> > Thanks! Looks like we're all set. Seeing this in GitHub:
> > > >> >
> > > >> > [image: image.png]
> > > >> >
> > > >> > It looks like I have the ability to:
> > > >> >
> > > >> > - Edit milestones/labels/assignee
> > > >> > - Close GH issues
> > > >> >
> > > >> > I'll let you know if I run into any other trouble
> permissions-wise.
> > > >> Thanks
> > > >> > again Jarek.
> > > >> >
> > > >> > Paola
> > > >> >
> > > >> > On Tue, Sep 15, 2020 at 8:40 AM Jarek Potiuk <
> > > Jarek.Potiuk@polidea.com>
> > > >> > wrote:
> > > >> >
> > > >> >> Hey Paola, Asif, Elad, Pete, Vikram - you should all be added to
> the
> > > >> >> 'airflow-triage' team.
> > > >> >>
> > > >> >> Can you please accept and confirm that it works so that I can
> close
> > > >> >> the ticket :)?
> > > >> >>
> > > >> >> J.
> > > >> >>
> > > >> >> On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <
> > > Jarek.Potiuk@polidea.com>
> > > >> >> wrote:
> > > >> >> >
> > > >> >> > Ticket updated with both - Paola and Asif. :) The more, the
> > > merrier
> > > >> >> indeed :)
> > > >> >> >
> > > >> >> > J.
> > > >> >> >
> > > >> >> >
> > > >> >> > On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <
> > > >> >> paola@astronomer.io> wrote:
> > > >> >> >>
> > > >> >> >> Jarek - my GitHub is @paolaperaza! Thanks for submitting that
> > > ticket
> > > >> >> with
> > > >> >> >> INFRA - let me know if there's anything else you need from me
> > > >> on that
> > > >> >> front.
> > > >> >> >>
> > > >> >> >> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <
> ash@apache.org
> > > >
> > > >> >> wrote:
> > > >> >> >>
> > > >> >> >> > The more the merrier! Don't you have enough on your plate
> > > >> maintaining
> > > >> >> >> > Celery though? ;)
> > > >> >> >> >
> > > >> >> >> > -ash
> > > >> >> >> >
> > > >> >> >> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <
> auvipy@gmail.com>
> > > >> >> wrote:
> > > >> >> >> >
> > > >> >> >> > > Hi All,
> > > >> >> >> > >
> > > >> >> >> > > I'm Asif (https://github.com/auvipy), I am a python
> developer
> > > >> >> with a
> > > >> >> >> > > significant amount o time maintaining small and big open
> > > source
> > > >> >> >> > > projects. I would love to help triage & review issues &
> pull
> > > >> >> request
> > > >> >> >> > > for apache airflow.
> > > >> >> >> > >
> > > >> >> >> > > Thanks
> > > >> >> >> > >
> > > >> >> >> > >
> > > >> >> >> > >
> > > >> >> >> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
> turbaszek@apache.org
> > > >
> > > >> >> wrote:
> > > >> >> >> > >> Hi all,
> > > >> >> >> > >>
> > > >> >> >> > >> Currently, we have about 582 open issues on Github. The
> > > oldest
> > > >> >> opened
> > > >> >> >> > >> in March. Do you think we should consider using stale bot
> > > >> as we
> > > >> >> do for
> > > >> >> >> > >> PRs?
> > > >> >> >> > >>
> > > >> >> >> > >> I don't think that issue that is open since March is "so
> > > >> >> important" to
> > > >> >> >> > >> keep it still open. This would also automate the process
> of
> > > >> >> verifying
> > > >> >> >> > >> the issue (the author will be notified and asked for an
> > > update).
> > > >> >> If
> > > >> >> >> > >> the issue is something that we want to keep open we
> should be
> > > >> >> able to
> > > >> >> >> > >> use the "pinned" label.
> > > >> >> >> > >>
> > > >> >> >> > >> Other projects use it and I don't see anything wrong with
> > > >> it. I
> > > >> >> would
> > > >> >> >> > >> say that 30d is a good period for keeping an issue open.
> > > >> >> >> > >>
> > > >> >> >> > >> What do you think?
> > > >> >> >> > >>
> > > >> >> >> > >> Bests,
> > > >> >> >> > >> Tomek
> > > >> >> >> > >>
> > > >> >> >> > >
> > > >> >> >> >
> > > >> >> >>
> > > >> >> >>
> > > >> >> >> --
> > > >> >> >>
> > > >> >> >> *Paola Peraza Calderon*
> > > >> >> >> Astronomer | Product
> > > >> >> >> 914.483.8291 <(914)%20483-8291>
> > > >> >> >
> > > >> >> >
> > > >> >> >
> > > >> >> > --
> > > >> >> >
> > > >> >> > Jarek Potiuk
> > > >> >> > Polidea | Principal Software Engineer
> > > >> >> >
> > > >> >> > M: +48 660 796 129
> > > >> >> >
> > > >> >> >
> > > >> >>
> > > >> >>
> > > >> >> --
> > > >> >>
> > > >> >> Jarek Potiuk
> > > >> >> Polidea | Principal Software Engineer
> > > >> >>
> > > >> >> M: +48 660 796 129
> > > >> >>
> > > >> >
> > > >> >
> > > >> > --
> > > >> >
> > > >> > *Paola Peraza Calderon*
> > > >> > Astronomer | Product
> > > >> > 914.483.8291 <(914)%20483-8291>
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >
> > >
>
Re: Consider using stale bot for issues
Posted by Tomasz Urbaszek <tu...@apache.org>.
Thanks, Vikram for the proposal! I've added a few thoughts.
Tomek
On Sat, Sep 19, 2020 at 2:35 AM Vikram Koka <vi...@astronomer.io> wrote:
>
> As promised, here is a quick write-up to help kick-start the discussion
> https://docs.google.com/document/d/1jqmXO6mGZzHkhuvISedQVnhyc37V_iz00hokdMuoFaI/
>
> Elad, Asif, Paola, Pete, and apologies to anyone I missed,
>
> Let's collaborate on this. We can use the slack channel Ash setup
> (#issue-triage) to discuss as well.
> I can schedule a zoom meeting for the middle of next week to discuss.
>
> Best regards,
>
> Vikram
>
>
> On Fri, Sep 18, 2020 at 2:33 AM Ash Berlin-Taylor <as...@apache.org> wrote:
>
> > I have renamed the existing, and seldom used #issue-ticket channel to
> > #issue-triage.
> >
> > On Sep 18 2020, at 7:37 am, Elad Kalif <el...@gmail.com> wrote:
> >
> > > After reviewing some issues I think we might need a few more labels like:
> > > area:scheduling options
> > > missing information
> > > can't reproduce
> > >
> > > maybe we can create a dedicated slack channel to work on the small
> > details.
> > >
> > > Elad
> > >
> > > On Wed, Sep 16, 2020 at 9:12 PM Kaxil Naik <ka...@gmail.com> wrote:
> > >
> > >> @paola - Unfortunately the images won't render here in this list. You
> > can
> > >> upload it to external services like https://imgur.com/ and post a link
> > >> here
> > >> :)
> > >>
> > >> Regards,
> > >> Kaxil
> > >>
> > >> On Wed, Sep 16, 2020 at 6:31 PM Paola Peraza Calderon <
> > paola@astronomer.io
> > >> >
> > >> wrote:
> > >>
> > >> > Hey Jarek,
> > >> >
> > >> > Thanks! Looks like we're all set. Seeing this in GitHub:
> > >> >
> > >> > [image: image.png]
> > >> >
> > >> > It looks like I have the ability to:
> > >> >
> > >> > - Edit milestones/labels/assignee
> > >> > - Close GH issues
> > >> >
> > >> > I'll let you know if I run into any other trouble permissions-wise.
> > >> Thanks
> > >> > again Jarek.
> > >> >
> > >> > Paola
> > >> >
> > >> > On Tue, Sep 15, 2020 at 8:40 AM Jarek Potiuk <
> > Jarek.Potiuk@polidea.com>
> > >> > wrote:
> > >> >
> > >> >> Hey Paola, Asif, Elad, Pete, Vikram - you should all be added to the
> > >> >> 'airflow-triage' team.
> > >> >>
> > >> >> Can you please accept and confirm that it works so that I can close
> > >> >> the ticket :)?
> > >> >>
> > >> >> J.
> > >> >>
> > >> >> On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <
> > Jarek.Potiuk@polidea.com>
> > >> >> wrote:
> > >> >> >
> > >> >> > Ticket updated with both - Paola and Asif. :) The more, the
> > merrier
> > >> >> indeed :)
> > >> >> >
> > >> >> > J.
> > >> >> >
> > >> >> >
> > >> >> > On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <
> > >> >> paola@astronomer.io> wrote:
> > >> >> >>
> > >> >> >> Jarek - my GitHub is @paolaperaza! Thanks for submitting that
> > ticket
> > >> >> with
> > >> >> >> INFRA - let me know if there's anything else you need from me
> > >> on that
> > >> >> front.
> > >> >> >>
> > >> >> >> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <ash@apache.org
> > >
> > >> >> wrote:
> > >> >> >>
> > >> >> >> > The more the merrier! Don't you have enough on your plate
> > >> maintaining
> > >> >> >> > Celery though? ;)
> > >> >> >> >
> > >> >> >> > -ash
> > >> >> >> >
> > >> >> >> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com>
> > >> >> wrote:
> > >> >> >> >
> > >> >> >> > > Hi All,
> > >> >> >> > >
> > >> >> >> > > I'm Asif (https://github.com/auvipy), I am a python developer
> > >> >> with a
> > >> >> >> > > significant amount o time maintaining small and big open
> > source
> > >> >> >> > > projects. I would love to help triage & review issues & pull
> > >> >> request
> > >> >> >> > > for apache airflow.
> > >> >> >> > >
> > >> >> >> > > Thanks
> > >> >> >> > >
> > >> >> >> > >
> > >> >> >> > >
> > >> >> >> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <turbaszek@apache.org
> > >
> > >> >> wrote:
> > >> >> >> > >> Hi all,
> > >> >> >> > >>
> > >> >> >> > >> Currently, we have about 582 open issues on Github. The
> > oldest
> > >> >> opened
> > >> >> >> > >> in March. Do you think we should consider using stale bot
> > >> as we
> > >> >> do for
> > >> >> >> > >> PRs?
> > >> >> >> > >>
> > >> >> >> > >> I don't think that issue that is open since March is "so
> > >> >> important" to
> > >> >> >> > >> keep it still open. This would also automate the process of
> > >> >> verifying
> > >> >> >> > >> the issue (the author will be notified and asked for an
> > update).
> > >> >> If
> > >> >> >> > >> the issue is something that we want to keep open we should be
> > >> >> able to
> > >> >> >> > >> use the "pinned" label.
> > >> >> >> > >>
> > >> >> >> > >> Other projects use it and I don't see anything wrong with
> > >> it. I
> > >> >> would
> > >> >> >> > >> say that 30d is a good period for keeping an issue open.
> > >> >> >> > >>
> > >> >> >> > >> What do you think?
> > >> >> >> > >>
> > >> >> >> > >> Bests,
> > >> >> >> > >> Tomek
> > >> >> >> > >>
> > >> >> >> > >
> > >> >> >> >
> > >> >> >>
> > >> >> >>
> > >> >> >> --
> > >> >> >>
> > >> >> >> *Paola Peraza Calderon*
> > >> >> >> Astronomer | Product
> > >> >> >> 914.483.8291 <(914)%20483-8291>
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> > --
> > >> >> >
> > >> >> > Jarek Potiuk
> > >> >> > Polidea | Principal Software Engineer
> > >> >> >
> > >> >> > M: +48 660 796 129
> > >> >> >
> > >> >> >
> > >> >>
> > >> >>
> > >> >> --
> > >> >>
> > >> >> Jarek Potiuk
> > >> >> Polidea | Principal Software Engineer
> > >> >>
> > >> >> M: +48 660 796 129
> > >> >>
> > >> >
> > >> >
> > >> > --
> > >> >
> > >> > *Paola Peraza Calderon*
> > >> > Astronomer | Product
> > >> > 914.483.8291 <(914)%20483-8291>
> > >> >
> > >> >
> > >> >
> > >>
> > >
> >
Re: Consider using stale bot for issues
Posted by Vikram Koka <vi...@astronomer.io>.
As promised, here is a quick write-up to help kick-start the discussion
https://docs.google.com/document/d/1jqmXO6mGZzHkhuvISedQVnhyc37V_iz00hokdMuoFaI/
Elad, Asif, Paola, Pete, and apologies to anyone I missed,
Let's collaborate on this. We can use the slack channel Ash setup
(#issue-triage) to discuss as well.
I can schedule a zoom meeting for the middle of next week to discuss.
Best regards,
Vikram
On Fri, Sep 18, 2020 at 2:33 AM Ash Berlin-Taylor <as...@apache.org> wrote:
> I have renamed the existing, and seldom used #issue-ticket channel to
> #issue-triage.
>
> On Sep 18 2020, at 7:37 am, Elad Kalif <el...@gmail.com> wrote:
>
> > After reviewing some issues I think we might need a few more labels like:
> > area:scheduling options
> > missing information
> > can't reproduce
> >
> > maybe we can create a dedicated slack channel to work on the small
> details.
> >
> > Elad
> >
> > On Wed, Sep 16, 2020 at 9:12 PM Kaxil Naik <ka...@gmail.com> wrote:
> >
> >> @paola - Unfortunately the images won't render here in this list. You
> can
> >> upload it to external services like https://imgur.com/ and post a link
> >> here
> >> :)
> >>
> >> Regards,
> >> Kaxil
> >>
> >> On Wed, Sep 16, 2020 at 6:31 PM Paola Peraza Calderon <
> paola@astronomer.io
> >> >
> >> wrote:
> >>
> >> > Hey Jarek,
> >> >
> >> > Thanks! Looks like we're all set. Seeing this in GitHub:
> >> >
> >> > [image: image.png]
> >> >
> >> > It looks like I have the ability to:
> >> >
> >> > - Edit milestones/labels/assignee
> >> > - Close GH issues
> >> >
> >> > I'll let you know if I run into any other trouble permissions-wise.
> >> Thanks
> >> > again Jarek.
> >> >
> >> > Paola
> >> >
> >> > On Tue, Sep 15, 2020 at 8:40 AM Jarek Potiuk <
> Jarek.Potiuk@polidea.com>
> >> > wrote:
> >> >
> >> >> Hey Paola, Asif, Elad, Pete, Vikram - you should all be added to the
> >> >> 'airflow-triage' team.
> >> >>
> >> >> Can you please accept and confirm that it works so that I can close
> >> >> the ticket :)?
> >> >>
> >> >> J.
> >> >>
> >> >> On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <
> Jarek.Potiuk@polidea.com>
> >> >> wrote:
> >> >> >
> >> >> > Ticket updated with both - Paola and Asif. :) The more, the
> merrier
> >> >> indeed :)
> >> >> >
> >> >> > J.
> >> >> >
> >> >> >
> >> >> > On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <
> >> >> paola@astronomer.io> wrote:
> >> >> >>
> >> >> >> Jarek - my GitHub is @paolaperaza! Thanks for submitting that
> ticket
> >> >> with
> >> >> >> INFRA - let me know if there's anything else you need from me
> >> on that
> >> >> front.
> >> >> >>
> >> >> >> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <ash@apache.org
> >
> >> >> wrote:
> >> >> >>
> >> >> >> > The more the merrier! Don't you have enough on your plate
> >> maintaining
> >> >> >> > Celery though? ;)
> >> >> >> >
> >> >> >> > -ash
> >> >> >> >
> >> >> >> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com>
> >> >> wrote:
> >> >> >> >
> >> >> >> > > Hi All,
> >> >> >> > >
> >> >> >> > > I'm Asif (https://github.com/auvipy), I am a python developer
> >> >> with a
> >> >> >> > > significant amount o time maintaining small and big open
> source
> >> >> >> > > projects. I would love to help triage & review issues & pull
> >> >> request
> >> >> >> > > for apache airflow.
> >> >> >> > >
> >> >> >> > > Thanks
> >> >> >> > >
> >> >> >> > >
> >> >> >> > >
> >> >> >> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <turbaszek@apache.org
> >
> >> >> wrote:
> >> >> >> > >> Hi all,
> >> >> >> > >>
> >> >> >> > >> Currently, we have about 582 open issues on Github. The
> oldest
> >> >> opened
> >> >> >> > >> in March. Do you think we should consider using stale bot
> >> as we
> >> >> do for
> >> >> >> > >> PRs?
> >> >> >> > >>
> >> >> >> > >> I don't think that issue that is open since March is "so
> >> >> important" to
> >> >> >> > >> keep it still open. This would also automate the process of
> >> >> verifying
> >> >> >> > >> the issue (the author will be notified and asked for an
> update).
> >> >> If
> >> >> >> > >> the issue is something that we want to keep open we should be
> >> >> able to
> >> >> >> > >> use the "pinned" label.
> >> >> >> > >>
> >> >> >> > >> Other projects use it and I don't see anything wrong with
> >> it. I
> >> >> would
> >> >> >> > >> say that 30d is a good period for keeping an issue open.
> >> >> >> > >>
> >> >> >> > >> What do you think?
> >> >> >> > >>
> >> >> >> > >> Bests,
> >> >> >> > >> Tomek
> >> >> >> > >>
> >> >> >> > >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >>
> >> >> >> *Paola Peraza Calderon*
> >> >> >> Astronomer | Product
> >> >> >> 914.483.8291 <(914)%20483-8291>
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> >
> >> >> > Jarek Potiuk
> >> >> > Polidea | Principal Software Engineer
> >> >> >
> >> >> > M: +48 660 796 129
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> Jarek Potiuk
> >> >> Polidea | Principal Software Engineer
> >> >>
> >> >> M: +48 660 796 129
> >> >>
> >> >
> >> >
> >> > --
> >> >
> >> > *Paola Peraza Calderon*
> >> > Astronomer | Product
> >> > 914.483.8291 <(914)%20483-8291>
> >> >
> >> >
> >> >
> >>
> >
>
Re: Consider using stale bot for issues
Posted by Ash Berlin-Taylor <as...@apache.org>.
I have renamed the existing, and seldom used #issue-ticket channel to #issue-triage.
On Sep 18 2020, at 7:37 am, Elad Kalif <el...@gmail.com> wrote:
> After reviewing some issues I think we might need a few more labels like:
> area:scheduling options
> missing information
> can't reproduce
>
> maybe we can create a dedicated slack channel to work on the small details.
>
> Elad
>
> On Wed, Sep 16, 2020 at 9:12 PM Kaxil Naik <ka...@gmail.com> wrote:
>
>> @paola - Unfortunately the images won't render here in this list. You can
>> upload it to external services like https://imgur.com/ and post a link
>> here
>> :)
>>
>> Regards,
>> Kaxil
>>
>> On Wed, Sep 16, 2020 at 6:31 PM Paola Peraza Calderon <paola@astronomer.io
>> >
>> wrote:
>>
>> > Hey Jarek,
>> >
>> > Thanks! Looks like we're all set. Seeing this in GitHub:
>> >
>> > [image: image.png]
>> >
>> > It looks like I have the ability to:
>> >
>> > - Edit milestones/labels/assignee
>> > - Close GH issues
>> >
>> > I'll let you know if I run into any other trouble permissions-wise.
>> Thanks
>> > again Jarek.
>> >
>> > Paola
>> >
>> > On Tue, Sep 15, 2020 at 8:40 AM Jarek Potiuk <Ja...@polidea.com>
>> > wrote:
>> >
>> >> Hey Paola, Asif, Elad, Pete, Vikram - you should all be added to the
>> >> 'airflow-triage' team.
>> >>
>> >> Can you please accept and confirm that it works so that I can close
>> >> the ticket :)?
>> >>
>> >> J.
>> >>
>> >> On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <Ja...@polidea.com>
>> >> wrote:
>> >> >
>> >> > Ticket updated with both - Paola and Asif. :) The more, the merrier
>> >> indeed :)
>> >> >
>> >> > J.
>> >> >
>> >> >
>> >> > On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <
>> >> paola@astronomer.io> wrote:
>> >> >>
>> >> >> Jarek - my GitHub is @paolaperaza! Thanks for submitting that ticket
>> >> with
>> >> >> INFRA - let me know if there's anything else you need from me
>> on that
>> >> front.
>> >> >>
>> >> >> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <as...@apache.org>
>> >> wrote:
>> >> >>
>> >> >> > The more the merrier! Don't you have enough on your plate
>> maintaining
>> >> >> > Celery though? ;)
>> >> >> >
>> >> >> > -ash
>> >> >> >
>> >> >> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com>
>> >> wrote:
>> >> >> >
>> >> >> > > Hi All,
>> >> >> > >
>> >> >> > > I'm Asif (https://github.com/auvipy), I am a python developer
>> >> with a
>> >> >> > > significant amount o time maintaining small and big open source
>> >> >> > > projects. I would love to help triage & review issues & pull
>> >> request
>> >> >> > > for apache airflow.
>> >> >> > >
>> >> >> > > Thanks
>> >> >> > >
>> >> >> > >
>> >> >> > >
>> >> >> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org>
>> >> wrote:
>> >> >> > >> Hi all,
>> >> >> > >>
>> >> >> > >> Currently, we have about 582 open issues on Github. The oldest
>> >> opened
>> >> >> > >> in March. Do you think we should consider using stale bot
>> as we
>> >> do for
>> >> >> > >> PRs?
>> >> >> > >>
>> >> >> > >> I don't think that issue that is open since March is "so
>> >> important" to
>> >> >> > >> keep it still open. This would also automate the process of
>> >> verifying
>> >> >> > >> the issue (the author will be notified and asked for an update).
>> >> If
>> >> >> > >> the issue is something that we want to keep open we should be
>> >> able to
>> >> >> > >> use the "pinned" label.
>> >> >> > >>
>> >> >> > >> Other projects use it and I don't see anything wrong with
>> it. I
>> >> would
>> >> >> > >> say that 30d is a good period for keeping an issue open.
>> >> >> > >>
>> >> >> > >> What do you think?
>> >> >> > >>
>> >> >> > >> Bests,
>> >> >> > >> Tomek
>> >> >> > >>
>> >> >> > >
>> >> >> >
>> >> >>
>> >> >>
>> >> >> --
>> >> >>
>> >> >> *Paola Peraza Calderon*
>> >> >> Astronomer | Product
>> >> >> 914.483.8291 <(914)%20483-8291>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> >
>> >> > Jarek Potiuk
>> >> > Polidea | Principal Software Engineer
>> >> >
>> >> > M: +48 660 796 129
>> >> >
>> >> >
>> >>
>> >>
>> >> --
>> >>
>> >> Jarek Potiuk
>> >> Polidea | Principal Software Engineer
>> >>
>> >> M: +48 660 796 129
>> >>
>> >
>> >
>> > --
>> >
>> > *Paola Peraza Calderon*
>> > Astronomer | Product
>> > 914.483.8291 <(914)%20483-8291>
>> >
>> >
>> >
>>
>
Re: Consider using stale bot for issues
Posted by Elad Kalif <el...@gmail.com>.
After reviewing some issues I think we might need a few more labels like:
area:scheduling options
missing information
can't reproduce
maybe we can create a dedicated slack channel to work on the small details.
Elad
On Wed, Sep 16, 2020 at 9:12 PM Kaxil Naik <ka...@gmail.com> wrote:
> @paola - Unfortunately the images won't render here in this list. You can
> upload it to external services like https://imgur.com/ and post a link
> here
> :)
>
> Regards,
> Kaxil
>
> On Wed, Sep 16, 2020 at 6:31 PM Paola Peraza Calderon <paola@astronomer.io
> >
> wrote:
>
> > Hey Jarek,
> >
> > Thanks! Looks like we're all set. Seeing this in GitHub:
> >
> > [image: image.png]
> >
> > It looks like I have the ability to:
> >
> > - Edit milestones/labels/assignee
> > - Close GH issues
> >
> > I'll let you know if I run into any other trouble permissions-wise.
> Thanks
> > again Jarek.
> >
> > Paola
> >
> > On Tue, Sep 15, 2020 at 8:40 AM Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> >> Hey Paola, Asif, Elad, Pete, Vikram - you should all be added to the
> >> 'airflow-triage' team.
> >>
> >> Can you please accept and confirm that it works so that I can close
> >> the ticket :)?
> >>
> >> J.
> >>
> >> On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <Ja...@polidea.com>
> >> wrote:
> >> >
> >> > Ticket updated with both - Paola and Asif. :) The more, the merrier
> >> indeed :)
> >> >
> >> > J.
> >> >
> >> >
> >> > On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <
> >> paola@astronomer.io> wrote:
> >> >>
> >> >> Jarek - my GitHub is @paolaperaza! Thanks for submitting that ticket
> >> with
> >> >> INFRA - let me know if there's anything else you need from me on that
> >> front.
> >> >>
> >> >> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <as...@apache.org>
> >> wrote:
> >> >>
> >> >> > The more the merrier! Don't you have enough on your plate
> maintaining
> >> >> > Celery though? ;)
> >> >> >
> >> >> > -ash
> >> >> >
> >> >> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com>
> >> wrote:
> >> >> >
> >> >> > > Hi All,
> >> >> > >
> >> >> > > I'm Asif (https://github.com/auvipy), I am a python developer
> >> with a
> >> >> > > significant amount o time maintaining small and big open source
> >> >> > > projects. I would love to help triage & review issues & pull
> >> request
> >> >> > > for apache airflow.
> >> >> > >
> >> >> > > Thanks
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org>
> >> wrote:
> >> >> > >> Hi all,
> >> >> > >>
> >> >> > >> Currently, we have about 582 open issues on Github. The oldest
> >> opened
> >> >> > >> in March. Do you think we should consider using stale bot as we
> >> do for
> >> >> > >> PRs?
> >> >> > >>
> >> >> > >> I don't think that issue that is open since March is "so
> >> important" to
> >> >> > >> keep it still open. This would also automate the process of
> >> verifying
> >> >> > >> the issue (the author will be notified and asked for an update).
> >> If
> >> >> > >> the issue is something that we want to keep open we should be
> >> able to
> >> >> > >> use the "pinned" label.
> >> >> > >>
> >> >> > >> Other projects use it and I don't see anything wrong with it. I
> >> would
> >> >> > >> say that 30d is a good period for keeping an issue open.
> >> >> > >>
> >> >> > >> What do you think?
> >> >> > >>
> >> >> > >> Bests,
> >> >> > >> Tomek
> >> >> > >>
> >> >> > >
> >> >> >
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> *Paola Peraza Calderon*
> >> >> Astronomer | Product
> >> >> 914.483.8291 <(914)%20483-8291>
> >> >
> >> >
> >> >
> >> > --
> >> >
> >> > Jarek Potiuk
> >> > Polidea | Principal Software Engineer
> >> >
> >> > M: +48 660 796 129
> >> >
> >> >
> >>
> >>
> >> --
> >>
> >> Jarek Potiuk
> >> Polidea | Principal Software Engineer
> >>
> >> M: +48 660 796 129
> >>
> >
> >
> > --
> >
> > *Paola Peraza Calderon*
> > Astronomer | Product
> > 914.483.8291 <(914)%20483-8291>
> >
> >
> >
>
Re: Consider using stale bot for issues
Posted by Kaxil Naik <ka...@gmail.com>.
@paola - Unfortunately the images won't render here in this list. You can
upload it to external services like https://imgur.com/ and post a link here
:)
Regards,
Kaxil
On Wed, Sep 16, 2020 at 6:31 PM Paola Peraza Calderon <pa...@astronomer.io>
wrote:
> Hey Jarek,
>
> Thanks! Looks like we're all set. Seeing this in GitHub:
>
> [image: image.png]
>
> It looks like I have the ability to:
>
> - Edit milestones/labels/assignee
> - Close GH issues
>
> I'll let you know if I run into any other trouble permissions-wise. Thanks
> again Jarek.
>
> Paola
>
> On Tue, Sep 15, 2020 at 8:40 AM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
>> Hey Paola, Asif, Elad, Pete, Vikram - you should all be added to the
>> 'airflow-triage' team.
>>
>> Can you please accept and confirm that it works so that I can close
>> the ticket :)?
>>
>> J.
>>
>> On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <Ja...@polidea.com>
>> wrote:
>> >
>> > Ticket updated with both - Paola and Asif. :) The more, the merrier
>> indeed :)
>> >
>> > J.
>> >
>> >
>> > On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <
>> paola@astronomer.io> wrote:
>> >>
>> >> Jarek - my GitHub is @paolaperaza! Thanks for submitting that ticket
>> with
>> >> INFRA - let me know if there's anything else you need from me on that
>> front.
>> >>
>> >> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <as...@apache.org>
>> wrote:
>> >>
>> >> > The more the merrier! Don't you have enough on your plate maintaining
>> >> > Celery though? ;)
>> >> >
>> >> > -ash
>> >> >
>> >> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com>
>> wrote:
>> >> >
>> >> > > Hi All,
>> >> > >
>> >> > > I'm Asif (https://github.com/auvipy), I am a python developer
>> with a
>> >> > > significant amount o time maintaining small and big open source
>> >> > > projects. I would love to help triage & review issues & pull
>> request
>> >> > > for apache airflow.
>> >> > >
>> >> > > Thanks
>> >> > >
>> >> > >
>> >> > >
>> >> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org>
>> wrote:
>> >> > >> Hi all,
>> >> > >>
>> >> > >> Currently, we have about 582 open issues on Github. The oldest
>> opened
>> >> > >> in March. Do you think we should consider using stale bot as we
>> do for
>> >> > >> PRs?
>> >> > >>
>> >> > >> I don't think that issue that is open since March is "so
>> important" to
>> >> > >> keep it still open. This would also automate the process of
>> verifying
>> >> > >> the issue (the author will be notified and asked for an update).
>> If
>> >> > >> the issue is something that we want to keep open we should be
>> able to
>> >> > >> use the "pinned" label.
>> >> > >>
>> >> > >> Other projects use it and I don't see anything wrong with it. I
>> would
>> >> > >> say that 30d is a good period for keeping an issue open.
>> >> > >>
>> >> > >> What do you think?
>> >> > >>
>> >> > >> Bests,
>> >> > >> Tomek
>> >> > >>
>> >> > >
>> >> >
>> >>
>> >>
>> >> --
>> >>
>> >> *Paola Peraza Calderon*
>> >> Astronomer | Product
>> >> 914.483.8291 <(914)%20483-8291>
>> >
>> >
>> >
>> > --
>> >
>> > Jarek Potiuk
>> > Polidea | Principal Software Engineer
>> >
>> > M: +48 660 796 129
>> >
>> >
>>
>>
>> --
>>
>> Jarek Potiuk
>> Polidea | Principal Software Engineer
>>
>> M: +48 660 796 129
>>
>
>
> --
>
> *Paola Peraza Calderon*
> Astronomer | Product
> 914.483.8291 <(914)%20483-8291>
>
>
>
Re: Consider using stale bot for issues
Posted by Paola Peraza Calderon <pa...@astronomer.io>.
Hey Jarek,
Thanks! Looks like we're all set. Seeing this in GitHub:
[image: image.png]
It looks like I have the ability to:
- Edit milestones/labels/assignee
- Close GH issues
I'll let you know if I run into any other trouble permissions-wise. Thanks
again Jarek.
Paola
On Tue, Sep 15, 2020 at 8:40 AM Jarek Potiuk <Ja...@polidea.com>
wrote:
> Hey Paola, Asif, Elad, Pete, Vikram - you should all be added to the
> 'airflow-triage' team.
>
> Can you please accept and confirm that it works so that I can close
> the ticket :)?
>
> J.
>
> On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <Ja...@polidea.com>
> wrote:
> >
> > Ticket updated with both - Paola and Asif. :) The more, the merrier
> indeed :)
> >
> > J.
> >
> >
> > On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <
> paola@astronomer.io> wrote:
> >>
> >> Jarek - my GitHub is @paolaperaza! Thanks for submitting that ticket
> with
> >> INFRA - let me know if there's anything else you need from me on that
> front.
> >>
> >> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <as...@apache.org>
> wrote:
> >>
> >> > The more the merrier! Don't you have enough on your plate maintaining
> >> > Celery though? ;)
> >> >
> >> > -ash
> >> >
> >> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com>
> wrote:
> >> >
> >> > > Hi All,
> >> > >
> >> > > I'm Asif (https://github.com/auvipy), I am a python developer with
> a
> >> > > significant amount o time maintaining small and big open source
> >> > > projects. I would love to help triage & review issues & pull request
> >> > > for apache airflow.
> >> > >
> >> > > Thanks
> >> > >
> >> > >
> >> > >
> >> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org>
> wrote:
> >> > >> Hi all,
> >> > >>
> >> > >> Currently, we have about 582 open issues on Github. The oldest
> opened
> >> > >> in March. Do you think we should consider using stale bot as we do
> for
> >> > >> PRs?
> >> > >>
> >> > >> I don't think that issue that is open since March is "so
> important" to
> >> > >> keep it still open. This would also automate the process of
> verifying
> >> > >> the issue (the author will be notified and asked for an update). If
> >> > >> the issue is something that we want to keep open we should be able
> to
> >> > >> use the "pinned" label.
> >> > >>
> >> > >> Other projects use it and I don't see anything wrong with it. I
> would
> >> > >> say that 30d is a good period for keeping an issue open.
> >> > >>
> >> > >> What do you think?
> >> > >>
> >> > >> Bests,
> >> > >> Tomek
> >> > >>
> >> > >
> >> >
> >>
> >>
> >> --
> >>
> >> *Paola Peraza Calderon*
> >> Astronomer | Product
> >> 914.483.8291 <(914)%20483-8291>
> >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea | Principal Software Engineer
> >
> > M: +48 660 796 129
> >
> >
>
>
> --
>
> Jarek Potiuk
> Polidea | Principal Software Engineer
>
> M: +48 660 796 129
>
--
*Paola Peraza Calderon*
Astronomer | Product
914.483.8291 <(914)%20483-8291>
Re: Consider using stale bot for issues
Posted by Jarek Potiuk <Ja...@polidea.com>.
Hey Paola, Asif, Elad, Pete, Vikram - you should all be added to the
'airflow-triage' team.
Can you please accept and confirm that it works so that I can close
the ticket :)?
J.
On Mon, Sep 14, 2020 at 5:39 PM Jarek Potiuk <Ja...@polidea.com> wrote:
>
> Ticket updated with both - Paola and Asif. :) The more, the merrier indeed :)
>
> J.
>
>
> On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <pa...@astronomer.io> wrote:
>>
>> Jarek - my GitHub is @paolaperaza! Thanks for submitting that ticket with
>> INFRA - let me know if there's anything else you need from me on that front.
>>
>> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <as...@apache.org> wrote:
>>
>> > The more the merrier! Don't you have enough on your plate maintaining
>> > Celery though? ;)
>> >
>> > -ash
>> >
>> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com> wrote:
>> >
>> > > Hi All,
>> > >
>> > > I'm Asif (https://github.com/auvipy), I am a python developer with a
>> > > significant amount o time maintaining small and big open source
>> > > projects. I would love to help triage & review issues & pull request
>> > > for apache airflow.
>> > >
>> > > Thanks
>> > >
>> > >
>> > >
>> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org> wrote:
>> > >> Hi all,
>> > >>
>> > >> Currently, we have about 582 open issues on Github. The oldest opened
>> > >> in March. Do you think we should consider using stale bot as we do for
>> > >> PRs?
>> > >>
>> > >> I don't think that issue that is open since March is "so important" to
>> > >> keep it still open. This would also automate the process of verifying
>> > >> the issue (the author will be notified and asked for an update). If
>> > >> the issue is something that we want to keep open we should be able to
>> > >> use the "pinned" label.
>> > >>
>> > >> Other projects use it and I don't see anything wrong with it. I would
>> > >> say that 30d is a good period for keeping an issue open.
>> > >>
>> > >> What do you think?
>> > >>
>> > >> Bests,
>> > >> Tomek
>> > >>
>> > >
>> >
>>
>>
>> --
>>
>> *Paola Peraza Calderon*
>> Astronomer | Product
>> 914.483.8291 <(914)%20483-8291>
>
>
>
> --
>
> Jarek Potiuk
> Polidea | Principal Software Engineer
>
> M: +48 660 796 129
>
>
--
Jarek Potiuk
Polidea | Principal Software Engineer
M: +48 660 796 129
Re: Consider using stale bot for issues
Posted by Jarek Potiuk <Ja...@polidea.com>.
Ticket updated with both - Paola and Asif. :) The more, the merrier indeed
:)
J.
On Mon, Sep 14, 2020 at 4:08 PM Paola Peraza Calderon <pa...@astronomer.io>
wrote:
> Jarek - my GitHub is @paolaperaza! Thanks for submitting that ticket with
> INFRA - let me know if there's anything else you need from me on that
> front.
>
> On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <as...@apache.org> wrote:
>
> > The more the merrier! Don't you have enough on your plate maintaining
> > Celery though? ;)
> >
> > -ash
> >
> > On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com> wrote:
> >
> > > Hi All,
> > >
> > > I'm Asif (https://github.com/auvipy), I am a python developer with a
> > > significant amount o time maintaining small and big open source
> > > projects. I would love to help triage & review issues & pull request
> > > for apache airflow.
> > >
> > > Thanks
> > >
> > >
> > >
> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org> wrote:
> > >> Hi all,
> > >>
> > >> Currently, we have about 582 open issues on Github. The oldest opened
> > >> in March. Do you think we should consider using stale bot as we do for
> > >> PRs?
> > >>
> > >> I don't think that issue that is open since March is "so important" to
> > >> keep it still open. This would also automate the process of verifying
> > >> the issue (the author will be notified and asked for an update). If
> > >> the issue is something that we want to keep open we should be able to
> > >> use the "pinned" label.
> > >>
> > >> Other projects use it and I don't see anything wrong with it. I would
> > >> say that 30d is a good period for keeping an issue open.
> > >>
> > >> What do you think?
> > >>
> > >> Bests,
> > >> Tomek
> > >>
> > >
> >
>
>
> --
>
> *Paola Peraza Calderon*
> Astronomer | Product
> 914.483.8291 <(914)%20483-8291>
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: Consider using stale bot for issues
Posted by Paola Peraza Calderon <pa...@astronomer.io>.
Jarek - my GitHub is @paolaperaza! Thanks for submitting that ticket with
INFRA - let me know if there's anything else you need from me on that front.
On Mon, Sep 14, 2020 at 6:50 AM Ash Berlin-Taylor <as...@apache.org> wrote:
> The more the merrier! Don't you have enough on your plate maintaining
> Celery though? ;)
>
> -ash
>
> On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com> wrote:
>
> > Hi All,
> >
> > I'm Asif (https://github.com/auvipy), I am a python developer with a
> > significant amount o time maintaining small and big open source
> > projects. I would love to help triage & review issues & pull request
> > for apache airflow.
> >
> > Thanks
> >
> >
> >
> > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org> wrote:
> >> Hi all,
> >>
> >> Currently, we have about 582 open issues on Github. The oldest opened
> >> in March. Do you think we should consider using stale bot as we do for
> >> PRs?
> >>
> >> I don't think that issue that is open since March is "so important" to
> >> keep it still open. This would also automate the process of verifying
> >> the issue (the author will be notified and asked for an update). If
> >> the issue is something that we want to keep open we should be able to
> >> use the "pinned" label.
> >>
> >> Other projects use it and I don't see anything wrong with it. I would
> >> say that 30d is a good period for keeping an issue open.
> >>
> >> What do you think?
> >>
> >> Bests,
> >> Tomek
> >>
> >
>
--
*Paola Peraza Calderon*
Astronomer | Product
914.483.8291 <(914)%20483-8291>
Re: Consider using stale bot for issues
Posted by Ash Berlin-Taylor <as...@apache.org>.
The more the merrier! Don't you have enough on your plate maintaining
Celery though? ;)
-ash
On Sep 14 2020, at 11:19 am, Asif Saif Uddin <au...@gmail.com> wrote:
> Hi All,
>
> I'm Asif (https://github.com/auvipy), I am a python developer with a
> significant amount o time maintaining small and big open source
> projects. I would love to help triage & review issues & pull request
> for apache airflow.
>
> Thanks
>
>
>
> On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org> wrote:
>> Hi all,
>>
>> Currently, we have about 582 open issues on Github. The oldest opened
>> in March. Do you think we should consider using stale bot as we do for
>> PRs?
>>
>> I don't think that issue that is open since March is "so important" to
>> keep it still open. This would also automate the process of verifying
>> the issue (the author will be notified and asked for an update). If
>> the issue is something that we want to keep open we should be able to
>> use the "pinned" label.
>>
>> Other projects use it and I don't see anything wrong with it. I would
>> say that 30d is a good period for keeping an issue open.
>>
>> What do you think?
>>
>> Bests,
>> Tomek
>>
>
Re: Consider using stale bot for issues
Posted by Asif Saif Uddin <au...@gmail.com>.
Hi All,
I'm Asif (https://github.com/auvipy), I am a python developer with a significant amount o time maintaining small and big open source projects. I would love to help triage & review issues & pull request for apache airflow.
Thanks
On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org> wrote:
> Hi all,
>
> Currently, we have about 582 open issues on Github. The oldest opened
> in March. Do you think we should consider using stale bot as we do for
> PRs?
>
> I don't think that issue that is open since March is "so important" to
> keep it still open. This would also automate the process of verifying
> the issue (the author will be notified and asked for an update). If
> the issue is something that we want to keep open we should be able to
> use the "pinned" label.
>
> Other projects use it and I don't see anything wrong with it. I would
> say that 30d is a good period for keeping an issue open.
>
> What do you think?
>
> Bests,
> Tomek
>
Re: Consider using stale bot for issues
Posted by Jarek Potiuk <Ja...@polidea.com>.
I think stalebot is not a good solution for Issues. It is good for PRs (PRs
age much faster than issues and usually if you have not touched the code
for a few weeks, it's better to start from the beginning, unless you
continuously upgrade and "refresh" it.
I do think, however (following what Elad wrote) that organizing the issues
might be a better idea to some extent. And here, I think help from
volunteers from the community - not only committers - might be super
valuable. There is a discussion recently about using the new (still in
public beta) Triage "level" for access in the project and I think what I
liked most is giving everyone from the community an automatically
Trage level of access.
I would be all for it. Maybe there are more people in the community, who
would like to help with that - similar to Elad? If so, maybe then we can
ask the infrastructure to enable the Triage level for us, work out some
general ideas on how we would like to organize the issues, document that,
and ask our community to help with that? This might be a road to
commitership as well for people who are not necessarily coders. Something
that we had a talk at the Airflow Summit (https://youtu.be/wxn9ta13Gbo) ?
Maybe we can pioneer and experiment with that for the whole ASF and help to
reach the decision by showing example :).
Here are the discussions in ASF about the "Triage" level:
Incubator:
https://lists.apache.org/thread.html/r497c5bf9a68e631bc93274e65beb3e28b769ce21e55961407adc5d10%40%3Cgeneral.incubator.apache.org%3E
DevCom discussion:
https://lists.apache.org/thread.html/r617c960eae5a33e8f911c8606f93b6826f2724b3260553a162e2f9f4%40%3Cdev.community.apache.org%3E
J.
On Thu, Sep 10, 2020 at 4:09 PM Elad Kalif <el...@gmail.com> wrote:
> If I opened a bug report - what is the action expected from my side to keep
> it alive?
> Am I supposed to comment on it every 30 days?
>
> Check https://github.com/apache/airflow/pull/10760 was picked after being
> open for 3+ months.
> Keep in mind that not always the person who reports the issue also has the
> skills to create a PR and address it.
>
> Is the actual problem the amount of open issues or the lack of labeling to
> specific areas/providers so it's hard to navigate and manage the list?
> I'm volunteering to help with labeling of current open issues if needed
>
> elad
>
> On Thu, Sep 10, 2020 at 3:54 PM Ash Berlin-Taylor <as...@apache.org> wrote:
>
> > I'm not a fan of these bots for issues.
> >
> > Yes, we have a lot of open issues, but I find it far more demotivating
> > to stumble across an issue on a project only to find it closed due to
> > inactivity -- even if it is still a problem.
> >
> > -ash
> >
> > On Sep 10 2020, at 1:22 pm, Ry Walker <ry...@rywalker.com> wrote:
> >
> > > I agree that stalebot is a best practice and we should use it, and 30d
> > > sounds like a good starting point.
> > >
> > > On Thu, Sep 10, 2020 at 7:56 AM Tomasz Urbaszek <tu...@apache.org>
> > > wrote:
> > >
> > >> Hi all,
> > >>
> > >> Currently, we have about 582 open issues on Github. The oldest opened
> > >> in March. Do you think we should consider using stale bot as we do for
> > >> PRs?
> > >>
> > >> I don't think that issue that is open since March is "so important" to
> > >> keep it still open. This would also automate the process of verifying
> > >> the issue (the author will be notified and asked for an update). If
> > >> the issue is something that we want to keep open we should be able to
> > >> use the "pinned" label.
> > >>
> > >> Other projects use it and I don't see anything wrong with it. I would
> > >> say that 30d is a good period for keeping an issue open.
> > >>
> > >> What do you think?
> > >>
> > >> Bests,
> > >> Tomek
> > >>
> > >
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: Consider using stale bot for issues
Posted by Elad Kalif <el...@gmail.com>.
If I opened a bug report - what is the action expected from my side to keep
it alive?
Am I supposed to comment on it every 30 days?
Check https://github.com/apache/airflow/pull/10760 was picked after being
open for 3+ months.
Keep in mind that not always the person who reports the issue also has the
skills to create a PR and address it.
Is the actual problem the amount of open issues or the lack of labeling to
specific areas/providers so it's hard to navigate and manage the list?
I'm volunteering to help with labeling of current open issues if needed
elad
On Thu, Sep 10, 2020 at 3:54 PM Ash Berlin-Taylor <as...@apache.org> wrote:
> I'm not a fan of these bots for issues.
>
> Yes, we have a lot of open issues, but I find it far more demotivating
> to stumble across an issue on a project only to find it closed due to
> inactivity -- even if it is still a problem.
>
> -ash
>
> On Sep 10 2020, at 1:22 pm, Ry Walker <ry...@rywalker.com> wrote:
>
> > I agree that stalebot is a best practice and we should use it, and 30d
> > sounds like a good starting point.
> >
> > On Thu, Sep 10, 2020 at 7:56 AM Tomasz Urbaszek <tu...@apache.org>
> > wrote:
> >
> >> Hi all,
> >>
> >> Currently, we have about 582 open issues on Github. The oldest opened
> >> in March. Do you think we should consider using stale bot as we do for
> >> PRs?
> >>
> >> I don't think that issue that is open since March is "so important" to
> >> keep it still open. This would also automate the process of verifying
> >> the issue (the author will be notified and asked for an update). If
> >> the issue is something that we want to keep open we should be able to
> >> use the "pinned" label.
> >>
> >> Other projects use it and I don't see anything wrong with it. I would
> >> say that 30d is a good period for keeping an issue open.
> >>
> >> What do you think?
> >>
> >> Bests,
> >> Tomek
> >>
> >
>
Re: Consider using stale bot for issues
Posted by Ash Berlin-Taylor <as...@apache.org>.
I'm not a fan of these bots for issues.
Yes, we have a lot of open issues, but I find it far more demotivating
to stumble across an issue on a project only to find it closed due to
inactivity -- even if it is still a problem.
-ash
On Sep 10 2020, at 1:22 pm, Ry Walker <ry...@rywalker.com> wrote:
> I agree that stalebot is a best practice and we should use it, and 30d
> sounds like a good starting point.
>
> On Thu, Sep 10, 2020 at 7:56 AM Tomasz Urbaszek <tu...@apache.org>
> wrote:
>
>> Hi all,
>>
>> Currently, we have about 582 open issues on Github. The oldest opened
>> in March. Do you think we should consider using stale bot as we do for
>> PRs?
>>
>> I don't think that issue that is open since March is "so important" to
>> keep it still open. This would also automate the process of verifying
>> the issue (the author will be notified and asked for an update). If
>> the issue is something that we want to keep open we should be able to
>> use the "pinned" label.
>>
>> Other projects use it and I don't see anything wrong with it. I would
>> say that 30d is a good period for keeping an issue open.
>>
>> What do you think?
>>
>> Bests,
>> Tomek
>>
>
Re: Consider using stale bot for issues
Posted by Ry Walker <ry...@rywalker.com>.
I agree that stalebot is a best practice and we should use it, and 30d
sounds like a good starting point.
On Thu, Sep 10, 2020 at 7:56 AM Tomasz Urbaszek <tu...@apache.org>
wrote:
> Hi all,
>
> Currently, we have about 582 open issues on Github. The oldest opened
> in March. Do you think we should consider using stale bot as we do for
> PRs?
>
> I don't think that issue that is open since March is "so important" to
> keep it still open. This would also automate the process of verifying
> the issue (the author will be notified and asked for an update). If
> the issue is something that we want to keep open we should be able to
> use the "pinned" label.
>
> Other projects use it and I don't see anything wrong with it. I would
> say that 30d is a good period for keeping an issue open.
>
> What do you think?
>
> Bests,
> Tomek
>
Re: Consider using stale bot for issues
Posted by Daniel Imberman <da...@gmail.com>.
I tried this out today and I am absolutely in love. It certainly needs some work (i.e. making it work for pull requests as well, faster updates, etc.) but this 100x better than the GitHub system right now. I also think that since it is open source, any airflow user who wants to start helping with tickets can easily launch with their own GitHub credentials and give it a try!
I wonder if we can talk to apache infra about setting up a dedicated server for this. It wouldn’t be a very large one (as it’s just a single go executable).
via Newton Mail [https://cloudmagic.com/k/d/mailapp?ct=dx&cv=10.0.51&pv=10.14.6&source=email_footer_2]
On Thu, Oct 1, 2020 at 3:02 PM, Kamil Breguła <ka...@polidea.com> wrote:
I don't know if everyone has had experience managing a project of a similar scale. Even if they did, I think the experience and knowledge of other projects would still be helpful for us. Nobody knows everything.
I agree that community is more important than code, but that doesn't mean we have to do our work manually. At first glance, this tool was a perfect fit for our workflow, so that's why I suggested it.
Now I tried to use this tool and I already have small progress. Unfortunately, I do not have a public server, but I have prepared screenshots and a script to launch the application quickly on the local computer.
Preview: https://imgur.com/a/JeQeP33 [https://imgur.com/a/JeQeP33]
Github project: https://github.com/mik-laj/airflow-triage-party [https://github.com/mik-laj/airflow-triage-party]
If you want, tomorrow I can show you this tool at a standup meeting so that you can evaluate its usefulness.
On Sun, Sep 13, 2020 at 10:57 PM Jarek Potiuk < Jarek.Potiuk@polidea.com [Jarek.Potiuk@polidea.com] > wrote:
@Kamil Breguła [kamil.bregula@polidea.com] - I believe we already base it on the experience of others (see the discussion before). I think in our case the will of people and their commitment to do so is far more important than any tools we would like to use (community over code). I think we should first let the people who want to do it try to do the task and we can introduce tools afterwards. No matter what, those people will need access. And then they can propose and choose any tool that make sense to them.
Paola, Elead,Vikram (and anyone who wants the triage permission) - please state your github users here, so I can create the ticket :)
J.
On Sun, Sep 13, 2020 at 9:40 PM Kamil Breguła < kamil.bregula@polidea.com [kamil.bregula@polidea.com] > wrote:
Hello,
I agree that it is worth considering changes in the way of handling
issues. Google has created a tool that can help us the issue and PR triage
for large open-source projects
https://github.com/google/triage-party [https://github.com/google/triage-party]
It was built from the Google Container DevEx team's experience contributing
to popular open-source projects, such as minikube, Skaffold, and Kaniko. Is
this something we should consider?
How do other projects handle issues? Maybe we can base our process on the
experience of others.
Best regards,
Kamil Breguła
On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka < vikram@astronomer.io [vikram@astronomer.io] > wrote:
> Sounds good!
>
> In the meantime, I will draft up a proposal for the set of labels and
> milestones that we are using to eliminate duplication to factor in the 2.0
> timeline.
>
>
> On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk < Jarek.Potiuk@polidea.com [Jarek.Potiuk@polidea.com] >
> wrote:
>
> > Fantastic initiative!
> >
> > However, currently you have no way to give access to either of the
> > people involved to modify the labels or assign them to issues.
> >
> > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the projects to
> assign
> > people to the "Triage" role I was talking about:
> > https://infra.apache.org/github-roles.html [https://infra.apache.org/github-roles.html]
> >
> > Can you please send me your github issues Vikram, Paola, Elad
> >
> > I will then create an INFRA ticket to add you?
> >
> > Unfortunately, there is no possibility yet to self-manage it, so it has
> to
> > be done through an INFRA ticket and it might take a few days to process.
> >
> > Anyone else willing to join our Triage squad :) ?
> >
> > J.
> >
> >
> > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka < vikram@astronomer.io [vikram@astronomer.io] >
> wrote:
> >
> > > I agree.
> > >
> > > Paola and Elad, I would like to help on this one as well. Let's get
> > > together and nail this.
> > >
> > > I spent a couple of hours looking through the open Github issues
> earlier
> > > today to look for some patterns.
> > > Currently, we have 576 open and "not invalid" issues.
> > > Out of these, we have around:
> > > - 270 open feature requests, which span the full gamut of
> functionality,
> > > from user visible to internal CI process.
> > > - 220 bugs including some going back to March as noted by Tomasz. There
> > > seem to be a fair number of these which need some categorization at
> > least.
> > > - 70 docs issues. These are categorized sometimes as "area:docs" and
> at
> > > other times as "kind:documentation".
> > > - 50 already assigned to milestones: Either Airflow 2.0.0 or 10.10.13
> > > - 80 provider related issues
> > >
> > > There was a set of 6, created in March 2019 which was rather peculiarly
> > > categorized as "Waiting for AIP".
> > >
> > > These don't all add up the total, since there are issues which are
> > > categorized (correctly) in multiple labels. However, we do seem to have
> > > proliferation of labels which would be useful to cleanup.
> > >
> > > Overall, I do think some time spent on documenting the use of labels,
> > then
> > > categorizing and cleaning up the issues would be very useful.
> > >
> > > Happy to help take care of this. Let's do it.
> > >
> > > Vikram
> > >
> > >
> > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
> Jarek.Potiuk@polidea.com [Jarek.Potiuk@polidea.com] >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik < kaxilnaik@gmail.com [kaxilnaik@gmail.com] >
> > wrote:
> > > >
> > > > > Yeah I agree and looks like Paola and Elad have already volunteered
> > to
> > > > help
> > > > > triage.
> > > > >
> > > > > Regards,
> > > > > Kaxil
> > > > >
> > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek < turbaszek@apache.org [turbaszek@apache.org] >
> > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > The main reason I suggested the stale bot was the lack of any
> > > > > > widespread prioritization/reviewing of issues which results in
> big
> > > > > > pile of never addresses issues.
> > > > > >
> > > > > > I think that triage access is a better answer to this problem as
> > > > > > engaging more people will help us all. I'm +1 for that.
> > > > > >
> > > > > > Cheers,
> > > > > > Tomek
> > > > > >
> > > > > >
> > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > > > < paola@astronomer.io [paola@astronomer.io] > wrote:
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Paola here from Astronomer. I've been working at Astro since
> our
> > > > early
> > > > > > days in both Customer and Product-centric roles and have of
> course
> > > been
> > > > > > closely following all-things Airflow for a long time.
> > > > > > >
> > > > > > > I happened to read this conversation around GH Issue management
> > and
> > > > > > figure I can step up to volunteer as someone familiar with the
> > > project
> > > > +
> > > > > > Product Ops principles, if that'd be helpful. I could always
> start
> > > by:
> > > > > > >
> > > > > > > - Cleaning up/commenting on duplicate issues (or close given
> the
> > > > right
> > > > > > permissions)
> > > > > > > - Commenting on stale issues and investigate whether they're
> > still
> > > a
> > > > > > problem or already addressed
> > > > > > > - Asking questions as needed if issues need clarification or
> > > > additional
> > > > > > scoping
> > > > > > >
> > > > > > > If this would be helpful, I'm more than happy to get involved
> and
> > > > pick
> > > > > > at these over time. It'll likely be a journey that never ends,
> but
> > I
> > > > > think
> > > > > > a compelling need to keep the community momentum going. Let me
> > know -
> > > > and
> > > > > > great to meet you all.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Paola
> > > > > > >
> > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek < turbaszek@apache.org [turbaszek@apache.org] >
> > > > wrote:
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Currently, we have about 582 open issues on Github. The
> oldest
> > > > opened
> > > > > > > > in March. Do you think we should consider using stale bot as
> we
> > > do
> > > > > for
> > > > > > > > PRs?
> > > > > > > >
> > > > > > > > I don't think that issue that is open since March is "so
> > > important"
> > > > > to
> > > > > > > > keep it still open. This would also automate the process of
> > > > verifying
> > > > > > > > the issue (the author will be notified and asked for an
> > update).
> > > If
> > > > > > > > the issue is something that we want to keep open we should be
> > > able
> > > > to
> > > > > > > > use the "pinned" label.
> > > > > > > >
> > > > > > > > Other projects use it and I don't see anything wrong with
> it. I
> > > > would
> > > > > > > > say that 30d is a good period for keeping an issue open.
> > > > > > > >
> > > > > > > > What do you think?
> > > > > > > >
> > > > > > > > Bests,
> > > > > > > > Tomek
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea < https://www.polidea.com/ [https://www.polidea.com/] > | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > [image: Polidea] < https://www.polidea.com/ [https://www.polidea.com/] >
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea < https://www.polidea.com/ [https://www.polidea.com/] > | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] < https://www.polidea.com/ [https://www.polidea.com/] >
> >
>
--
Jarek Potiuk
Polidea [https://www.polidea.com/] | Principal Software Engineer
M: +48 660 796 129 [tel:+48660796129]
[https://www.polidea.com/]
Re: Consider using stale bot for issues
Posted by Kamil Breguła <ka...@polidea.com>.
I don't know if everyone has had experience managing a project of a similar
scale. Even if they did, I think the experience and knowledge of other
projects would still be helpful for us. Nobody knows everything.
I agree that community is more important than code, but that doesn't mean
we have to do our work manually. At first glance, this tool was a perfect
fit for our workflow, so that's why I suggested it.
Now I tried to use this tool and I already have small
progress. Unfortunately, I do not have a public server, but I have prepared
screenshots and a script to launch the application quickly on the local
computer.
Preview: https://imgur.com/a/JeQeP33
Github project: https://github.com/mik-laj/airflow-triage-party
If you want, tomorrow I can show you this tool at a standup meeting so that
you can evaluate its usefulness.
On Sun, Sep 13, 2020 at 10:57 PM Jarek Potiuk <Ja...@polidea.com>
wrote:
> @Kamil Breguła <ka...@polidea.com> - I believe we already base
> it on the experience of others (see the discussion before). I think in our
> case the will of people and their commitment to do so is far more important
> than any tools we would like to use (community over code). I think we
> should first let the people who want to do it try to do the task and we can
> introduce tools afterwards. No matter what, those people will need access.
> And then they can propose and choose any tool that make sense to them.
>
> Paola, Elead,Vikram (and anyone who wants the triage permission) - please
> state your github users here, so I can create the ticket :)
>
> J.
>
>
> On Sun, Sep 13, 2020 at 9:40 PM Kamil Breguła <ka...@polidea.com>
> wrote:
>
>> Hello,
>>
>> I agree that it is worth considering changes in the way of handling
>> issues. Google has created a tool that can help us the issue and PR triage
>> for large open-source projects
>> https://github.com/google/triage-party
>> It was built from the Google Container DevEx team's experience
>> contributing
>> to popular open-source projects, such as minikube, Skaffold, and Kaniko.
>> Is
>> this something we should consider?
>>
>> How do other projects handle issues? Maybe we can base our process on the
>> experience of others.
>>
>> Best regards,
>> Kamil Breguła
>>
>> On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka <vi...@astronomer.io> wrote:
>>
>> > Sounds good!
>> >
>> > In the meantime, I will draft up a proposal for the set of labels and
>> > milestones that we are using to eliminate duplication to factor in the
>> 2.0
>> > timeline.
>> >
>> >
>> > On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <Ja...@polidea.com>
>> > wrote:
>> >
>> > > Fantastic initiative!
>> > >
>> > > However, currently you have no way to give access to either of the
>> > > people involved to modify the labels or assign them to issues.
>> > >
>> > > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the projects to
>> > assign
>> > > people to the "Triage" role I was talking about:
>> > > https://infra.apache.org/github-roles.html
>> > >
>> > > Can you please send me your github issues Vikram, Paola, Elad
>> > >
>> > > I will then create an INFRA ticket to add you?
>> > >
>> > > Unfortunately, there is no possibility yet to self-manage it, so it
>> has
>> > to
>> > > be done through an INFRA ticket and it might take a few days to
>> process.
>> > >
>> > > Anyone else willing to join our Triage squad :) ?
>> > >
>> > > J.
>> > >
>> > >
>> > > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <vi...@astronomer.io>
>> > wrote:
>> > >
>> > > > I agree.
>> > > >
>> > > > Paola and Elad, I would like to help on this one as well. Let's get
>> > > > together and nail this.
>> > > >
>> > > > I spent a couple of hours looking through the open Github issues
>> > earlier
>> > > > today to look for some patterns.
>> > > > Currently, we have 576 open and "not invalid" issues.
>> > > > Out of these, we have around:
>> > > > - 270 open feature requests, which span the full gamut of
>> > functionality,
>> > > > from user visible to internal CI process.
>> > > > - 220 bugs including some going back to March as noted by Tomasz.
>> There
>> > > > seem to be a fair number of these which need some categorization at
>> > > least.
>> > > > - 70 docs issues. These are categorized sometimes as "area:docs"
>> and
>> > at
>> > > > other times as "kind:documentation".
>> > > > - 50 already assigned to milestones: Either Airflow 2.0.0 or
>> 10.10.13
>> > > > - 80 provider related issues
>> > > >
>> > > > There was a set of 6, created in March 2019 which was rather
>> peculiarly
>> > > > categorized as "Waiting for AIP".
>> > > >
>> > > > These don't all add up the total, since there are issues which are
>> > > > categorized (correctly) in multiple labels. However, we do seem to
>> have
>> > > > proliferation of labels which would be useful to cleanup.
>> > > >
>> > > > Overall, I do think some time spent on documenting the use of
>> labels,
>> > > then
>> > > > categorizing and cleaning up the issues would be very useful.
>> > > >
>> > > > Happy to help take care of this. Let's do it.
>> > > >
>> > > > Vikram
>> > > >
>> > > >
>> > > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
>> > Jarek.Potiuk@polidea.com>
>> > > > wrote:
>> > > >
>> > > > > +1
>> > > > >
>> > > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <ka...@gmail.com>
>> > > wrote:
>> > > > >
>> > > > > > Yeah I agree and looks like Paola and Elad have already
>> volunteered
>> > > to
>> > > > > help
>> > > > > > triage.
>> > > > > >
>> > > > > > Regards,
>> > > > > > Kaxil
>> > > > > >
>> > > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <
>> turbaszek@apache.org>
>> > > > > wrote:
>> > > > > >
>> > > > > > > Hi all,
>> > > > > > >
>> > > > > > > The main reason I suggested the stale bot was the lack of any
>> > > > > > > widespread prioritization/reviewing of issues which results in
>> > big
>> > > > > > > pile of never addresses issues.
>> > > > > > >
>> > > > > > > I think that triage access is a better answer to this problem
>> as
>> > > > > > > engaging more people will help us all. I'm +1 for that.
>> > > > > > >
>> > > > > > > Cheers,
>> > > > > > > Tomek
>> > > > > > >
>> > > > > > >
>> > > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
>> > > > > > > <pa...@astronomer.io> wrote:
>> > > > > > > >
>> > > > > > > > Hi all,
>> > > > > > > >
>> > > > > > > > Paola here from Astronomer. I've been working at Astro since
>> > our
>> > > > > early
>> > > > > > > days in both Customer and Product-centric roles and have of
>> > course
>> > > > been
>> > > > > > > closely following all-things Airflow for a long time.
>> > > > > > > >
>> > > > > > > > I happened to read this conversation around GH Issue
>> management
>> > > and
>> > > > > > > figure I can step up to volunteer as someone familiar with the
>> > > > project
>> > > > > +
>> > > > > > > Product Ops principles, if that'd be helpful. I could always
>> > start
>> > > > by:
>> > > > > > > >
>> > > > > > > > - Cleaning up/commenting on duplicate issues (or close given
>> > the
>> > > > > right
>> > > > > > > permissions)
>> > > > > > > > - Commenting on stale issues and investigate whether they're
>> > > still
>> > > > a
>> > > > > > > problem or already addressed
>> > > > > > > > - Asking questions as needed if issues need clarification or
>> > > > > additional
>> > > > > > > scoping
>> > > > > > > >
>> > > > > > > > If this would be helpful, I'm more than happy to get
>> involved
>> > and
>> > > > > pick
>> > > > > > > at these over time. It'll likely be a journey that never ends,
>> > but
>> > > I
>> > > > > > think
>> > > > > > > a compelling need to keep the community momentum going. Let me
>> > > know -
>> > > > > and
>> > > > > > > great to meet you all.
>> > > > > > > >
>> > > > > > > > Cheers,
>> > > > > > > > Paola
>> > > > > > > >
>> > > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
>> turbaszek@apache.org>
>> > > > > wrote:
>> > > > > > > > > Hi all,
>> > > > > > > > >
>> > > > > > > > > Currently, we have about 582 open issues on Github. The
>> > oldest
>> > > > > opened
>> > > > > > > > > in March. Do you think we should consider using stale bot
>> as
>> > we
>> > > > do
>> > > > > > for
>> > > > > > > > > PRs?
>> > > > > > > > >
>> > > > > > > > > I don't think that issue that is open since March is "so
>> > > > important"
>> > > > > > to
>> > > > > > > > > keep it still open. This would also automate the process
>> of
>> > > > > verifying
>> > > > > > > > > the issue (the author will be notified and asked for an
>> > > update).
>> > > > If
>> > > > > > > > > the issue is something that we want to keep open we
>> should be
>> > > > able
>> > > > > to
>> > > > > > > > > use the "pinned" label.
>> > > > > > > > >
>> > > > > > > > > Other projects use it and I don't see anything wrong with
>> > it. I
>> > > > > would
>> > > > > > > > > say that 30d is a good period for keeping an issue open.
>> > > > > > > > >
>> > > > > > > > > What do you think?
>> > > > > > > > >
>> > > > > > > > > Bests,
>> > > > > > > > > Tomek
>> > > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > >
>> > > > > Jarek Potiuk
>> > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
>> > > > >
>> > > > > M: +48 660 796 129 <+48660796129>
>> > > > > [image: Polidea] <https://www.polidea.com/>
>> > > > >
>> > > >
>> > >
>> > >
>> > > --
>> > >
>> > > Jarek Potiuk
>> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
>> > >
>> > > M: +48 660 796 129 <+48660796129>
>> > > [image: Polidea] <https://www.polidea.com/>
>> > >
>> >
>>
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
>
Re: Consider using stale bot for issues
Posted by Jarek Potiuk <Ja...@polidea.com>.
Ticket created: https://issues.apache.org/jira/browse/INFRA-20843, Paola -
I will add you to the list when I get your GitHub username :).
J.
On Mon, Sep 14, 2020 at 8:00 AM Jarek Potiuk <Ja...@polidea.com>
wrote:
> Good one Max :). I think eventually we will get to a place where we will
> be able to manage it via .asf-config (I guess it's coming) and eventually
> maybe we also can try to get the Triage role for everyone. There is a nice
> value in being able to use the native Github labelling interface
> (especially bulk management would be rather difficult to replicate). I will
> go ahead and create ticket now , and ask INFRA about potential improvements
> to the process they're working on.
>
> J.
>
>
> On Mon, Sep 14, 2020 at 6:37 AM Maxime Beauchemin <
> maximebeauchemin@gmail.com> wrote:
>
>> About labeling on Github, I wrote a bot for Superset that enables anyone
>> to
>> apply labels through commenting using emojis.
>>
>> It does other things like auto-labeling organization on an allow-list. We
>> could teach it new tricks top.
>>
>> Generalizing it or porting it to work in other communities should be
>> very easy.
>>
>> I've also been advocating for the ASF to open up the triage role, but was
>> hoping to use .asf-config.yaml and avoid the voting process...
>>
>> Check it out the bot here:
>> https://github.com/apache-superset/superset-github-bot
>>
>> On Sun, Sep 13, 2020, 7:56 PM Vikram Koka <vi...@astronomer.io> wrote:
>>
>> > Mine is @vikramkoka
>> >
>> >
>> >
>> > On Sun, Sep 13, 2020 at 7:29 PM Elad Kalif <el...@gmail.com> wrote:
>> >
>> > > mine is @eladkal
>> > >
>> > > On Mon, Sep 14, 2020 at 4:33 AM Pete DeJoy <pd...@gmail.com>
>> wrote:
>> > >
>> > > > I’d love to help as well! Gh handle is @petedejoy
>> > > >
>> > > > Thanks for organizing everyone.
>> > > >
>> > > > Pete
>> > > > On Sep 13, 2020, 4:57 PM -0400, Jarek Potiuk <
>> Jarek.Potiuk@polidea.com
>> > >,
>> > > > wrote:
>> > > > > @Kamil Breguła <ka...@polidea.com> - I believe we already
>> > base
>> > > > it
>> > > > > on the experience of others (see the discussion before). I think
>> in
>> > our
>> > > > > case the will of people and their commitment to do so is far more
>> > > > important
>> > > > > than any tools we would like to use (community over code). I
>> think we
>> > > > > should first let the people who want to do it try to do the task
>> and
>> > we
>> > > > can
>> > > > > introduce tools afterwards. No matter what, those people will need
>> > > > access.
>> > > > > And then they can propose and choose any tool that make sense to
>> > them.
>> > > > >
>> > > > > Paola, Elead,Vikram (and anyone who wants the triage permission) -
>> > > please
>> > > > > state your github users here, so I can create the ticket :)
>> > > > >
>> > > > > J.
>> > > > >
>> > > > >
>> > > > > On Sun, Sep 13, 2020 at 9:40 PM Kamil Breguła <
>> > > kamil.bregula@polidea.com
>> > > > >
>> > > > > wrote:
>> > > > >
>> > > > > > Hello,
>> > > > > >
>> > > > > > I agree that it is worth considering changes in the way of
>> handling
>> > > > > > issues. Google has created a tool that can help us the issue
>> and PR
>> > > > triage
>> > > > > > for large open-source projects
>> > > > > > https://github.com/google/triage-party
>> > > > > > It was built from the Google Container DevEx team's experience
>> > > > contributing
>> > > > > > to popular open-source projects, such as minikube, Skaffold, and
>> > > > Kaniko. Is
>> > > > > > this something we should consider?
>> > > > > >
>> > > > > > How do other projects handle issues? Maybe we can base our
>> process
>> > on
>> > > > the
>> > > > > > experience of others.
>> > > > > >
>> > > > > > Best regards,
>> > > > > > Kamil Breguła
>> > > > > >
>> > > > > > On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka <
>> vikram@astronomer.io>
>> > > > wrote:
>> > > > > >
>> > > > > > > Sounds good!
>> > > > > > >
>> > > > > > > In the meantime, I will draft up a proposal for the set of
>> labels
>> > > and
>> > > > > > > milestones that we are using to eliminate duplication to
>> factor
>> > in
>> > > > the
>> > > > > > 2.0
>> > > > > > > timeline.
>> > > > > > >
>> > > > > > >
>> > > > > > > On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <
>> > > > Jarek.Potiuk@polidea.com>
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > > > Fantastic initiative!
>> > > > > > > >
>> > > > > > > > However, currently you have no way to give access to either
>> of
>> > > the
>> > > > > > > > people involved to modify the labels or assign them to
>> issues.
>> > > > > > > >
>> > > > > > > > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the
>> > projects
>> > > > to
>> > > > > > > assign
>> > > > > > > > people to the "Triage" role I was talking about:
>> > > > > > > > https://infra.apache.org/github-roles.html
>> > > > > > > >
>> > > > > > > > Can you please send me your github issues Vikram, Paola,
>> Elad
>> > > > > > > >
>> > > > > > > > I will then create an INFRA ticket to add you?
>> > > > > > > >
>> > > > > > > > Unfortunately, there is no possibility yet to self-manage
>> it,
>> > so
>> > > > it has
>> > > > > > > to
>> > > > > > > > be done through an INFRA ticket and it might take a few
>> days to
>> > > > > > process.
>> > > > > > > >
>> > > > > > > > Anyone else willing to join our Triage squad :) ?
>> > > > > > > >
>> > > > > > > > J.
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <
>> > > vikram@astronomer.io>
>> > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > > I agree.
>> > > > > > > > >
>> > > > > > > > > Paola and Elad, I would like to help on this one as well.
>> > Let's
>> > > > get
>> > > > > > > > > together and nail this.
>> > > > > > > > >
>> > > > > > > > > I spent a couple of hours looking through the open Github
>> > > issues
>> > > > > > > earlier
>> > > > > > > > > today to look for some patterns.
>> > > > > > > > > Currently, we have 576 open and "not invalid" issues.
>> > > > > > > > > Out of these, we have around:
>> > > > > > > > > - 270 open feature requests, which span the full gamut of
>> > > > > > > functionality,
>> > > > > > > > > from user visible to internal CI process.
>> > > > > > > > > - 220 bugs including some going back to March as noted by
>> > > Tomasz.
>> > > > > > There
>> > > > > > > > > seem to be a fair number of these which need some
>> > > categorization
>> > > > at
>> > > > > > > > least.
>> > > > > > > > > - 70 docs issues. These are categorized sometimes as
>> > > "area:docs"
>> > > > and
>> > > > > > > at
>> > > > > > > > > other times as "kind:documentation".
>> > > > > > > > > - 50 already assigned to milestones: Either Airflow 2.0.0
>> or
>> > > > > > 10.10.13
>> > > > > > > > > - 80 provider related issues
>> > > > > > > > >
>> > > > > > > > > There was a set of 6, created in March 2019 which was
>> rather
>> > > > > > peculiarly
>> > > > > > > > > categorized as "Waiting for AIP".
>> > > > > > > > >
>> > > > > > > > > These don't all add up the total, since there are issues
>> > which
>> > > > are
>> > > > > > > > > categorized (correctly) in multiple labels. However, we do
>> > seem
>> > > > to
>> > > > > > have
>> > > > > > > > > proliferation of labels which would be useful to cleanup.
>> > > > > > > > >
>> > > > > > > > > Overall, I do think some time spent on documenting the
>> use of
>> > > > labels,
>> > > > > > > > then
>> > > > > > > > > categorizing and cleaning up the issues would be very
>> useful.
>> > > > > > > > >
>> > > > > > > > > Happy to help take care of this. Let's do it.
>> > > > > > > > >
>> > > > > > > > > Vikram
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
>> > > > > > > Jarek.Potiuk@polidea.com>
>> > > > > > > > > wrote:
>> > > > > > > > >
>> > > > > > > > > > +1
>> > > > > > > > > >
>> > > > > > > > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <
>> > > > kaxilnaik@gmail.com>
>> > > > > > > > wrote:
>> > > > > > > > > >
>> > > > > > > > > > > Yeah I agree and looks like Paola and Elad have
>> already
>> > > > > > volunteered
>> > > > > > > > to
>> > > > > > > > > > help
>> > > > > > > > > > > triage.
>> > > > > > > > > > >
>> > > > > > > > > > > Regards,
>> > > > > > > > > > > Kaxil
>> > > > > > > > > > >
>> > > > > > > > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <
>> > > > > > turbaszek@apache.org>
>> > > > > > > > > > wrote:
>> > > > > > > > > > >
>> > > > > > > > > > > > Hi all,
>> > > > > > > > > > > >
>> > > > > > > > > > > > The main reason I suggested the stale bot was the
>> lack
>> > of
>> > > > any
>> > > > > > > > > > > > widespread prioritization/reviewing of issues which
>> > > > results in
>> > > > > > > big
>> > > > > > > > > > > > pile of never addresses issues.
>> > > > > > > > > > > >
>> > > > > > > > > > > > I think that triage access is a better answer to
>> this
>> > > > problem
>> > > > > > as
>> > > > > > > > > > > > engaging more people will help us all. I'm +1 for
>> that.
>> > > > > > > > > > > >
>> > > > > > > > > > > > Cheers,
>> > > > > > > > > > > > Tomek
>> > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza
>> Calderon
>> > > > > > > > > > > > <pa...@astronomer.io> wrote:
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > Hi all,
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > Paola here from Astronomer. I've been working at
>> > Astro
>> > > > since
>> > > > > > > our
>> > > > > > > > > > early
>> > > > > > > > > > > > days in both Customer and Product-centric roles and
>> > have
>> > > of
>> > > > > > > course
>> > > > > > > > > been
>> > > > > > > > > > > > closely following all-things Airflow for a long
>> time.
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > I happened to read this conversation around GH
>> Issue
>> > > > > > management
>> > > > > > > > and
>> > > > > > > > > > > > figure I can step up to volunteer as someone
>> familiar
>> > > with
>> > > > the
>> > > > > > > > > project
>> > > > > > > > > > +
>> > > > > > > > > > > > Product Ops principles, if that'd be helpful. I
>> could
>> > > > always
>> > > > > > > start
>> > > > > > > > > by:
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > - Cleaning up/commenting on duplicate issues (or
>> > close
>> > > > given
>> > > > > > > the
>> > > > > > > > > > right
>> > > > > > > > > > > > permissions)
>> > > > > > > > > > > > > - Commenting on stale issues and investigate
>> whether
>> > > > they're
>> > > > > > > > still
>> > > > > > > > > a
>> > > > > > > > > > > > problem or already addressed
>> > > > > > > > > > > > > - Asking questions as needed if issues need
>> > > > clarification or
>> > > > > > > > > > additional
>> > > > > > > > > > > > scoping
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > If this would be helpful, I'm more than happy to
>> get
>> > > > involved
>> > > > > > > and
>> > > > > > > > > > pick
>> > > > > > > > > > > > at these over time. It'll likely be a journey that
>> > never
>> > > > ends,
>> > > > > > > but
>> > > > > > > > I
>> > > > > > > > > > > think
>> > > > > > > > > > > > a compelling need to keep the community momentum
>> going.
>> > > > Let me
>> > > > > > > > know -
>> > > > > > > > > > and
>> > > > > > > > > > > > great to meet you all.
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > Cheers,
>> > > > > > > > > > > > > Paola
>> > > > > > > > > > > > >
>> > > > > > > > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
>> > > > > > turbaszek@apache.org>
>> > > > > > > > > > wrote:
>> > > > > > > > > > > > > > Hi all,
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > Currently, we have about 582 open issues on
>> Github.
>> > > The
>> > > > > > > oldest
>> > > > > > > > > > opened
>> > > > > > > > > > > > > > in March. Do you think we should consider using
>> > stale
>> > > > bot
>> > > > > > as
>> > > > > > > we
>> > > > > > > > > do
>> > > > > > > > > > > for
>> > > > > > > > > > > > > > PRs?
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > I don't think that issue that is open since
>> March
>> > is
>> > > > "so
>> > > > > > > > > important"
>> > > > > > > > > > > to
>> > > > > > > > > > > > > > keep it still open. This would also automate the
>> > > > process of
>> > > > > > > > > > verifying
>> > > > > > > > > > > > > > the issue (the author will be notified and asked
>> > for
>> > > an
>> > > > > > > > update).
>> > > > > > > > > If
>> > > > > > > > > > > > > > the issue is something that we want to keep
>> open we
>> > > > should
>> > > > > > be
>> > > > > > > > > able
>> > > > > > > > > > to
>> > > > > > > > > > > > > > use the "pinned" label.
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > Other projects use it and I don't see anything
>> > wrong
>> > > > with
>> > > > > > > it. I
>> > > > > > > > > > would
>> > > > > > > > > > > > > > say that 30d is a good period for keeping an
>> issue
>> > > > open.
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > What do you think?
>> > > > > > > > > > > > > >
>> > > > > > > > > > > > > > Bests,
>> > > > > > > > > > > > > > Tomek
>> > > > > > > > > > > > > >
>> > > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > --
>> > > > > > > > > >
>> > > > > > > > > > Jarek Potiuk
>> > > > > > > > > > Polidea <https://www.polidea.com/> | Principal Software
>> > > > Engineer
>> > > > > > > > > >
>> > > > > > > > > > M: +48 660 796 129 <+48660796129>
>> > > > > > > > > > [image: Polidea] <https://www.polidea.com/>
>> > > > > > > > > >
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > --
>> > > > > > > >
>> > > > > > > > Jarek Potiuk
>> > > > > > > > Polidea <https://www.polidea.com/> | Principal Software
>> > Engineer
>> > > > > > > >
>> > > > > > > > M: +48 660 796 129 <+48660796129>
>> > > > > > > > [image: Polidea] <https://www.polidea.com/>
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > > > --
>> > > > >
>> > > > > Jarek Potiuk
>> > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
>> > > > >
>> > > > > M: +48 660 796 129 <+48660796129>
>> > > > > [image: Polidea] <https://www.polidea.com/>
>> > > >
>> > >
>> >
>>
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: Consider using stale bot for issues
Posted by Jarek Potiuk <Ja...@polidea.com>.
Good one Max :). I think eventually we will get to a place where we will be
able to manage it via .asf-config (I guess it's coming) and eventually
maybe we also can try to get the Triage role for everyone. There is a nice
value in being able to use the native Github labelling interface
(especially bulk management would be rather difficult to replicate). I will
go ahead and create ticket now , and ask INFRA about potential improvements
to the process they're working on.
J.
On Mon, Sep 14, 2020 at 6:37 AM Maxime Beauchemin <
maximebeauchemin@gmail.com> wrote:
> About labeling on Github, I wrote a bot for Superset that enables anyone to
> apply labels through commenting using emojis.
>
> It does other things like auto-labeling organization on an allow-list. We
> could teach it new tricks top.
>
> Generalizing it or porting it to work in other communities should be
> very easy.
>
> I've also been advocating for the ASF to open up the triage role, but was
> hoping to use .asf-config.yaml and avoid the voting process...
>
> Check it out the bot here:
> https://github.com/apache-superset/superset-github-bot
>
> On Sun, Sep 13, 2020, 7:56 PM Vikram Koka <vi...@astronomer.io> wrote:
>
> > Mine is @vikramkoka
> >
> >
> >
> > On Sun, Sep 13, 2020 at 7:29 PM Elad Kalif <el...@gmail.com> wrote:
> >
> > > mine is @eladkal
> > >
> > > On Mon, Sep 14, 2020 at 4:33 AM Pete DeJoy <pd...@gmail.com> wrote:
> > >
> > > > I’d love to help as well! Gh handle is @petedejoy
> > > >
> > > > Thanks for organizing everyone.
> > > >
> > > > Pete
> > > > On Sep 13, 2020, 4:57 PM -0400, Jarek Potiuk <
> Jarek.Potiuk@polidea.com
> > >,
> > > > wrote:
> > > > > @Kamil Breguła <ka...@polidea.com> - I believe we already
> > base
> > > > it
> > > > > on the experience of others (see the discussion before). I think in
> > our
> > > > > case the will of people and their commitment to do so is far more
> > > > important
> > > > > than any tools we would like to use (community over code). I think
> we
> > > > > should first let the people who want to do it try to do the task
> and
> > we
> > > > can
> > > > > introduce tools afterwards. No matter what, those people will need
> > > > access.
> > > > > And then they can propose and choose any tool that make sense to
> > them.
> > > > >
> > > > > Paola, Elead,Vikram (and anyone who wants the triage permission) -
> > > please
> > > > > state your github users here, so I can create the ticket :)
> > > > >
> > > > > J.
> > > > >
> > > > >
> > > > > On Sun, Sep 13, 2020 at 9:40 PM Kamil Breguła <
> > > kamil.bregula@polidea.com
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Hello,
> > > > > >
> > > > > > I agree that it is worth considering changes in the way of
> handling
> > > > > > issues. Google has created a tool that can help us the issue and
> PR
> > > > triage
> > > > > > for large open-source projects
> > > > > > https://github.com/google/triage-party
> > > > > > It was built from the Google Container DevEx team's experience
> > > > contributing
> > > > > > to popular open-source projects, such as minikube, Skaffold, and
> > > > Kaniko. Is
> > > > > > this something we should consider?
> > > > > >
> > > > > > How do other projects handle issues? Maybe we can base our
> process
> > on
> > > > the
> > > > > > experience of others.
> > > > > >
> > > > > > Best regards,
> > > > > > Kamil Breguła
> > > > > >
> > > > > > On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka <
> vikram@astronomer.io>
> > > > wrote:
> > > > > >
> > > > > > > Sounds good!
> > > > > > >
> > > > > > > In the meantime, I will draft up a proposal for the set of
> labels
> > > and
> > > > > > > milestones that we are using to eliminate duplication to factor
> > in
> > > > the
> > > > > > 2.0
> > > > > > > timeline.
> > > > > > >
> > > > > > >
> > > > > > > On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <
> > > > Jarek.Potiuk@polidea.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Fantastic initiative!
> > > > > > > >
> > > > > > > > However, currently you have no way to give access to either
> of
> > > the
> > > > > > > > people involved to modify the labels or assign them to
> issues.
> > > > > > > >
> > > > > > > > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the
> > projects
> > > > to
> > > > > > > assign
> > > > > > > > people to the "Triage" role I was talking about:
> > > > > > > > https://infra.apache.org/github-roles.html
> > > > > > > >
> > > > > > > > Can you please send me your github issues Vikram, Paola, Elad
> > > > > > > >
> > > > > > > > I will then create an INFRA ticket to add you?
> > > > > > > >
> > > > > > > > Unfortunately, there is no possibility yet to self-manage it,
> > so
> > > > it has
> > > > > > > to
> > > > > > > > be done through an INFRA ticket and it might take a few days
> to
> > > > > > process.
> > > > > > > >
> > > > > > > > Anyone else willing to join our Triage squad :) ?
> > > > > > > >
> > > > > > > > J.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <
> > > vikram@astronomer.io>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > I agree.
> > > > > > > > >
> > > > > > > > > Paola and Elad, I would like to help on this one as well.
> > Let's
> > > > get
> > > > > > > > > together and nail this.
> > > > > > > > >
> > > > > > > > > I spent a couple of hours looking through the open Github
> > > issues
> > > > > > > earlier
> > > > > > > > > today to look for some patterns.
> > > > > > > > > Currently, we have 576 open and "not invalid" issues.
> > > > > > > > > Out of these, we have around:
> > > > > > > > > - 270 open feature requests, which span the full gamut of
> > > > > > > functionality,
> > > > > > > > > from user visible to internal CI process.
> > > > > > > > > - 220 bugs including some going back to March as noted by
> > > Tomasz.
> > > > > > There
> > > > > > > > > seem to be a fair number of these which need some
> > > categorization
> > > > at
> > > > > > > > least.
> > > > > > > > > - 70 docs issues. These are categorized sometimes as
> > > "area:docs"
> > > > and
> > > > > > > at
> > > > > > > > > other times as "kind:documentation".
> > > > > > > > > - 50 already assigned to milestones: Either Airflow 2.0.0
> or
> > > > > > 10.10.13
> > > > > > > > > - 80 provider related issues
> > > > > > > > >
> > > > > > > > > There was a set of 6, created in March 2019 which was
> rather
> > > > > > peculiarly
> > > > > > > > > categorized as "Waiting for AIP".
> > > > > > > > >
> > > > > > > > > These don't all add up the total, since there are issues
> > which
> > > > are
> > > > > > > > > categorized (correctly) in multiple labels. However, we do
> > seem
> > > > to
> > > > > > have
> > > > > > > > > proliferation of labels which would be useful to cleanup.
> > > > > > > > >
> > > > > > > > > Overall, I do think some time spent on documenting the use
> of
> > > > labels,
> > > > > > > > then
> > > > > > > > > categorizing and cleaning up the issues would be very
> useful.
> > > > > > > > >
> > > > > > > > > Happy to help take care of this. Let's do it.
> > > > > > > > >
> > > > > > > > > Vikram
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
> > > > > > > Jarek.Potiuk@polidea.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <
> > > > kaxilnaik@gmail.com>
> > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Yeah I agree and looks like Paola and Elad have already
> > > > > > volunteered
> > > > > > > > to
> > > > > > > > > > help
> > > > > > > > > > > triage.
> > > > > > > > > > >
> > > > > > > > > > > Regards,
> > > > > > > > > > > Kaxil
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <
> > > > > > turbaszek@apache.org>
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hi all,
> > > > > > > > > > > >
> > > > > > > > > > > > The main reason I suggested the stale bot was the
> lack
> > of
> > > > any
> > > > > > > > > > > > widespread prioritization/reviewing of issues which
> > > > results in
> > > > > > > big
> > > > > > > > > > > > pile of never addresses issues.
> > > > > > > > > > > >
> > > > > > > > > > > > I think that triage access is a better answer to this
> > > > problem
> > > > > > as
> > > > > > > > > > > > engaging more people will help us all. I'm +1 for
> that.
> > > > > > > > > > > >
> > > > > > > > > > > > Cheers,
> > > > > > > > > > > > Tomek
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > > > > > > > > > <pa...@astronomer.io> wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Paola here from Astronomer. I've been working at
> > Astro
> > > > since
> > > > > > > our
> > > > > > > > > > early
> > > > > > > > > > > > days in both Customer and Product-centric roles and
> > have
> > > of
> > > > > > > course
> > > > > > > > > been
> > > > > > > > > > > > closely following all-things Airflow for a long time.
> > > > > > > > > > > > >
> > > > > > > > > > > > > I happened to read this conversation around GH
> Issue
> > > > > > management
> > > > > > > > and
> > > > > > > > > > > > figure I can step up to volunteer as someone familiar
> > > with
> > > > the
> > > > > > > > > project
> > > > > > > > > > +
> > > > > > > > > > > > Product Ops principles, if that'd be helpful. I could
> > > > always
> > > > > > > start
> > > > > > > > > by:
> > > > > > > > > > > > >
> > > > > > > > > > > > > - Cleaning up/commenting on duplicate issues (or
> > close
> > > > given
> > > > > > > the
> > > > > > > > > > right
> > > > > > > > > > > > permissions)
> > > > > > > > > > > > > - Commenting on stale issues and investigate
> whether
> > > > they're
> > > > > > > > still
> > > > > > > > > a
> > > > > > > > > > > > problem or already addressed
> > > > > > > > > > > > > - Asking questions as needed if issues need
> > > > clarification or
> > > > > > > > > > additional
> > > > > > > > > > > > scoping
> > > > > > > > > > > > >
> > > > > > > > > > > > > If this would be helpful, I'm more than happy to
> get
> > > > involved
> > > > > > > and
> > > > > > > > > > pick
> > > > > > > > > > > > at these over time. It'll likely be a journey that
> > never
> > > > ends,
> > > > > > > but
> > > > > > > > I
> > > > > > > > > > > think
> > > > > > > > > > > > a compelling need to keep the community momentum
> going.
> > > > Let me
> > > > > > > > know -
> > > > > > > > > > and
> > > > > > > > > > > > great to meet you all.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Cheers,
> > > > > > > > > > > > > Paola
> > > > > > > > > > > > >
> > > > > > > > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
> > > > > > turbaszek@apache.org>
> > > > > > > > > > wrote:
> > > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Currently, we have about 582 open issues on
> Github.
> > > The
> > > > > > > oldest
> > > > > > > > > > opened
> > > > > > > > > > > > > > in March. Do you think we should consider using
> > stale
> > > > bot
> > > > > > as
> > > > > > > we
> > > > > > > > > do
> > > > > > > > > > > for
> > > > > > > > > > > > > > PRs?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I don't think that issue that is open since March
> > is
> > > > "so
> > > > > > > > > important"
> > > > > > > > > > > to
> > > > > > > > > > > > > > keep it still open. This would also automate the
> > > > process of
> > > > > > > > > > verifying
> > > > > > > > > > > > > > the issue (the author will be notified and asked
> > for
> > > an
> > > > > > > > update).
> > > > > > > > > If
> > > > > > > > > > > > > > the issue is something that we want to keep open
> we
> > > > should
> > > > > > be
> > > > > > > > > able
> > > > > > > > > > to
> > > > > > > > > > > > > > use the "pinned" label.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Other projects use it and I don't see anything
> > wrong
> > > > with
> > > > > > > it. I
> > > > > > > > > > would
> > > > > > > > > > > > > > say that 30d is a good period for keeping an
> issue
> > > > open.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > What do you think?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Bests,
> > > > > > > > > > > > > > Tomek
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > >
> > > > > > > > > > Jarek Potiuk
> > > > > > > > > > Polidea <https://www.polidea.com/> | Principal Software
> > > > Engineer
> > > > > > > > > >
> > > > > > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > Jarek Potiuk
> > > > > > > > Polidea <https://www.polidea.com/> | Principal Software
> > Engineer
> > > > > > > >
> > > > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Jarek Potiuk
> > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > >
> > > > > M: +48 660 796 129 <+48660796129>
> > > > > [image: Polidea] <https://www.polidea.com/>
> > > >
> > >
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: Consider using stale bot for issues
Posted by Maxime Beauchemin <ma...@gmail.com>.
About labeling on Github, I wrote a bot for Superset that enables anyone to
apply labels through commenting using emojis.
It does other things like auto-labeling organization on an allow-list. We
could teach it new tricks top.
Generalizing it or porting it to work in other communities should be
very easy.
I've also been advocating for the ASF to open up the triage role, but was
hoping to use .asf-config.yaml and avoid the voting process...
Check it out the bot here:
https://github.com/apache-superset/superset-github-bot
On Sun, Sep 13, 2020, 7:56 PM Vikram Koka <vi...@astronomer.io> wrote:
> Mine is @vikramkoka
>
>
>
> On Sun, Sep 13, 2020 at 7:29 PM Elad Kalif <el...@gmail.com> wrote:
>
> > mine is @eladkal
> >
> > On Mon, Sep 14, 2020 at 4:33 AM Pete DeJoy <pd...@gmail.com> wrote:
> >
> > > I’d love to help as well! Gh handle is @petedejoy
> > >
> > > Thanks for organizing everyone.
> > >
> > > Pete
> > > On Sep 13, 2020, 4:57 PM -0400, Jarek Potiuk <Jarek.Potiuk@polidea.com
> >,
> > > wrote:
> > > > @Kamil Breguła <ka...@polidea.com> - I believe we already
> base
> > > it
> > > > on the experience of others (see the discussion before). I think in
> our
> > > > case the will of people and their commitment to do so is far more
> > > important
> > > > than any tools we would like to use (community over code). I think we
> > > > should first let the people who want to do it try to do the task and
> we
> > > can
> > > > introduce tools afterwards. No matter what, those people will need
> > > access.
> > > > And then they can propose and choose any tool that make sense to
> them.
> > > >
> > > > Paola, Elead,Vikram (and anyone who wants the triage permission) -
> > please
> > > > state your github users here, so I can create the ticket :)
> > > >
> > > > J.
> > > >
> > > >
> > > > On Sun, Sep 13, 2020 at 9:40 PM Kamil Breguła <
> > kamil.bregula@polidea.com
> > > >
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I agree that it is worth considering changes in the way of handling
> > > > > issues. Google has created a tool that can help us the issue and PR
> > > triage
> > > > > for large open-source projects
> > > > > https://github.com/google/triage-party
> > > > > It was built from the Google Container DevEx team's experience
> > > contributing
> > > > > to popular open-source projects, such as minikube, Skaffold, and
> > > Kaniko. Is
> > > > > this something we should consider?
> > > > >
> > > > > How do other projects handle issues? Maybe we can base our process
> on
> > > the
> > > > > experience of others.
> > > > >
> > > > > Best regards,
> > > > > Kamil Breguła
> > > > >
> > > > > On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka <vi...@astronomer.io>
> > > wrote:
> > > > >
> > > > > > Sounds good!
> > > > > >
> > > > > > In the meantime, I will draft up a proposal for the set of labels
> > and
> > > > > > milestones that we are using to eliminate duplication to factor
> in
> > > the
> > > > > 2.0
> > > > > > timeline.
> > > > > >
> > > > > >
> > > > > > On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <
> > > Jarek.Potiuk@polidea.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Fantastic initiative!
> > > > > > >
> > > > > > > However, currently you have no way to give access to either of
> > the
> > > > > > > people involved to modify the labels or assign them to issues.
> > > > > > >
> > > > > > > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the
> projects
> > > to
> > > > > > assign
> > > > > > > people to the "Triage" role I was talking about:
> > > > > > > https://infra.apache.org/github-roles.html
> > > > > > >
> > > > > > > Can you please send me your github issues Vikram, Paola, Elad
> > > > > > >
> > > > > > > I will then create an INFRA ticket to add you?
> > > > > > >
> > > > > > > Unfortunately, there is no possibility yet to self-manage it,
> so
> > > it has
> > > > > > to
> > > > > > > be done through an INFRA ticket and it might take a few days to
> > > > > process.
> > > > > > >
> > > > > > > Anyone else willing to join our Triage squad :) ?
> > > > > > >
> > > > > > > J.
> > > > > > >
> > > > > > >
> > > > > > > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <
> > vikram@astronomer.io>
> > > > > > wrote:
> > > > > > >
> > > > > > > > I agree.
> > > > > > > >
> > > > > > > > Paola and Elad, I would like to help on this one as well.
> Let's
> > > get
> > > > > > > > together and nail this.
> > > > > > > >
> > > > > > > > I spent a couple of hours looking through the open Github
> > issues
> > > > > > earlier
> > > > > > > > today to look for some patterns.
> > > > > > > > Currently, we have 576 open and "not invalid" issues.
> > > > > > > > Out of these, we have around:
> > > > > > > > - 270 open feature requests, which span the full gamut of
> > > > > > functionality,
> > > > > > > > from user visible to internal CI process.
> > > > > > > > - 220 bugs including some going back to March as noted by
> > Tomasz.
> > > > > There
> > > > > > > > seem to be a fair number of these which need some
> > categorization
> > > at
> > > > > > > least.
> > > > > > > > - 70 docs issues. These are categorized sometimes as
> > "area:docs"
> > > and
> > > > > > at
> > > > > > > > other times as "kind:documentation".
> > > > > > > > - 50 already assigned to milestones: Either Airflow 2.0.0 or
> > > > > 10.10.13
> > > > > > > > - 80 provider related issues
> > > > > > > >
> > > > > > > > There was a set of 6, created in March 2019 which was rather
> > > > > peculiarly
> > > > > > > > categorized as "Waiting for AIP".
> > > > > > > >
> > > > > > > > These don't all add up the total, since there are issues
> which
> > > are
> > > > > > > > categorized (correctly) in multiple labels. However, we do
> seem
> > > to
> > > > > have
> > > > > > > > proliferation of labels which would be useful to cleanup.
> > > > > > > >
> > > > > > > > Overall, I do think some time spent on documenting the use of
> > > labels,
> > > > > > > then
> > > > > > > > categorizing and cleaning up the issues would be very useful.
> > > > > > > >
> > > > > > > > Happy to help take care of this. Let's do it.
> > > > > > > >
> > > > > > > > Vikram
> > > > > > > >
> > > > > > > >
> > > > > > > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
> > > > > > Jarek.Potiuk@polidea.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <
> > > kaxilnaik@gmail.com>
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Yeah I agree and looks like Paola and Elad have already
> > > > > volunteered
> > > > > > > to
> > > > > > > > > help
> > > > > > > > > > triage.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Kaxil
> > > > > > > > > >
> > > > > > > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <
> > > > > turbaszek@apache.org>
> > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi all,
> > > > > > > > > > >
> > > > > > > > > > > The main reason I suggested the stale bot was the lack
> of
> > > any
> > > > > > > > > > > widespread prioritization/reviewing of issues which
> > > results in
> > > > > > big
> > > > > > > > > > > pile of never addresses issues.
> > > > > > > > > > >
> > > > > > > > > > > I think that triage access is a better answer to this
> > > problem
> > > > > as
> > > > > > > > > > > engaging more people will help us all. I'm +1 for that.
> > > > > > > > > > >
> > > > > > > > > > > Cheers,
> > > > > > > > > > > Tomek
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > > > > > > > > <pa...@astronomer.io> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi all,
> > > > > > > > > > > >
> > > > > > > > > > > > Paola here from Astronomer. I've been working at
> Astro
> > > since
> > > > > > our
> > > > > > > > > early
> > > > > > > > > > > days in both Customer and Product-centric roles and
> have
> > of
> > > > > > course
> > > > > > > > been
> > > > > > > > > > > closely following all-things Airflow for a long time.
> > > > > > > > > > > >
> > > > > > > > > > > > I happened to read this conversation around GH Issue
> > > > > management
> > > > > > > and
> > > > > > > > > > > figure I can step up to volunteer as someone familiar
> > with
> > > the
> > > > > > > > project
> > > > > > > > > +
> > > > > > > > > > > Product Ops principles, if that'd be helpful. I could
> > > always
> > > > > > start
> > > > > > > > by:
> > > > > > > > > > > >
> > > > > > > > > > > > - Cleaning up/commenting on duplicate issues (or
> close
> > > given
> > > > > > the
> > > > > > > > > right
> > > > > > > > > > > permissions)
> > > > > > > > > > > > - Commenting on stale issues and investigate whether
> > > they're
> > > > > > > still
> > > > > > > > a
> > > > > > > > > > > problem or already addressed
> > > > > > > > > > > > - Asking questions as needed if issues need
> > > clarification or
> > > > > > > > > additional
> > > > > > > > > > > scoping
> > > > > > > > > > > >
> > > > > > > > > > > > If this would be helpful, I'm more than happy to get
> > > involved
> > > > > > and
> > > > > > > > > pick
> > > > > > > > > > > at these over time. It'll likely be a journey that
> never
> > > ends,
> > > > > > but
> > > > > > > I
> > > > > > > > > > think
> > > > > > > > > > > a compelling need to keep the community momentum going.
> > > Let me
> > > > > > > know -
> > > > > > > > > and
> > > > > > > > > > > great to meet you all.
> > > > > > > > > > > >
> > > > > > > > > > > > Cheers,
> > > > > > > > > > > > Paola
> > > > > > > > > > > >
> > > > > > > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
> > > > > turbaszek@apache.org>
> > > > > > > > > wrote:
> > > > > > > > > > > > > Hi all,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Currently, we have about 582 open issues on Github.
> > The
> > > > > > oldest
> > > > > > > > > opened
> > > > > > > > > > > > > in March. Do you think we should consider using
> stale
> > > bot
> > > > > as
> > > > > > we
> > > > > > > > do
> > > > > > > > > > for
> > > > > > > > > > > > > PRs?
> > > > > > > > > > > > >
> > > > > > > > > > > > > I don't think that issue that is open since March
> is
> > > "so
> > > > > > > > important"
> > > > > > > > > > to
> > > > > > > > > > > > > keep it still open. This would also automate the
> > > process of
> > > > > > > > > verifying
> > > > > > > > > > > > > the issue (the author will be notified and asked
> for
> > an
> > > > > > > update).
> > > > > > > > If
> > > > > > > > > > > > > the issue is something that we want to keep open we
> > > should
> > > > > be
> > > > > > > > able
> > > > > > > > > to
> > > > > > > > > > > > > use the "pinned" label.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Other projects use it and I don't see anything
> wrong
> > > with
> > > > > > it. I
> > > > > > > > > would
> > > > > > > > > > > > > say that 30d is a good period for keeping an issue
> > > open.
> > > > > > > > > > > > >
> > > > > > > > > > > > > What do you think?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Bests,
> > > > > > > > > > > > > Tomek
> > > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > >
> > > > > > > > > Jarek Potiuk
> > > > > > > > > Polidea <https://www.polidea.com/> | Principal Software
> > > Engineer
> > > > > > > > >
> > > > > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Jarek Potiuk
> > > > > > > Polidea <https://www.polidea.com/> | Principal Software
> Engineer
> > > > > > >
> > > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > [image: Polidea] <https://www.polidea.com/>
> > >
> >
>
Re: Consider using stale bot for issues
Posted by Vikram Koka <vi...@astronomer.io>.
Mine is @vikramkoka
On Sun, Sep 13, 2020 at 7:29 PM Elad Kalif <el...@gmail.com> wrote:
> mine is @eladkal
>
> On Mon, Sep 14, 2020 at 4:33 AM Pete DeJoy <pd...@gmail.com> wrote:
>
> > I’d love to help as well! Gh handle is @petedejoy
> >
> > Thanks for organizing everyone.
> >
> > Pete
> > On Sep 13, 2020, 4:57 PM -0400, Jarek Potiuk <Ja...@polidea.com>,
> > wrote:
> > > @Kamil Breguła <ka...@polidea.com> - I believe we already base
> > it
> > > on the experience of others (see the discussion before). I think in our
> > > case the will of people and their commitment to do so is far more
> > important
> > > than any tools we would like to use (community over code). I think we
> > > should first let the people who want to do it try to do the task and we
> > can
> > > introduce tools afterwards. No matter what, those people will need
> > access.
> > > And then they can propose and choose any tool that make sense to them.
> > >
> > > Paola, Elead,Vikram (and anyone who wants the triage permission) -
> please
> > > state your github users here, so I can create the ticket :)
> > >
> > > J.
> > >
> > >
> > > On Sun, Sep 13, 2020 at 9:40 PM Kamil Breguła <
> kamil.bregula@polidea.com
> > >
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > I agree that it is worth considering changes in the way of handling
> > > > issues. Google has created a tool that can help us the issue and PR
> > triage
> > > > for large open-source projects
> > > > https://github.com/google/triage-party
> > > > It was built from the Google Container DevEx team's experience
> > contributing
> > > > to popular open-source projects, such as minikube, Skaffold, and
> > Kaniko. Is
> > > > this something we should consider?
> > > >
> > > > How do other projects handle issues? Maybe we can base our process on
> > the
> > > > experience of others.
> > > >
> > > > Best regards,
> > > > Kamil Breguła
> > > >
> > > > On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka <vi...@astronomer.io>
> > wrote:
> > > >
> > > > > Sounds good!
> > > > >
> > > > > In the meantime, I will draft up a proposal for the set of labels
> and
> > > > > milestones that we are using to eliminate duplication to factor in
> > the
> > > > 2.0
> > > > > timeline.
> > > > >
> > > > >
> > > > > On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <
> > Jarek.Potiuk@polidea.com>
> > > > > wrote:
> > > > >
> > > > > > Fantastic initiative!
> > > > > >
> > > > > > However, currently you have no way to give access to either of
> the
> > > > > > people involved to modify the labels or assign them to issues.
> > > > > >
> > > > > > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the projects
> > to
> > > > > assign
> > > > > > people to the "Triage" role I was talking about:
> > > > > > https://infra.apache.org/github-roles.html
> > > > > >
> > > > > > Can you please send me your github issues Vikram, Paola, Elad
> > > > > >
> > > > > > I will then create an INFRA ticket to add you?
> > > > > >
> > > > > > Unfortunately, there is no possibility yet to self-manage it, so
> > it has
> > > > > to
> > > > > > be done through an INFRA ticket and it might take a few days to
> > > > process.
> > > > > >
> > > > > > Anyone else willing to join our Triage squad :) ?
> > > > > >
> > > > > > J.
> > > > > >
> > > > > >
> > > > > > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <
> vikram@astronomer.io>
> > > > > wrote:
> > > > > >
> > > > > > > I agree.
> > > > > > >
> > > > > > > Paola and Elad, I would like to help on this one as well. Let's
> > get
> > > > > > > together and nail this.
> > > > > > >
> > > > > > > I spent a couple of hours looking through the open Github
> issues
> > > > > earlier
> > > > > > > today to look for some patterns.
> > > > > > > Currently, we have 576 open and "not invalid" issues.
> > > > > > > Out of these, we have around:
> > > > > > > - 270 open feature requests, which span the full gamut of
> > > > > functionality,
> > > > > > > from user visible to internal CI process.
> > > > > > > - 220 bugs including some going back to March as noted by
> Tomasz.
> > > > There
> > > > > > > seem to be a fair number of these which need some
> categorization
> > at
> > > > > > least.
> > > > > > > - 70 docs issues. These are categorized sometimes as
> "area:docs"
> > and
> > > > > at
> > > > > > > other times as "kind:documentation".
> > > > > > > - 50 already assigned to milestones: Either Airflow 2.0.0 or
> > > > 10.10.13
> > > > > > > - 80 provider related issues
> > > > > > >
> > > > > > > There was a set of 6, created in March 2019 which was rather
> > > > peculiarly
> > > > > > > categorized as "Waiting for AIP".
> > > > > > >
> > > > > > > These don't all add up the total, since there are issues which
> > are
> > > > > > > categorized (correctly) in multiple labels. However, we do seem
> > to
> > > > have
> > > > > > > proliferation of labels which would be useful to cleanup.
> > > > > > >
> > > > > > > Overall, I do think some time spent on documenting the use of
> > labels,
> > > > > > then
> > > > > > > categorizing and cleaning up the issues would be very useful.
> > > > > > >
> > > > > > > Happy to help take care of this. Let's do it.
> > > > > > >
> > > > > > > Vikram
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
> > > > > Jarek.Potiuk@polidea.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <
> > kaxilnaik@gmail.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > Yeah I agree and looks like Paola and Elad have already
> > > > volunteered
> > > > > > to
> > > > > > > > help
> > > > > > > > > triage.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Kaxil
> > > > > > > > >
> > > > > > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <
> > > > turbaszek@apache.org>
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi all,
> > > > > > > > > >
> > > > > > > > > > The main reason I suggested the stale bot was the lack of
> > any
> > > > > > > > > > widespread prioritization/reviewing of issues which
> > results in
> > > > > big
> > > > > > > > > > pile of never addresses issues.
> > > > > > > > > >
> > > > > > > > > > I think that triage access is a better answer to this
> > problem
> > > > as
> > > > > > > > > > engaging more people will help us all. I'm +1 for that.
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > > Tomek
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > > > > > > > <pa...@astronomer.io> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi all,
> > > > > > > > > > >
> > > > > > > > > > > Paola here from Astronomer. I've been working at Astro
> > since
> > > > > our
> > > > > > > > early
> > > > > > > > > > days in both Customer and Product-centric roles and have
> of
> > > > > course
> > > > > > > been
> > > > > > > > > > closely following all-things Airflow for a long time.
> > > > > > > > > > >
> > > > > > > > > > > I happened to read this conversation around GH Issue
> > > > management
> > > > > > and
> > > > > > > > > > figure I can step up to volunteer as someone familiar
> with
> > the
> > > > > > > project
> > > > > > > > +
> > > > > > > > > > Product Ops principles, if that'd be helpful. I could
> > always
> > > > > start
> > > > > > > by:
> > > > > > > > > > >
> > > > > > > > > > > - Cleaning up/commenting on duplicate issues (or close
> > given
> > > > > the
> > > > > > > > right
> > > > > > > > > > permissions)
> > > > > > > > > > > - Commenting on stale issues and investigate whether
> > they're
> > > > > > still
> > > > > > > a
> > > > > > > > > > problem or already addressed
> > > > > > > > > > > - Asking questions as needed if issues need
> > clarification or
> > > > > > > > additional
> > > > > > > > > > scoping
> > > > > > > > > > >
> > > > > > > > > > > If this would be helpful, I'm more than happy to get
> > involved
> > > > > and
> > > > > > > > pick
> > > > > > > > > > at these over time. It'll likely be a journey that never
> > ends,
> > > > > but
> > > > > > I
> > > > > > > > > think
> > > > > > > > > > a compelling need to keep the community momentum going.
> > Let me
> > > > > > know -
> > > > > > > > and
> > > > > > > > > > great to meet you all.
> > > > > > > > > > >
> > > > > > > > > > > Cheers,
> > > > > > > > > > > Paola
> > > > > > > > > > >
> > > > > > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
> > > > turbaszek@apache.org>
> > > > > > > > wrote:
> > > > > > > > > > > > Hi all,
> > > > > > > > > > > >
> > > > > > > > > > > > Currently, we have about 582 open issues on Github.
> The
> > > > > oldest
> > > > > > > > opened
> > > > > > > > > > > > in March. Do you think we should consider using stale
> > bot
> > > > as
> > > > > we
> > > > > > > do
> > > > > > > > > for
> > > > > > > > > > > > PRs?
> > > > > > > > > > > >
> > > > > > > > > > > > I don't think that issue that is open since March is
> > "so
> > > > > > > important"
> > > > > > > > > to
> > > > > > > > > > > > keep it still open. This would also automate the
> > process of
> > > > > > > > verifying
> > > > > > > > > > > > the issue (the author will be notified and asked for
> an
> > > > > > update).
> > > > > > > If
> > > > > > > > > > > > the issue is something that we want to keep open we
> > should
> > > > be
> > > > > > > able
> > > > > > > > to
> > > > > > > > > > > > use the "pinned" label.
> > > > > > > > > > > >
> > > > > > > > > > > > Other projects use it and I don't see anything wrong
> > with
> > > > > it. I
> > > > > > > > would
> > > > > > > > > > > > say that 30d is a good period for keeping an issue
> > open.
> > > > > > > > > > > >
> > > > > > > > > > > > What do you think?
> > > > > > > > > > > >
> > > > > > > > > > > > Bests,
> > > > > > > > > > > > Tomek
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > Jarek Potiuk
> > > > > > > > Polidea <https://www.polidea.com/> | Principal Software
> > Engineer
> > > > > > > >
> > > > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Jarek Potiuk
> > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > > >
> > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > [image: Polidea] <https://www.polidea.com/>
> >
>
Re: Consider using stale bot for issues
Posted by Elad Kalif <el...@gmail.com>.
mine is @eladkal
On Mon, Sep 14, 2020 at 4:33 AM Pete DeJoy <pd...@gmail.com> wrote:
> I’d love to help as well! Gh handle is @petedejoy
>
> Thanks for organizing everyone.
>
> Pete
> On Sep 13, 2020, 4:57 PM -0400, Jarek Potiuk <Ja...@polidea.com>,
> wrote:
> > @Kamil Breguła <ka...@polidea.com> - I believe we already base
> it
> > on the experience of others (see the discussion before). I think in our
> > case the will of people and their commitment to do so is far more
> important
> > than any tools we would like to use (community over code). I think we
> > should first let the people who want to do it try to do the task and we
> can
> > introduce tools afterwards. No matter what, those people will need
> access.
> > And then they can propose and choose any tool that make sense to them.
> >
> > Paola, Elead,Vikram (and anyone who wants the triage permission) - please
> > state your github users here, so I can create the ticket :)
> >
> > J.
> >
> >
> > On Sun, Sep 13, 2020 at 9:40 PM Kamil Breguła <kamil.bregula@polidea.com
> >
> > wrote:
> >
> > > Hello,
> > >
> > > I agree that it is worth considering changes in the way of handling
> > > issues. Google has created a tool that can help us the issue and PR
> triage
> > > for large open-source projects
> > > https://github.com/google/triage-party
> > > It was built from the Google Container DevEx team's experience
> contributing
> > > to popular open-source projects, such as minikube, Skaffold, and
> Kaniko. Is
> > > this something we should consider?
> > >
> > > How do other projects handle issues? Maybe we can base our process on
> the
> > > experience of others.
> > >
> > > Best regards,
> > > Kamil Breguła
> > >
> > > On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka <vi...@astronomer.io>
> wrote:
> > >
> > > > Sounds good!
> > > >
> > > > In the meantime, I will draft up a proposal for the set of labels and
> > > > milestones that we are using to eliminate duplication to factor in
> the
> > > 2.0
> > > > timeline.
> > > >
> > > >
> > > > On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <
> Jarek.Potiuk@polidea.com>
> > > > wrote:
> > > >
> > > > > Fantastic initiative!
> > > > >
> > > > > However, currently you have no way to give access to either of the
> > > > > people involved to modify the labels or assign them to issues.
> > > > >
> > > > > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the projects
> to
> > > > assign
> > > > > people to the "Triage" role I was talking about:
> > > > > https://infra.apache.org/github-roles.html
> > > > >
> > > > > Can you please send me your github issues Vikram, Paola, Elad
> > > > >
> > > > > I will then create an INFRA ticket to add you?
> > > > >
> > > > > Unfortunately, there is no possibility yet to self-manage it, so
> it has
> > > > to
> > > > > be done through an INFRA ticket and it might take a few days to
> > > process.
> > > > >
> > > > > Anyone else willing to join our Triage squad :) ?
> > > > >
> > > > > J.
> > > > >
> > > > >
> > > > > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <vi...@astronomer.io>
> > > > wrote:
> > > > >
> > > > > > I agree.
> > > > > >
> > > > > > Paola and Elad, I would like to help on this one as well. Let's
> get
> > > > > > together and nail this.
> > > > > >
> > > > > > I spent a couple of hours looking through the open Github issues
> > > > earlier
> > > > > > today to look for some patterns.
> > > > > > Currently, we have 576 open and "not invalid" issues.
> > > > > > Out of these, we have around:
> > > > > > - 270 open feature requests, which span the full gamut of
> > > > functionality,
> > > > > > from user visible to internal CI process.
> > > > > > - 220 bugs including some going back to March as noted by Tomasz.
> > > There
> > > > > > seem to be a fair number of these which need some categorization
> at
> > > > > least.
> > > > > > - 70 docs issues. These are categorized sometimes as "area:docs"
> and
> > > > at
> > > > > > other times as "kind:documentation".
> > > > > > - 50 already assigned to milestones: Either Airflow 2.0.0 or
> > > 10.10.13
> > > > > > - 80 provider related issues
> > > > > >
> > > > > > There was a set of 6, created in March 2019 which was rather
> > > peculiarly
> > > > > > categorized as "Waiting for AIP".
> > > > > >
> > > > > > These don't all add up the total, since there are issues which
> are
> > > > > > categorized (correctly) in multiple labels. However, we do seem
> to
> > > have
> > > > > > proliferation of labels which would be useful to cleanup.
> > > > > >
> > > > > > Overall, I do think some time spent on documenting the use of
> labels,
> > > > > then
> > > > > > categorizing and cleaning up the issues would be very useful.
> > > > > >
> > > > > > Happy to help take care of this. Let's do it.
> > > > > >
> > > > > > Vikram
> > > > > >
> > > > > >
> > > > > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
> > > > Jarek.Potiuk@polidea.com>
> > > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <
> kaxilnaik@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > Yeah I agree and looks like Paola and Elad have already
> > > volunteered
> > > > > to
> > > > > > > help
> > > > > > > > triage.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Kaxil
> > > > > > > >
> > > > > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <
> > > turbaszek@apache.org>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > The main reason I suggested the stale bot was the lack of
> any
> > > > > > > > > widespread prioritization/reviewing of issues which
> results in
> > > > big
> > > > > > > > > pile of never addresses issues.
> > > > > > > > >
> > > > > > > > > I think that triage access is a better answer to this
> problem
> > > as
> > > > > > > > > engaging more people will help us all. I'm +1 for that.
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > > Tomek
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > > > > > > <pa...@astronomer.io> wrote:
> > > > > > > > > >
> > > > > > > > > > Hi all,
> > > > > > > > > >
> > > > > > > > > > Paola here from Astronomer. I've been working at Astro
> since
> > > > our
> > > > > > > early
> > > > > > > > > days in both Customer and Product-centric roles and have of
> > > > course
> > > > > > been
> > > > > > > > > closely following all-things Airflow for a long time.
> > > > > > > > > >
> > > > > > > > > > I happened to read this conversation around GH Issue
> > > management
> > > > > and
> > > > > > > > > figure I can step up to volunteer as someone familiar with
> the
> > > > > > project
> > > > > > > +
> > > > > > > > > Product Ops principles, if that'd be helpful. I could
> always
> > > > start
> > > > > > by:
> > > > > > > > > >
> > > > > > > > > > - Cleaning up/commenting on duplicate issues (or close
> given
> > > > the
> > > > > > > right
> > > > > > > > > permissions)
> > > > > > > > > > - Commenting on stale issues and investigate whether
> they're
> > > > > still
> > > > > > a
> > > > > > > > > problem or already addressed
> > > > > > > > > > - Asking questions as needed if issues need
> clarification or
> > > > > > > additional
> > > > > > > > > scoping
> > > > > > > > > >
> > > > > > > > > > If this would be helpful, I'm more than happy to get
> involved
> > > > and
> > > > > > > pick
> > > > > > > > > at these over time. It'll likely be a journey that never
> ends,
> > > > but
> > > > > I
> > > > > > > > think
> > > > > > > > > a compelling need to keep the community momentum going.
> Let me
> > > > > know -
> > > > > > > and
> > > > > > > > > great to meet you all.
> > > > > > > > > >
> > > > > > > > > > Cheers,
> > > > > > > > > > Paola
> > > > > > > > > >
> > > > > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
> > > turbaszek@apache.org>
> > > > > > > wrote:
> > > > > > > > > > > Hi all,
> > > > > > > > > > >
> > > > > > > > > > > Currently, we have about 582 open issues on Github. The
> > > > oldest
> > > > > > > opened
> > > > > > > > > > > in March. Do you think we should consider using stale
> bot
> > > as
> > > > we
> > > > > > do
> > > > > > > > for
> > > > > > > > > > > PRs?
> > > > > > > > > > >
> > > > > > > > > > > I don't think that issue that is open since March is
> "so
> > > > > > important"
> > > > > > > > to
> > > > > > > > > > > keep it still open. This would also automate the
> process of
> > > > > > > verifying
> > > > > > > > > > > the issue (the author will be notified and asked for an
> > > > > update).
> > > > > > If
> > > > > > > > > > > the issue is something that we want to keep open we
> should
> > > be
> > > > > > able
> > > > > > > to
> > > > > > > > > > > use the "pinned" label.
> > > > > > > > > > >
> > > > > > > > > > > Other projects use it and I don't see anything wrong
> with
> > > > it. I
> > > > > > > would
> > > > > > > > > > > say that 30d is a good period for keeping an issue
> open.
> > > > > > > > > > >
> > > > > > > > > > > What do you think?
> > > > > > > > > > >
> > > > > > > > > > > Bests,
> > > > > > > > > > > Tomek
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > Jarek Potiuk
> > > > > > > Polidea <https://www.polidea.com/> | Principal Software
> Engineer
> > > > > > >
> > > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Jarek Potiuk
> > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > >
> > > > > M: +48 660 796 129 <+48660796129>
> > > > > [image: Polidea] <https://www.polidea.com/>
> > > > >
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] <https://www.polidea.com/>
>
Re: Consider using stale bot for issues
Posted by Pete DeJoy <pd...@gmail.com>.
I’d love to help as well! Gh handle is @petedejoy
Thanks for organizing everyone.
Pete
On Sep 13, 2020, 4:57 PM -0400, Jarek Potiuk <Ja...@polidea.com>, wrote:
> @Kamil Breguła <ka...@polidea.com> - I believe we already base it
> on the experience of others (see the discussion before). I think in our
> case the will of people and their commitment to do so is far more important
> than any tools we would like to use (community over code). I think we
> should first let the people who want to do it try to do the task and we can
> introduce tools afterwards. No matter what, those people will need access.
> And then they can propose and choose any tool that make sense to them.
>
> Paola, Elead,Vikram (and anyone who wants the triage permission) - please
> state your github users here, so I can create the ticket :)
>
> J.
>
>
> On Sun, Sep 13, 2020 at 9:40 PM Kamil Breguła <ka...@polidea.com>
> wrote:
>
> > Hello,
> >
> > I agree that it is worth considering changes in the way of handling
> > issues. Google has created a tool that can help us the issue and PR triage
> > for large open-source projects
> > https://github.com/google/triage-party
> > It was built from the Google Container DevEx team's experience contributing
> > to popular open-source projects, such as minikube, Skaffold, and Kaniko. Is
> > this something we should consider?
> >
> > How do other projects handle issues? Maybe we can base our process on the
> > experience of others.
> >
> > Best regards,
> > Kamil Breguła
> >
> > On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka <vi...@astronomer.io> wrote:
> >
> > > Sounds good!
> > >
> > > In the meantime, I will draft up a proposal for the set of labels and
> > > milestones that we are using to eliminate duplication to factor in the
> > 2.0
> > > timeline.
> > >
> > >
> > > On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <Ja...@polidea.com>
> > > wrote:
> > >
> > > > Fantastic initiative!
> > > >
> > > > However, currently you have no way to give access to either of the
> > > > people involved to modify the labels or assign them to issues.
> > > >
> > > > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the projects to
> > > assign
> > > > people to the "Triage" role I was talking about:
> > > > https://infra.apache.org/github-roles.html
> > > >
> > > > Can you please send me your github issues Vikram, Paola, Elad
> > > >
> > > > I will then create an INFRA ticket to add you?
> > > >
> > > > Unfortunately, there is no possibility yet to self-manage it, so it has
> > > to
> > > > be done through an INFRA ticket and it might take a few days to
> > process.
> > > >
> > > > Anyone else willing to join our Triage squad :) ?
> > > >
> > > > J.
> > > >
> > > >
> > > > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <vi...@astronomer.io>
> > > wrote:
> > > >
> > > > > I agree.
> > > > >
> > > > > Paola and Elad, I would like to help on this one as well. Let's get
> > > > > together and nail this.
> > > > >
> > > > > I spent a couple of hours looking through the open Github issues
> > > earlier
> > > > > today to look for some patterns.
> > > > > Currently, we have 576 open and "not invalid" issues.
> > > > > Out of these, we have around:
> > > > > - 270 open feature requests, which span the full gamut of
> > > functionality,
> > > > > from user visible to internal CI process.
> > > > > - 220 bugs including some going back to March as noted by Tomasz.
> > There
> > > > > seem to be a fair number of these which need some categorization at
> > > > least.
> > > > > - 70 docs issues. These are categorized sometimes as "area:docs" and
> > > at
> > > > > other times as "kind:documentation".
> > > > > - 50 already assigned to milestones: Either Airflow 2.0.0 or
> > 10.10.13
> > > > > - 80 provider related issues
> > > > >
> > > > > There was a set of 6, created in March 2019 which was rather
> > peculiarly
> > > > > categorized as "Waiting for AIP".
> > > > >
> > > > > These don't all add up the total, since there are issues which are
> > > > > categorized (correctly) in multiple labels. However, we do seem to
> > have
> > > > > proliferation of labels which would be useful to cleanup.
> > > > >
> > > > > Overall, I do think some time spent on documenting the use of labels,
> > > > then
> > > > > categorizing and cleaning up the issues would be very useful.
> > > > >
> > > > > Happy to help take care of this. Let's do it.
> > > > >
> > > > > Vikram
> > > > >
> > > > >
> > > > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
> > > Jarek.Potiuk@polidea.com>
> > > > > wrote:
> > > > >
> > > > > > +1
> > > > > >
> > > > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <ka...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > Yeah I agree and looks like Paola and Elad have already
> > volunteered
> > > > to
> > > > > > help
> > > > > > > triage.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Kaxil
> > > > > > >
> > > > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <
> > turbaszek@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > The main reason I suggested the stale bot was the lack of any
> > > > > > > > widespread prioritization/reviewing of issues which results in
> > > big
> > > > > > > > pile of never addresses issues.
> > > > > > > >
> > > > > > > > I think that triage access is a better answer to this problem
> > as
> > > > > > > > engaging more people will help us all. I'm +1 for that.
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Tomek
> > > > > > > >
> > > > > > > >
> > > > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > > > > > <pa...@astronomer.io> wrote:
> > > > > > > > >
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > Paola here from Astronomer. I've been working at Astro since
> > > our
> > > > > > early
> > > > > > > > days in both Customer and Product-centric roles and have of
> > > course
> > > > > been
> > > > > > > > closely following all-things Airflow for a long time.
> > > > > > > > >
> > > > > > > > > I happened to read this conversation around GH Issue
> > management
> > > > and
> > > > > > > > figure I can step up to volunteer as someone familiar with the
> > > > > project
> > > > > > +
> > > > > > > > Product Ops principles, if that'd be helpful. I could always
> > > start
> > > > > by:
> > > > > > > > >
> > > > > > > > > - Cleaning up/commenting on duplicate issues (or close given
> > > the
> > > > > > right
> > > > > > > > permissions)
> > > > > > > > > - Commenting on stale issues and investigate whether they're
> > > > still
> > > > > a
> > > > > > > > problem or already addressed
> > > > > > > > > - Asking questions as needed if issues need clarification or
> > > > > > additional
> > > > > > > > scoping
> > > > > > > > >
> > > > > > > > > If this would be helpful, I'm more than happy to get involved
> > > and
> > > > > > pick
> > > > > > > > at these over time. It'll likely be a journey that never ends,
> > > but
> > > > I
> > > > > > > think
> > > > > > > > a compelling need to keep the community momentum going. Let me
> > > > know -
> > > > > > and
> > > > > > > > great to meet you all.
> > > > > > > > >
> > > > > > > > > Cheers,
> > > > > > > > > Paola
> > > > > > > > >
> > > > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
> > turbaszek@apache.org>
> > > > > > wrote:
> > > > > > > > > > Hi all,
> > > > > > > > > >
> > > > > > > > > > Currently, we have about 582 open issues on Github. The
> > > oldest
> > > > > > opened
> > > > > > > > > > in March. Do you think we should consider using stale bot
> > as
> > > we
> > > > > do
> > > > > > > for
> > > > > > > > > > PRs?
> > > > > > > > > >
> > > > > > > > > > I don't think that issue that is open since March is "so
> > > > > important"
> > > > > > > to
> > > > > > > > > > keep it still open. This would also automate the process of
> > > > > > verifying
> > > > > > > > > > the issue (the author will be notified and asked for an
> > > > update).
> > > > > If
> > > > > > > > > > the issue is something that we want to keep open we should
> > be
> > > > > able
> > > > > > to
> > > > > > > > > > use the "pinned" label.
> > > > > > > > > >
> > > > > > > > > > Other projects use it and I don't see anything wrong with
> > > it. I
> > > > > > would
> > > > > > > > > > say that 30d is a good period for keeping an issue open.
> > > > > > > > > >
> > > > > > > > > > What do you think?
> > > > > > > > > >
> > > > > > > > > > Bests,
> > > > > > > > > > Tomek
> > > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Jarek Potiuk
> > > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > > >
> > > > > > M: +48 660 796 129 <+48660796129>
> > > > > > [image: Polidea] <https://www.polidea.com/>
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > [image: Polidea] <https://www.polidea.com/>
> > > >
> > >
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
Re: Consider using stale bot for issues
Posted by Jarek Potiuk <Ja...@polidea.com>.
@Kamil Breguła <ka...@polidea.com> - I believe we already base it
on the experience of others (see the discussion before). I think in our
case the will of people and their commitment to do so is far more important
than any tools we would like to use (community over code). I think we
should first let the people who want to do it try to do the task and we can
introduce tools afterwards. No matter what, those people will need access.
And then they can propose and choose any tool that make sense to them.
Paola, Elead,Vikram (and anyone who wants the triage permission) - please
state your github users here, so I can create the ticket :)
J.
On Sun, Sep 13, 2020 at 9:40 PM Kamil Breguła <ka...@polidea.com>
wrote:
> Hello,
>
> I agree that it is worth considering changes in the way of handling
> issues. Google has created a tool that can help us the issue and PR triage
> for large open-source projects
> https://github.com/google/triage-party
> It was built from the Google Container DevEx team's experience contributing
> to popular open-source projects, such as minikube, Skaffold, and Kaniko. Is
> this something we should consider?
>
> How do other projects handle issues? Maybe we can base our process on the
> experience of others.
>
> Best regards,
> Kamil Breguła
>
> On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka <vi...@astronomer.io> wrote:
>
> > Sounds good!
> >
> > In the meantime, I will draft up a proposal for the set of labels and
> > milestones that we are using to eliminate duplication to factor in the
> 2.0
> > timeline.
> >
> >
> > On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> > > Fantastic initiative!
> > >
> > > However, currently you have no way to give access to either of the
> > > people involved to modify the labels or assign them to issues.
> > >
> > > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the projects to
> > assign
> > > people to the "Triage" role I was talking about:
> > > https://infra.apache.org/github-roles.html
> > >
> > > Can you please send me your github issues Vikram, Paola, Elad
> > >
> > > I will then create an INFRA ticket to add you?
> > >
> > > Unfortunately, there is no possibility yet to self-manage it, so it has
> > to
> > > be done through an INFRA ticket and it might take a few days to
> process.
> > >
> > > Anyone else willing to join our Triage squad :) ?
> > >
> > > J.
> > >
> > >
> > > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <vi...@astronomer.io>
> > wrote:
> > >
> > > > I agree.
> > > >
> > > > Paola and Elad, I would like to help on this one as well. Let's get
> > > > together and nail this.
> > > >
> > > > I spent a couple of hours looking through the open Github issues
> > earlier
> > > > today to look for some patterns.
> > > > Currently, we have 576 open and "not invalid" issues.
> > > > Out of these, we have around:
> > > > - 270 open feature requests, which span the full gamut of
> > functionality,
> > > > from user visible to internal CI process.
> > > > - 220 bugs including some going back to March as noted by Tomasz.
> There
> > > > seem to be a fair number of these which need some categorization at
> > > least.
> > > > - 70 docs issues. These are categorized sometimes as "area:docs" and
> > at
> > > > other times as "kind:documentation".
> > > > - 50 already assigned to milestones: Either Airflow 2.0.0 or
> 10.10.13
> > > > - 80 provider related issues
> > > >
> > > > There was a set of 6, created in March 2019 which was rather
> peculiarly
> > > > categorized as "Waiting for AIP".
> > > >
> > > > These don't all add up the total, since there are issues which are
> > > > categorized (correctly) in multiple labels. However, we do seem to
> have
> > > > proliferation of labels which would be useful to cleanup.
> > > >
> > > > Overall, I do think some time spent on documenting the use of labels,
> > > then
> > > > categorizing and cleaning up the issues would be very useful.
> > > >
> > > > Happy to help take care of this. Let's do it.
> > > >
> > > > Vikram
> > > >
> > > >
> > > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
> > Jarek.Potiuk@polidea.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <ka...@gmail.com>
> > > wrote:
> > > > >
> > > > > > Yeah I agree and looks like Paola and Elad have already
> volunteered
> > > to
> > > > > help
> > > > > > triage.
> > > > > >
> > > > > > Regards,
> > > > > > Kaxil
> > > > > >
> > > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <
> turbaszek@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > The main reason I suggested the stale bot was the lack of any
> > > > > > > widespread prioritization/reviewing of issues which results in
> > big
> > > > > > > pile of never addresses issues.
> > > > > > >
> > > > > > > I think that triage access is a better answer to this problem
> as
> > > > > > > engaging more people will help us all. I'm +1 for that.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Tomek
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > > > > <pa...@astronomer.io> wrote:
> > > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Paola here from Astronomer. I've been working at Astro since
> > our
> > > > > early
> > > > > > > days in both Customer and Product-centric roles and have of
> > course
> > > > been
> > > > > > > closely following all-things Airflow for a long time.
> > > > > > > >
> > > > > > > > I happened to read this conversation around GH Issue
> management
> > > and
> > > > > > > figure I can step up to volunteer as someone familiar with the
> > > > project
> > > > > +
> > > > > > > Product Ops principles, if that'd be helpful. I could always
> > start
> > > > by:
> > > > > > > >
> > > > > > > > - Cleaning up/commenting on duplicate issues (or close given
> > the
> > > > > right
> > > > > > > permissions)
> > > > > > > > - Commenting on stale issues and investigate whether they're
> > > still
> > > > a
> > > > > > > problem or already addressed
> > > > > > > > - Asking questions as needed if issues need clarification or
> > > > > additional
> > > > > > > scoping
> > > > > > > >
> > > > > > > > If this would be helpful, I'm more than happy to get involved
> > and
> > > > > pick
> > > > > > > at these over time. It'll likely be a journey that never ends,
> > but
> > > I
> > > > > > think
> > > > > > > a compelling need to keep the community momentum going. Let me
> > > know -
> > > > > and
> > > > > > > great to meet you all.
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Paola
> > > > > > > >
> > > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <
> turbaszek@apache.org>
> > > > > wrote:
> > > > > > > > > Hi all,
> > > > > > > > >
> > > > > > > > > Currently, we have about 582 open issues on Github. The
> > oldest
> > > > > opened
> > > > > > > > > in March. Do you think we should consider using stale bot
> as
> > we
> > > > do
> > > > > > for
> > > > > > > > > PRs?
> > > > > > > > >
> > > > > > > > > I don't think that issue that is open since March is "so
> > > > important"
> > > > > > to
> > > > > > > > > keep it still open. This would also automate the process of
> > > > > verifying
> > > > > > > > > the issue (the author will be notified and asked for an
> > > update).
> > > > If
> > > > > > > > > the issue is something that we want to keep open we should
> be
> > > > able
> > > > > to
> > > > > > > > > use the "pinned" label.
> > > > > > > > >
> > > > > > > > > Other projects use it and I don't see anything wrong with
> > it. I
> > > > > would
> > > > > > > > > say that 30d is a good period for keeping an issue open.
> > > > > > > > >
> > > > > > > > > What do you think?
> > > > > > > > >
> > > > > > > > > Bests,
> > > > > > > > > Tomek
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Jarek Potiuk
> > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > > >
> > > > > M: +48 660 796 129 <+48660796129>
> > > > > [image: Polidea] <https://www.polidea.com/>
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > [image: Polidea] <https://www.polidea.com/>
> > >
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: Consider using stale bot for issues
Posted by Kamil Breguła <ka...@polidea.com>.
Hello,
I agree that it is worth considering changes in the way of handling
issues. Google has created a tool that can help us the issue and PR triage
for large open-source projects
https://github.com/google/triage-party
It was built from the Google Container DevEx team's experience contributing
to popular open-source projects, such as minikube, Skaffold, and Kaniko. Is
this something we should consider?
How do other projects handle issues? Maybe we can base our process on the
experience of others.
Best regards,
Kamil Breguła
On Sun, Sep 13, 2020 at 9:09 PM Vikram Koka <vi...@astronomer.io> wrote:
> Sounds good!
>
> In the meantime, I will draft up a proposal for the set of labels and
> milestones that we are using to eliminate duplication to factor in the 2.0
> timeline.
>
>
> On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > Fantastic initiative!
> >
> > However, currently you have no way to give access to either of the
> > people involved to modify the labels or assign them to issues.
> >
> > But .... Wait for it ... ASF *JUST DAYS AGO* allowed the projects to
> assign
> > people to the "Triage" role I was talking about:
> > https://infra.apache.org/github-roles.html
> >
> > Can you please send me your github issues Vikram, Paola, Elad
> >
> > I will then create an INFRA ticket to add you?
> >
> > Unfortunately, there is no possibility yet to self-manage it, so it has
> to
> > be done through an INFRA ticket and it might take a few days to process.
> >
> > Anyone else willing to join our Triage squad :) ?
> >
> > J.
> >
> >
> > On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <vi...@astronomer.io>
> wrote:
> >
> > > I agree.
> > >
> > > Paola and Elad, I would like to help on this one as well. Let's get
> > > together and nail this.
> > >
> > > I spent a couple of hours looking through the open Github issues
> earlier
> > > today to look for some patterns.
> > > Currently, we have 576 open and "not invalid" issues.
> > > Out of these, we have around:
> > > - 270 open feature requests, which span the full gamut of
> functionality,
> > > from user visible to internal CI process.
> > > - 220 bugs including some going back to March as noted by Tomasz. There
> > > seem to be a fair number of these which need some categorization at
> > least.
> > > - 70 docs issues. These are categorized sometimes as "area:docs" and
> at
> > > other times as "kind:documentation".
> > > - 50 already assigned to milestones: Either Airflow 2.0.0 or 10.10.13
> > > - 80 provider related issues
> > >
> > > There was a set of 6, created in March 2019 which was rather peculiarly
> > > categorized as "Waiting for AIP".
> > >
> > > These don't all add up the total, since there are issues which are
> > > categorized (correctly) in multiple labels. However, we do seem to have
> > > proliferation of labels which would be useful to cleanup.
> > >
> > > Overall, I do think some time spent on documenting the use of labels,
> > then
> > > categorizing and cleaning up the issues would be very useful.
> > >
> > > Happy to help take care of this. Let's do it.
> > >
> > > Vikram
> > >
> > >
> > > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <
> Jarek.Potiuk@polidea.com>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <ka...@gmail.com>
> > wrote:
> > > >
> > > > > Yeah I agree and looks like Paola and Elad have already volunteered
> > to
> > > > help
> > > > > triage.
> > > > >
> > > > > Regards,
> > > > > Kaxil
> > > > >
> > > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <tu...@apache.org>
> > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > The main reason I suggested the stale bot was the lack of any
> > > > > > widespread prioritization/reviewing of issues which results in
> big
> > > > > > pile of never addresses issues.
> > > > > >
> > > > > > I think that triage access is a better answer to this problem as
> > > > > > engaging more people will help us all. I'm +1 for that.
> > > > > >
> > > > > > Cheers,
> > > > > > Tomek
> > > > > >
> > > > > >
> > > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > > > <pa...@astronomer.io> wrote:
> > > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Paola here from Astronomer. I've been working at Astro since
> our
> > > > early
> > > > > > days in both Customer and Product-centric roles and have of
> course
> > > been
> > > > > > closely following all-things Airflow for a long time.
> > > > > > >
> > > > > > > I happened to read this conversation around GH Issue management
> > and
> > > > > > figure I can step up to volunteer as someone familiar with the
> > > project
> > > > +
> > > > > > Product Ops principles, if that'd be helpful. I could always
> start
> > > by:
> > > > > > >
> > > > > > > - Cleaning up/commenting on duplicate issues (or close given
> the
> > > > right
> > > > > > permissions)
> > > > > > > - Commenting on stale issues and investigate whether they're
> > still
> > > a
> > > > > > problem or already addressed
> > > > > > > - Asking questions as needed if issues need clarification or
> > > > additional
> > > > > > scoping
> > > > > > >
> > > > > > > If this would be helpful, I'm more than happy to get involved
> and
> > > > pick
> > > > > > at these over time. It'll likely be a journey that never ends,
> but
> > I
> > > > > think
> > > > > > a compelling need to keep the community momentum going. Let me
> > know -
> > > > and
> > > > > > great to meet you all.
> > > > > > >
> > > > > > > Cheers,
> > > > > > > Paola
> > > > > > >
> > > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org>
> > > > wrote:
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > Currently, we have about 582 open issues on Github. The
> oldest
> > > > opened
> > > > > > > > in March. Do you think we should consider using stale bot as
> we
> > > do
> > > > > for
> > > > > > > > PRs?
> > > > > > > >
> > > > > > > > I don't think that issue that is open since March is "so
> > > important"
> > > > > to
> > > > > > > > keep it still open. This would also automate the process of
> > > > verifying
> > > > > > > > the issue (the author will be notified and asked for an
> > update).
> > > If
> > > > > > > > the issue is something that we want to keep open we should be
> > > able
> > > > to
> > > > > > > > use the "pinned" label.
> > > > > > > >
> > > > > > > > Other projects use it and I don't see anything wrong with
> it. I
> > > > would
> > > > > > > > say that 30d is a good period for keeping an issue open.
> > > > > > > >
> > > > > > > > What do you think?
> > > > > > > >
> > > > > > > > Bests,
> > > > > > > > Tomek
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Jarek Potiuk
> > > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > > >
> > > > M: +48 660 796 129 <+48660796129>
> > > > [image: Polidea] <https://www.polidea.com/>
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] <https://www.polidea.com/>
> >
>
Re: Consider using stale bot for issues
Posted by Vikram Koka <vi...@astronomer.io>.
Sounds good!
In the meantime, I will draft up a proposal for the set of labels and
milestones that we are using to eliminate duplication to factor in the 2.0
timeline.
On Sun, Sep 13, 2020 at 7:40 AM Jarek Potiuk <Ja...@polidea.com>
wrote:
> Fantastic initiative!
>
> However, currently you have no way to give access to either of the
> people involved to modify the labels or assign them to issues.
>
> But .... Wait for it ... ASF *JUST DAYS AGO* allowed the projects to assign
> people to the "Triage" role I was talking about:
> https://infra.apache.org/github-roles.html
>
> Can you please send me your github issues Vikram, Paola, Elad
>
> I will then create an INFRA ticket to add you?
>
> Unfortunately, there is no possibility yet to self-manage it, so it has to
> be done through an INFRA ticket and it might take a few days to process.
>
> Anyone else willing to join our Triage squad :) ?
>
> J.
>
>
> On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <vi...@astronomer.io> wrote:
>
> > I agree.
> >
> > Paola and Elad, I would like to help on this one as well. Let's get
> > together and nail this.
> >
> > I spent a couple of hours looking through the open Github issues earlier
> > today to look for some patterns.
> > Currently, we have 576 open and "not invalid" issues.
> > Out of these, we have around:
> > - 270 open feature requests, which span the full gamut of functionality,
> > from user visible to internal CI process.
> > - 220 bugs including some going back to March as noted by Tomasz. There
> > seem to be a fair number of these which need some categorization at
> least.
> > - 70 docs issues. These are categorized sometimes as "area:docs" and at
> > other times as "kind:documentation".
> > - 50 already assigned to milestones: Either Airflow 2.0.0 or 10.10.13
> > - 80 provider related issues
> >
> > There was a set of 6, created in March 2019 which was rather peculiarly
> > categorized as "Waiting for AIP".
> >
> > These don't all add up the total, since there are issues which are
> > categorized (correctly) in multiple labels. However, we do seem to have
> > proliferation of labels which would be useful to cleanup.
> >
> > Overall, I do think some time spent on documenting the use of labels,
> then
> > categorizing and cleaning up the issues would be very useful.
> >
> > Happy to help take care of this. Let's do it.
> >
> > Vikram
> >
> >
> > On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <Ja...@polidea.com>
> > wrote:
> >
> > > +1
> > >
> > > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <ka...@gmail.com>
> wrote:
> > >
> > > > Yeah I agree and looks like Paola and Elad have already volunteered
> to
> > > help
> > > > triage.
> > > >
> > > > Regards,
> > > > Kaxil
> > > >
> > > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <tu...@apache.org>
> > > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > The main reason I suggested the stale bot was the lack of any
> > > > > widespread prioritization/reviewing of issues which results in big
> > > > > pile of never addresses issues.
> > > > >
> > > > > I think that triage access is a better answer to this problem as
> > > > > engaging more people will help us all. I'm +1 for that.
> > > > >
> > > > > Cheers,
> > > > > Tomek
> > > > >
> > > > >
> > > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > > <pa...@astronomer.io> wrote:
> > > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > Paola here from Astronomer. I've been working at Astro since our
> > > early
> > > > > days in both Customer and Product-centric roles and have of course
> > been
> > > > > closely following all-things Airflow for a long time.
> > > > > >
> > > > > > I happened to read this conversation around GH Issue management
> and
> > > > > figure I can step up to volunteer as someone familiar with the
> > project
> > > +
> > > > > Product Ops principles, if that'd be helpful. I could always start
> > by:
> > > > > >
> > > > > > - Cleaning up/commenting on duplicate issues (or close given the
> > > right
> > > > > permissions)
> > > > > > - Commenting on stale issues and investigate whether they're
> still
> > a
> > > > > problem or already addressed
> > > > > > - Asking questions as needed if issues need clarification or
> > > additional
> > > > > scoping
> > > > > >
> > > > > > If this would be helpful, I'm more than happy to get involved and
> > > pick
> > > > > at these over time. It'll likely be a journey that never ends, but
> I
> > > > think
> > > > > a compelling need to keep the community momentum going. Let me
> know -
> > > and
> > > > > great to meet you all.
> > > > > >
> > > > > > Cheers,
> > > > > > Paola
> > > > > >
> > > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org>
> > > wrote:
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Currently, we have about 582 open issues on Github. The oldest
> > > opened
> > > > > > > in March. Do you think we should consider using stale bot as we
> > do
> > > > for
> > > > > > > PRs?
> > > > > > >
> > > > > > > I don't think that issue that is open since March is "so
> > important"
> > > > to
> > > > > > > keep it still open. This would also automate the process of
> > > verifying
> > > > > > > the issue (the author will be notified and asked for an
> update).
> > If
> > > > > > > the issue is something that we want to keep open we should be
> > able
> > > to
> > > > > > > use the "pinned" label.
> > > > > > >
> > > > > > > Other projects use it and I don't see anything wrong with it. I
> > > would
> > > > > > > say that 30d is a good period for keeping an issue open.
> > > > > > >
> > > > > > > What do you think?
> > > > > > >
> > > > > > > Bests,
> > > > > > > Tomek
> > > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Jarek Potiuk
> > > Polidea <https://www.polidea.com/> | Principal Software Engineer
> > >
> > > M: +48 660 796 129 <+48660796129>
> > > [image: Polidea] <https://www.polidea.com/>
> > >
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
Re: Consider using stale bot for issues
Posted by Jarek Potiuk <Ja...@polidea.com>.
Fantastic initiative!
However, currently you have no way to give access to either of the
people involved to modify the labels or assign them to issues.
But .... Wait for it ... ASF *JUST DAYS AGO* allowed the projects to assign
people to the "Triage" role I was talking about:
https://infra.apache.org/github-roles.html
Can you please send me your github issues Vikram, Paola, Elad
I will then create an INFRA ticket to add you?
Unfortunately, there is no possibility yet to self-manage it, so it has to
be done through an INFRA ticket and it might take a few days to process.
Anyone else willing to join our Triage squad :) ?
J.
On Sun, Sep 13, 2020 at 2:31 AM Vikram Koka <vi...@astronomer.io> wrote:
> I agree.
>
> Paola and Elad, I would like to help on this one as well. Let's get
> together and nail this.
>
> I spent a couple of hours looking through the open Github issues earlier
> today to look for some patterns.
> Currently, we have 576 open and "not invalid" issues.
> Out of these, we have around:
> - 270 open feature requests, which span the full gamut of functionality,
> from user visible to internal CI process.
> - 220 bugs including some going back to March as noted by Tomasz. There
> seem to be a fair number of these which need some categorization at least.
> - 70 docs issues. These are categorized sometimes as "area:docs" and at
> other times as "kind:documentation".
> - 50 already assigned to milestones: Either Airflow 2.0.0 or 10.10.13
> - 80 provider related issues
>
> There was a set of 6, created in March 2019 which was rather peculiarly
> categorized as "Waiting for AIP".
>
> These don't all add up the total, since there are issues which are
> categorized (correctly) in multiple labels. However, we do seem to have
> proliferation of labels which would be useful to cleanup.
>
> Overall, I do think some time spent on documenting the use of labels, then
> categorizing and cleaning up the issues would be very useful.
>
> Happy to help take care of this. Let's do it.
>
> Vikram
>
>
> On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <Ja...@polidea.com>
> wrote:
>
> > +1
> >
> > On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <ka...@gmail.com> wrote:
> >
> > > Yeah I agree and looks like Paola and Elad have already volunteered to
> > help
> > > triage.
> > >
> > > Regards,
> > > Kaxil
> > >
> > > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <tu...@apache.org>
> > wrote:
> > >
> > > > Hi all,
> > > >
> > > > The main reason I suggested the stale bot was the lack of any
> > > > widespread prioritization/reviewing of issues which results in big
> > > > pile of never addresses issues.
> > > >
> > > > I think that triage access is a better answer to this problem as
> > > > engaging more people will help us all. I'm +1 for that.
> > > >
> > > > Cheers,
> > > > Tomek
> > > >
> > > >
> > > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > > <pa...@astronomer.io> wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > Paola here from Astronomer. I've been working at Astro since our
> > early
> > > > days in both Customer and Product-centric roles and have of course
> been
> > > > closely following all-things Airflow for a long time.
> > > > >
> > > > > I happened to read this conversation around GH Issue management and
> > > > figure I can step up to volunteer as someone familiar with the
> project
> > +
> > > > Product Ops principles, if that'd be helpful. I could always start
> by:
> > > > >
> > > > > - Cleaning up/commenting on duplicate issues (or close given the
> > right
> > > > permissions)
> > > > > - Commenting on stale issues and investigate whether they're still
> a
> > > > problem or already addressed
> > > > > - Asking questions as needed if issues need clarification or
> > additional
> > > > scoping
> > > > >
> > > > > If this would be helpful, I'm more than happy to get involved and
> > pick
> > > > at these over time. It'll likely be a journey that never ends, but I
> > > think
> > > > a compelling need to keep the community momentum going. Let me know -
> > and
> > > > great to meet you all.
> > > > >
> > > > > Cheers,
> > > > > Paola
> > > > >
> > > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org>
> > wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > Currently, we have about 582 open issues on Github. The oldest
> > opened
> > > > > > in March. Do you think we should consider using stale bot as we
> do
> > > for
> > > > > > PRs?
> > > > > >
> > > > > > I don't think that issue that is open since March is "so
> important"
> > > to
> > > > > > keep it still open. This would also automate the process of
> > verifying
> > > > > > the issue (the author will be notified and asked for an update).
> If
> > > > > > the issue is something that we want to keep open we should be
> able
> > to
> > > > > > use the "pinned" label.
> > > > > >
> > > > > > Other projects use it and I don't see anything wrong with it. I
> > would
> > > > > > say that 30d is a good period for keeping an issue open.
> > > > > >
> > > > > > What do you think?
> > > > > >
> > > > > > Bests,
> > > > > > Tomek
> > > > > >
> > > >
> > >
> >
> >
> > --
> >
> > Jarek Potiuk
> > Polidea <https://www.polidea.com/> | Principal Software Engineer
> >
> > M: +48 660 796 129 <+48660796129>
> > [image: Polidea] <https://www.polidea.com/>
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: Consider using stale bot for issues
Posted by Vikram Koka <vi...@astronomer.io>.
I agree.
Paola and Elad, I would like to help on this one as well. Let's get
together and nail this.
I spent a couple of hours looking through the open Github issues earlier
today to look for some patterns.
Currently, we have 576 open and "not invalid" issues.
Out of these, we have around:
- 270 open feature requests, which span the full gamut of functionality,
from user visible to internal CI process.
- 220 bugs including some going back to March as noted by Tomasz. There
seem to be a fair number of these which need some categorization at least.
- 70 docs issues. These are categorized sometimes as "area:docs" and at
other times as "kind:documentation".
- 50 already assigned to milestones: Either Airflow 2.0.0 or 10.10.13
- 80 provider related issues
There was a set of 6, created in March 2019 which was rather peculiarly
categorized as "Waiting for AIP".
These don't all add up the total, since there are issues which are
categorized (correctly) in multiple labels. However, we do seem to have
proliferation of labels which would be useful to cleanup.
Overall, I do think some time spent on documenting the use of labels, then
categorizing and cleaning up the issues would be very useful.
Happy to help take care of this. Let's do it.
Vikram
On Fri, Sep 11, 2020 at 12:00 PM Jarek Potiuk <Ja...@polidea.com>
wrote:
> +1
>
> On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <ka...@gmail.com> wrote:
>
> > Yeah I agree and looks like Paola and Elad have already volunteered to
> help
> > triage.
> >
> > Regards,
> > Kaxil
> >
> > On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <tu...@apache.org>
> wrote:
> >
> > > Hi all,
> > >
> > > The main reason I suggested the stale bot was the lack of any
> > > widespread prioritization/reviewing of issues which results in big
> > > pile of never addresses issues.
> > >
> > > I think that triage access is a better answer to this problem as
> > > engaging more people will help us all. I'm +1 for that.
> > >
> > > Cheers,
> > > Tomek
> > >
> > >
> > > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > > <pa...@astronomer.io> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Paola here from Astronomer. I've been working at Astro since our
> early
> > > days in both Customer and Product-centric roles and have of course been
> > > closely following all-things Airflow for a long time.
> > > >
> > > > I happened to read this conversation around GH Issue management and
> > > figure I can step up to volunteer as someone familiar with the project
> +
> > > Product Ops principles, if that'd be helpful. I could always start by:
> > > >
> > > > - Cleaning up/commenting on duplicate issues (or close given the
> right
> > > permissions)
> > > > - Commenting on stale issues and investigate whether they're still a
> > > problem or already addressed
> > > > - Asking questions as needed if issues need clarification or
> additional
> > > scoping
> > > >
> > > > If this would be helpful, I'm more than happy to get involved and
> pick
> > > at these over time. It'll likely be a journey that never ends, but I
> > think
> > > a compelling need to keep the community momentum going. Let me know -
> and
> > > great to meet you all.
> > > >
> > > > Cheers,
> > > > Paola
> > > >
> > > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org>
> wrote:
> > > > > Hi all,
> > > > >
> > > > > Currently, we have about 582 open issues on Github. The oldest
> opened
> > > > > in March. Do you think we should consider using stale bot as we do
> > for
> > > > > PRs?
> > > > >
> > > > > I don't think that issue that is open since March is "so important"
> > to
> > > > > keep it still open. This would also automate the process of
> verifying
> > > > > the issue (the author will be notified and asked for an update). If
> > > > > the issue is something that we want to keep open we should be able
> to
> > > > > use the "pinned" label.
> > > > >
> > > > > Other projects use it and I don't see anything wrong with it. I
> would
> > > > > say that 30d is a good period for keeping an issue open.
> > > > >
> > > > > What do you think?
> > > > >
> > > > > Bests,
> > > > > Tomek
> > > > >
> > >
> >
>
>
> --
>
> Jarek Potiuk
> Polidea <https://www.polidea.com/> | Principal Software Engineer
>
> M: +48 660 796 129 <+48660796129>
> [image: Polidea] <https://www.polidea.com/>
>
Re: Consider using stale bot for issues
Posted by Jarek Potiuk <Ja...@polidea.com>.
+1
On Fri, Sep 11, 2020 at 7:12 PM Kaxil Naik <ka...@gmail.com> wrote:
> Yeah I agree and looks like Paola and Elad have already volunteered to help
> triage.
>
> Regards,
> Kaxil
>
> On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <tu...@apache.org> wrote:
>
> > Hi all,
> >
> > The main reason I suggested the stale bot was the lack of any
> > widespread prioritization/reviewing of issues which results in big
> > pile of never addresses issues.
> >
> > I think that triage access is a better answer to this problem as
> > engaging more people will help us all. I'm +1 for that.
> >
> > Cheers,
> > Tomek
> >
> >
> > On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> > <pa...@astronomer.io> wrote:
> > >
> > > Hi all,
> > >
> > > Paola here from Astronomer. I've been working at Astro since our early
> > days in both Customer and Product-centric roles and have of course been
> > closely following all-things Airflow for a long time.
> > >
> > > I happened to read this conversation around GH Issue management and
> > figure I can step up to volunteer as someone familiar with the project +
> > Product Ops principles, if that'd be helpful. I could always start by:
> > >
> > > - Cleaning up/commenting on duplicate issues (or close given the right
> > permissions)
> > > - Commenting on stale issues and investigate whether they're still a
> > problem or already addressed
> > > - Asking questions as needed if issues need clarification or additional
> > scoping
> > >
> > > If this would be helpful, I'm more than happy to get involved and pick
> > at these over time. It'll likely be a journey that never ends, but I
> think
> > a compelling need to keep the community momentum going. Let me know - and
> > great to meet you all.
> > >
> > > Cheers,
> > > Paola
> > >
> > > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org> wrote:
> > > > Hi all,
> > > >
> > > > Currently, we have about 582 open issues on Github. The oldest opened
> > > > in March. Do you think we should consider using stale bot as we do
> for
> > > > PRs?
> > > >
> > > > I don't think that issue that is open since March is "so important"
> to
> > > > keep it still open. This would also automate the process of verifying
> > > > the issue (the author will be notified and asked for an update). If
> > > > the issue is something that we want to keep open we should be able to
> > > > use the "pinned" label.
> > > >
> > > > Other projects use it and I don't see anything wrong with it. I would
> > > > say that 30d is a good period for keeping an issue open.
> > > >
> > > > What do you think?
> > > >
> > > > Bests,
> > > > Tomek
> > > >
> >
>
--
Jarek Potiuk
Polidea <https://www.polidea.com/> | Principal Software Engineer
M: +48 660 796 129 <+48660796129>
[image: Polidea] <https://www.polidea.com/>
Re: Consider using stale bot for issues
Posted by Kaxil Naik <ka...@gmail.com>.
Yeah I agree and looks like Paola and Elad have already volunteered to help
triage.
Regards,
Kaxil
On Fri, Sep 11, 2020, 18:09 Tomasz Urbaszek <tu...@apache.org> wrote:
> Hi all,
>
> The main reason I suggested the stale bot was the lack of any
> widespread prioritization/reviewing of issues which results in big
> pile of never addresses issues.
>
> I think that triage access is a better answer to this problem as
> engaging more people will help us all. I'm +1 for that.
>
> Cheers,
> Tomek
>
>
> On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
> <pa...@astronomer.io> wrote:
> >
> > Hi all,
> >
> > Paola here from Astronomer. I've been working at Astro since our early
> days in both Customer and Product-centric roles and have of course been
> closely following all-things Airflow for a long time.
> >
> > I happened to read this conversation around GH Issue management and
> figure I can step up to volunteer as someone familiar with the project +
> Product Ops principles, if that'd be helpful. I could always start by:
> >
> > - Cleaning up/commenting on duplicate issues (or close given the right
> permissions)
> > - Commenting on stale issues and investigate whether they're still a
> problem or already addressed
> > - Asking questions as needed if issues need clarification or additional
> scoping
> >
> > If this would be helpful, I'm more than happy to get involved and pick
> at these over time. It'll likely be a journey that never ends, but I think
> a compelling need to keep the community momentum going. Let me know - and
> great to meet you all.
> >
> > Cheers,
> > Paola
> >
> > On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org> wrote:
> > > Hi all,
> > >
> > > Currently, we have about 582 open issues on Github. The oldest opened
> > > in March. Do you think we should consider using stale bot as we do for
> > > PRs?
> > >
> > > I don't think that issue that is open since March is "so important" to
> > > keep it still open. This would also automate the process of verifying
> > > the issue (the author will be notified and asked for an update). If
> > > the issue is something that we want to keep open we should be able to
> > > use the "pinned" label.
> > >
> > > Other projects use it and I don't see anything wrong with it. I would
> > > say that 30d is a good period for keeping an issue open.
> > >
> > > What do you think?
> > >
> > > Bests,
> > > Tomek
> > >
>
Re: Consider using stale bot for issues
Posted by Tomasz Urbaszek <tu...@apache.org>.
Hi all,
The main reason I suggested the stale bot was the lack of any
widespread prioritization/reviewing of issues which results in big
pile of never addresses issues.
I think that triage access is a better answer to this problem as
engaging more people will help us all. I'm +1 for that.
Cheers,
Tomek
On Fri, Sep 11, 2020 at 5:00 PM Paola Peraza Calderon
<pa...@astronomer.io> wrote:
>
> Hi all,
>
> Paola here from Astronomer. I've been working at Astro since our early days in both Customer and Product-centric roles and have of course been closely following all-things Airflow for a long time.
>
> I happened to read this conversation around GH Issue management and figure I can step up to volunteer as someone familiar with the project + Product Ops principles, if that'd be helpful. I could always start by:
>
> - Cleaning up/commenting on duplicate issues (or close given the right permissions)
> - Commenting on stale issues and investigate whether they're still a problem or already addressed
> - Asking questions as needed if issues need clarification or additional scoping
>
> If this would be helpful, I'm more than happy to get involved and pick at these over time. It'll likely be a journey that never ends, but I think a compelling need to keep the community momentum going. Let me know - and great to meet you all.
>
> Cheers,
> Paola
>
> On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org> wrote:
> > Hi all,
> >
> > Currently, we have about 582 open issues on Github. The oldest opened
> > in March. Do you think we should consider using stale bot as we do for
> > PRs?
> >
> > I don't think that issue that is open since March is "so important" to
> > keep it still open. This would also automate the process of verifying
> > the issue (the author will be notified and asked for an update). If
> > the issue is something that we want to keep open we should be able to
> > use the "pinned" label.
> >
> > Other projects use it and I don't see anything wrong with it. I would
> > say that 30d is a good period for keeping an issue open.
> >
> > What do you think?
> >
> > Bests,
> > Tomek
> >
Re: Consider using stale bot for issues
Posted by Paola Peraza Calderon <pa...@astronomer.io>.
Hi all,
Paola here from Astronomer. I've been working at Astro since our early days in both Customer and Product-centric roles and have of course been closely following all-things Airflow for a long time.
I happened to read this conversation around GH Issue management and figure I can step up to volunteer as someone familiar with the project + Product Ops principles, if that'd be helpful. I could always start by:
- Cleaning up/commenting on duplicate issues (or close given the right permissions)
- Commenting on stale issues and investigate whether they're still a problem or already addressed
- Asking questions as needed if issues need clarification or additional scoping
If this would be helpful, I'm more than happy to get involved and pick at these over time. It'll likely be a journey that never ends, but I think a compelling need to keep the community momentum going. Let me know - and great to meet you all.
Cheers,
Paola
On 2020/09/10 11:56:22, Tomasz Urbaszek <tu...@apache.org> wrote:
> Hi all,
>
> Currently, we have about 582 open issues on Github. The oldest opened
> in March. Do you think we should consider using stale bot as we do for
> PRs?
>
> I don't think that issue that is open since March is "so important" to
> keep it still open. This would also automate the process of verifying
> the issue (the author will be notified and asked for an update). If
> the issue is something that we want to keep open we should be able to
> use the "pinned" label.
>
> Other projects use it and I don't see anything wrong with it. I would
> say that 30d is a good period for keeping an issue open.
>
> What do you think?
>
> Bests,
> Tomek
>