Using Stale bot to clean up issues
GUNNAR MILLS
gmills at linux.vnet.ibm.com
Sat Feb 9 11:23:51 AEDT 2019
On 2/7/2019 5:13 PM, Ed Tanous wrote:
> Have we looked at what a majority of our issues are getting stale from?
Just in openbmc/openbmc there is 467 issues. 281 are older than a year
and 78 are older than 2 years.
Some of them are a lack of feedback from the submitter. A pretty large
percentage I don’t know if they are still an issue.
I feel this many issues is unmanageable. From the stale bot README:
"In the experience of the maintainers of this app—and the hundreds of
other projects and organizations that use it—focusing on issues that are
actively affecting humans is an effective method for prioritizing work.
To some, a robot trying to close stale issues may seem inhospitable or
offensive to contributors. But the alternative is to disrespect them by
setting false expectations and implicitly ignoring their work. This app
makes it explicit: if work is not progressing, then it's stale. A
comment is all it takes to keep the conversation alive."
I feel strongly we should do something like this to manage our issues.
- Gunnar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190208/7aff0080/attachment.htm>
More information about the openbmc
mailing list