Announcement: GitHub Issues Reset #6920
Replies: 6 comments 14 replies
-
|
I used to think this project had a good foundation relying on good development practices. Not anymore definitely. Shameful to delete/ignore potentially useful data provided by users, even if it was only 1% useful. Just do your homework and tidy up the backlog. What a joke. |
Beta Was this translation helpful? Give feedback.
-
|
So many years creating/perfecting development practices to enhance/maximize the impact of feedback loop in software development. I am shocked regardless, not something a serious project would do. |
Beta Was this translation helpful? Give feedback.
-
|
Simple solution... Close with message asking to reopen if issue truly still exists and just work through those. Win-Win |
Beta Was this translation helpful? Give feedback.
-
That's literally what I'll be doing, with just a bit more in-depth instructions on the comment to guide people to the right places for support for non "issues" and we will re open the ones they ask us to that are valid. :) |
Beta Was this translation helpful? Give feedback.
-
|
@lyncodev i had to turn off notifications on the chia repository. I dont know how anyone could keep notifications on without going crazy |
Beta Was this translation helpful? Give feedback.
-
Can confirm. Am crazy. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
90% of issues are from dau's, who consider their layer 8 problems to be bugs |
Beta Was this translation helpful? Give feedback.
-
|
Sometimes you need to just need to be able to work from a clean slate, as opposed to working against 1.4k issues. Issues that are still relevant and important enough can be reopened. It makes more sense to do exactly what they are doing. I see this interface of the project as community contribution, rather than a customer support ticket system. |
Beta Was this translation helpful? Give feedback.
-
|
If you read the actual words instead of assuming the worst, it makes a lot more sense. If you're volunteering to work a week for free, just say that @Gumba4 |
Beta Was this translation helpful? Give feedback.
-
|
Can't you use something like this to close all the stale issues instead: https://github.com/probot/stale In a few weeks only the issues that are being discussed will stay open. |
Beta Was this translation helpful? Give feedback.
-
|
Funny you mention that, I plan to incorporate something just like this going forward once we have it all under control. I have been going back and fourth on just turning it on at the start and letting it do the pruning of all the old issues as well, and I might still do that, but for now am a little uncertain how it might behave with over 1k issues, vs a rolling window of 100 a week or so. Definitely going to implement something like this going forward though, that part is for certain. |
Beta Was this translation helpful? Give feedback.
-
|
This is pretty mainstream these days in large projects. I guess you can give it a try, you have nothing to lose - worst-case scenario it hits the GitHub API rate limit or something, although unlikely given that it's in the thousand requests per hour: https://docs.github.com/en/developers/apps/building-github-apps/rate-limits-for-github-apps |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
READ!!! It is not trashing everything... |
Beta Was this translation helpful? Give feedback.
-
^^^ In fact not trashing ANYTHING! |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
Tl;dr - There is an unmanageable amount of GitHub issues that are either old, not issues, or lost in the noise. We will be doing a “reset” and starting from scratch in the coming days.
We’re working on a better way to help and support the community!
Due to an overwhelming amount of GitHub Issues—many of which are not actual bugs and a majority of which are from before the current version of Chia was released—in the coming days we will be conducting a GitHub Issue Reset.
There are an overwhelming number of “issues” that are little more than duplicates of “I can’t sync” or redundant posts about netspace growth rate, pooling, etc., with many more that are asking for general support (which should be posted elsewhere such as Discussions or Keybase). Most were opened for the above reasons and then subsequently abandoned by their poster when they resolved their issue on their own or new releases were launched, making them out of date.
GitHub Issues are meant to be a place for the Developers to work with the community to resolve bugs and issues, communicate with the open source community over the Pull Requests and feature enhancements they provide. Now that Chia has dedicated resources available for this task, our goal is to stay on top of them regularly so we can solve your issues, but to do that, we need to start from a manageable baseline.
We will be conducting a reset later this week that will mass-close most issues, save for a handful being kept open for one reason or another. The closure will be accompanied with notes that direct submitters on the best course of action to follow up if they still need assistance, with guidance on how to find support in Discussions or Keybase, documentation in the Wiki, and how to re-open the issue for manual review by Chia staff if they think it's an Issue that warrants further attention.
Additionally, we will begin employing the same automated GitHub Job Actions used by many other organizations currently, and auto-respond with a warning to stale issues that have had no updates beyond a week, and automatically closing them a few days after if they are not commented on, in further attempts to keep things manageable and follow best practices.
Do know, however, that none of these actions are permanent or irreversible. We will always endeavor to surface your issues to the right people. Our concern is not about obscuring the quantity of issues, but about ensuring the quality of what is there, and managing the ability to filter through them to ensure the issues that need addressing by the Chia Devs are seen.
Beta Was this translation helpful? Give feedback.
All reactions