You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Todd Farmer <to...@voltrondata.com> on 2022/07/08 15:49:28 UTC

Proposal: Unassign idle issues

Hello,

The backlog of ARROW issues currently stands at 2585 open issues [1]. The
size of the backlog presents challenges to users and developers alike, and
I believe the project would benefit from establishing guidance around issue
handling. I'll be submitting a series of proposals for discussion,
including this one focusing specifically on assigned issues that have gone
dormant.

It's my belief that issue assignment implies the assignee is actively
working on a task, or intends to start working on it in short order. In
cases where well-intentioned developers are assigned tasks, but no progress
is reported for extended periods of time, I propose that we unassign the
issue and add a comment explaining why the action was taken. I believe any
assigned issue that has been idle for 90 days or more is a good threshold
to use, and that currently maps to 370 such issues [2], or 14% of the
current backlog. (Note: 153 of those have not been updated in the past
year.)

I would also like to expand the existing "Report bugs and propose features"
documentation [3] to cover issue handling in general, including the ask
that assigned issues be actively worked within the 90 day period or be
unassigned.

In summary, here are the actions I propose:

1. Establish a threshold at which assigned, idle issues should be
unassigned and comment added.
2. Define that threshold to be 90 days.
3. Document the above as a project policy for issue handling (PR against
docs)
4. Automate 1 and 2 above.

Thoughts on this?

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved%20%20AND%20assignee%20IS%20NOT%20EMPTY%20AND%20updated%20%3C%20-90d
[3] https://arrow.apache.org/docs/developers/bug_reports.html

Best regards,

Todd Farmer

Re: Proposal: Unassign idle issues

Posted by Weston Pace <we...@gmail.com>.
+1 (I'm assuming, as Neal described, I can just reassign the issue to
myself and it won't confuse the assignment bot)

On Fri, Jul 8, 2022 at 8:29 AM Jacob Wujciak <ja...@voltrondata.com> wrote:
>
> I support this idea and a 90 days threshold seems good to me!
>
> On Fri, Jul 8, 2022 at 8:02 PM Neal Richardson <ne...@gmail.com>
> wrote:
>
> > Sounds like a good idea to me, thanks for taking the initiative on this.
> >
> > To Benson's idea about varying the timeout based on priority, IMO we could
> > just start with the simple approach and see how that goes. Maybe that would
> > be helpful but maybe it's not necessary. If you're truly watching an issue
> > because you intend to do it, you'll notice that you were removed from it
> > and can reassign yourself, which would give you another 90 days.
> >
> > Neal
> >
> >
> > On Fri, Jul 8, 2022 at 12:00 PM Benson Muite <be...@emailplus.org>
> > wrote:
> >
> > > On 7/8/22 18:49, Todd Farmer wrote:
> > > > Hello,
> > > >
> > > > The backlog of ARROW issues currently stands at 2585 open issues [1].
> > The
> > > > size of the backlog presents challenges to users and developers alike,
> > > and
> > > > I believe the project would benefit from establishing guidance around
> > > issue
> > > > handling. I'll be submitting a series of proposals for discussion,
> > > > including this one focusing specifically on assigned issues that have
> > > gone
> > > > dormant.
> > > >
> > > > It's my belief that issue assignment implies the assignee is actively
> > > > working on a task, or intends to start working on it in short order. In
> > > > cases where well-intentioned developers are assigned tasks, but no
> > > progress
> > > > is reported for extended periods of time, I propose that we unassign
> > the
> > > > issue and add a comment explaining why the action was taken. I believe
> > > any
> > > > assigned issue that has been idle for 90 days or more is a good
> > threshold
> > > > to use, and that currently maps to 370 such issues [2], or 14% of the
> > > > current backlog. (Note: 153 of those have not been updated in the past
> > > > year.)
> > > >
> > > > I would also like to expand the existing "Report bugs and propose
> > > features"
> > > > documentation [3] to cover issue handling in general, including the ask
> > > > that assigned issues be actively worked within the 90 day period or be
> > > > unassigned.
> > > >
> > > > In summary, here are the actions I propose:
> > > >
> > > > 1. Establish a threshold at which assigned, idle issues should be
> > > > unassigned and comment added.
> > > > 2. Define that threshold to be 90 days.
> > > > 3. Document the above as a project policy for issue handling (PR
> > against
> > > > docs)
> > > > 4. Automate 1 and 2 above.
> > > >
> > > > Thoughts on this?
> > > >
> > > > [1]
> > > >
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved
> > > > [2]
> > > >
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved%20%20AND%20assignee%20IS%20NOT%20EMPTY%20AND%20updated%20%3C%20-90d
> > > > [3] https://arrow.apache.org/docs/developers/bug_reports.html
> > > >
> > > > Best regards,
> > > >
> > > > Todd Farmer
> > > >
> > > This seems reasonable.  One might change the policy according to the
> > > importance of an issue, with low priority issues given more time.
> > >
> >

Re: Proposal: Unassign idle issues

Posted by Jacob Wujciak <ja...@voltrondata.com>.
I support this idea and a 90 days threshold seems good to me!

On Fri, Jul 8, 2022 at 8:02 PM Neal Richardson <ne...@gmail.com>
wrote:

> Sounds like a good idea to me, thanks for taking the initiative on this.
>
> To Benson's idea about varying the timeout based on priority, IMO we could
> just start with the simple approach and see how that goes. Maybe that would
> be helpful but maybe it's not necessary. If you're truly watching an issue
> because you intend to do it, you'll notice that you were removed from it
> and can reassign yourself, which would give you another 90 days.
>
> Neal
>
>
> On Fri, Jul 8, 2022 at 12:00 PM Benson Muite <be...@emailplus.org>
> wrote:
>
> > On 7/8/22 18:49, Todd Farmer wrote:
> > > Hello,
> > >
> > > The backlog of ARROW issues currently stands at 2585 open issues [1].
> The
> > > size of the backlog presents challenges to users and developers alike,
> > and
> > > I believe the project would benefit from establishing guidance around
> > issue
> > > handling. I'll be submitting a series of proposals for discussion,
> > > including this one focusing specifically on assigned issues that have
> > gone
> > > dormant.
> > >
> > > It's my belief that issue assignment implies the assignee is actively
> > > working on a task, or intends to start working on it in short order. In
> > > cases where well-intentioned developers are assigned tasks, but no
> > progress
> > > is reported for extended periods of time, I propose that we unassign
> the
> > > issue and add a comment explaining why the action was taken. I believe
> > any
> > > assigned issue that has been idle for 90 days or more is a good
> threshold
> > > to use, and that currently maps to 370 such issues [2], or 14% of the
> > > current backlog. (Note: 153 of those have not been updated in the past
> > > year.)
> > >
> > > I would also like to expand the existing "Report bugs and propose
> > features"
> > > documentation [3] to cover issue handling in general, including the ask
> > > that assigned issues be actively worked within the 90 day period or be
> > > unassigned.
> > >
> > > In summary, here are the actions I propose:
> > >
> > > 1. Establish a threshold at which assigned, idle issues should be
> > > unassigned and comment added.
> > > 2. Define that threshold to be 90 days.
> > > 3. Document the above as a project policy for issue handling (PR
> against
> > > docs)
> > > 4. Automate 1 and 2 above.
> > >
> > > Thoughts on this?
> > >
> > > [1]
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved
> > > [2]
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved%20%20AND%20assignee%20IS%20NOT%20EMPTY%20AND%20updated%20%3C%20-90d
> > > [3] https://arrow.apache.org/docs/developers/bug_reports.html
> > >
> > > Best regards,
> > >
> > > Todd Farmer
> > >
> > This seems reasonable.  One might change the policy according to the
> > importance of an issue, with low priority issues given more time.
> >
>

Re: Proposal: Unassign idle issues

Posted by Neal Richardson <ne...@gmail.com>.
Sounds like a good idea to me, thanks for taking the initiative on this.

To Benson's idea about varying the timeout based on priority, IMO we could
just start with the simple approach and see how that goes. Maybe that would
be helpful but maybe it's not necessary. If you're truly watching an issue
because you intend to do it, you'll notice that you were removed from it
and can reassign yourself, which would give you another 90 days.

Neal


On Fri, Jul 8, 2022 at 12:00 PM Benson Muite <be...@emailplus.org>
wrote:

> On 7/8/22 18:49, Todd Farmer wrote:
> > Hello,
> >
> > The backlog of ARROW issues currently stands at 2585 open issues [1]. The
> > size of the backlog presents challenges to users and developers alike,
> and
> > I believe the project would benefit from establishing guidance around
> issue
> > handling. I'll be submitting a series of proposals for discussion,
> > including this one focusing specifically on assigned issues that have
> gone
> > dormant.
> >
> > It's my belief that issue assignment implies the assignee is actively
> > working on a task, or intends to start working on it in short order. In
> > cases where well-intentioned developers are assigned tasks, but no
> progress
> > is reported for extended periods of time, I propose that we unassign the
> > issue and add a comment explaining why the action was taken. I believe
> any
> > assigned issue that has been idle for 90 days or more is a good threshold
> > to use, and that currently maps to 370 such issues [2], or 14% of the
> > current backlog. (Note: 153 of those have not been updated in the past
> > year.)
> >
> > I would also like to expand the existing "Report bugs and propose
> features"
> > documentation [3] to cover issue handling in general, including the ask
> > that assigned issues be actively worked within the 90 day period or be
> > unassigned.
> >
> > In summary, here are the actions I propose:
> >
> > 1. Establish a threshold at which assigned, idle issues should be
> > unassigned and comment added.
> > 2. Define that threshold to be 90 days.
> > 3. Document the above as a project policy for issue handling (PR against
> > docs)
> > 4. Automate 1 and 2 above.
> >
> > Thoughts on this?
> >
> > [1]
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved
> > [2]
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved%20%20AND%20assignee%20IS%20NOT%20EMPTY%20AND%20updated%20%3C%20-90d
> > [3] https://arrow.apache.org/docs/developers/bug_reports.html
> >
> > Best regards,
> >
> > Todd Farmer
> >
> This seems reasonable.  One might change the policy according to the
> importance of an issue, with low priority issues given more time.
>

Re: Proposal: Unassign idle issues

Posted by Benson Muite <be...@emailplus.org>.
On 7/8/22 18:49, Todd Farmer wrote:
> Hello,
> 
> The backlog of ARROW issues currently stands at 2585 open issues [1]. The
> size of the backlog presents challenges to users and developers alike, and
> I believe the project would benefit from establishing guidance around issue
> handling. I'll be submitting a series of proposals for discussion,
> including this one focusing specifically on assigned issues that have gone
> dormant.
> 
> It's my belief that issue assignment implies the assignee is actively
> working on a task, or intends to start working on it in short order. In
> cases where well-intentioned developers are assigned tasks, but no progress
> is reported for extended periods of time, I propose that we unassign the
> issue and add a comment explaining why the action was taken. I believe any
> assigned issue that has been idle for 90 days or more is a good threshold
> to use, and that currently maps to 370 such issues [2], or 14% of the
> current backlog. (Note: 153 of those have not been updated in the past
> year.)
> 
> I would also like to expand the existing "Report bugs and propose features"
> documentation [3] to cover issue handling in general, including the ask
> that assigned issues be actively worked within the 90 day period or be
> unassigned.
> 
> In summary, here are the actions I propose:
> 
> 1. Establish a threshold at which assigned, idle issues should be
> unassigned and comment added.
> 2. Define that threshold to be 90 days.
> 3. Document the above as a project policy for issue handling (PR against
> docs)
> 4. Automate 1 and 2 above.
> 
> Thoughts on this?
> 
> [1]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved
> [2]
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved%20%20AND%20assignee%20IS%20NOT%20EMPTY%20AND%20updated%20%3C%20-90d
> [3] https://arrow.apache.org/docs/developers/bug_reports.html
> 
> Best regards,
> 
> Todd Farmer
> 
This seems reasonable.  One might change the policy according to the 
importance of an issue, with low priority issues given more time.

Re: Proposal: Unassign idle issues

Posted by Todd Farmer <to...@voltrondata.com.INVALID>.
Thank you all for the feedback on the proposal. I unassigned 371 idle (not
updated within past 90 days) issues on 2022-07-12 [1]. It doesn't appear
that this action has caused problems or confusion - please let me know if
I've missed anything. There are currently an additional 31 issues that are
now considered idle, and I'll update those in batch as well [2].

I've created a PR to document this project policy [3].

In doing this, it was noted that issues that are unassigned should probably
not be left in a status of "In Progress". The PR addresses this, specifying
that any issue that is "In Progress" should have an assignee, and issues
lacking an assignee may be set back to a status of "Open" for consistency.

Additionally, the PR proposes standardization of the usage of status and
resolution code field values.

Please comment on the PR as appropriate - it feels any concerns or
suggestions are better coordinated there than via email.

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20comment%20~%20%22This%20issue%20was%20last%20updated%20over%2090%20days%20ago%2C%20which%20may%20be%20an%20indication%20it%20is%20no%20longer%20being%20actively%20worked.%22%20ORDER%20BY%20updated%20DESC
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved%20%20AND%20assignee%20IS%20NOT%20EMPTY%20AND%20updated%20%3C%20-90d
[3] https://github.com/apache/arrow/pull/13781

Thanks,

Todd Farmer


On Tue, Jul 12, 2022 at 6:51 AM Antoine Pitrou <an...@python.org> wrote:

> On Fri, 8 Jul 2022 09:49:28 -0600
> Todd Farmer <to...@voltrondata.com> wrote:
> >
> > In summary, here are the actions I propose:
> >
> > 1. Establish a threshold at which assigned, idle issues should be
> > unassigned and comment added.
> > 2. Define that threshold to be 90 days.
> > 3. Document the above as a project policy for issue handling (PR against
> > docs)
> > 4. Automate 1 and 2 above.
> >
> > Thoughts on this?
>
> +1 from me. This will be a welcome improvement IMHO.
>
> Regards
>
> Antoine.
>
>
>

Re: Proposal: Unassign idle issues

Posted by Antoine Pitrou <an...@python.org>.
On Fri, 8 Jul 2022 09:49:28 -0600
Todd Farmer <to...@voltrondata.com> wrote:
> 
> In summary, here are the actions I propose:
> 
> 1. Establish a threshold at which assigned, idle issues should be
> unassigned and comment added.
> 2. Define that threshold to be 90 days.
> 3. Document the above as a project policy for issue handling (PR against
> docs)
> 4. Automate 1 and 2 above.
> 
> Thoughts on this?

+1 from me. This will be a welcome improvement IMHO.

Regards

Antoine.